Nexscope

YouTube Trending Shorts

Read currently trending YouTube Shorts with titles, URLs, thumbnails, views, likes and comments. Results describe the returned short-form video selection.

CostAt least 10 credits / call
Try online
POST · https://api.nexscope.ai/social/youtube/shorts/trendingMCP · social_youtube_shorts_trending

What this API does

Read currently trending YouTube Shorts with titles, URLs, thumbnails, views, likes and comments. Results describe the returned short-form video selection. Its documented result includes platform, resourceStatus.

YouTube Trending Shorts API use cases

Plan a YouTube Trending Shorts request

A researcher checks the published operation description and supplies the documented inputs for YouTube Trending Shorts. The request stays within the supported parameters rather than assuming other platform capabilities.

Inspect YouTube Trending Shorts results

An analyst reviews platform, resourceStatus from YouTube Trending Shorts for the requested subject. Missing values remain explicit, and the response does not establish complete platform coverage.

Document YouTube Trending Shorts observations

A researcher records the inputs and available results from YouTube Trending Shorts alongside its published description. The record supports a scoped review without inferring unsupported actions, refresh intervals or broader conclusions.

YouTube Trending Shorts API FAQ

What does the YouTube Trending Shorts API return?

Read currently trending YouTube Shorts with titles, URLs, thumbnails, views, likes and comments. Results describe the returned short-form video selection. The documented output includes platform, resourceStatus. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the YouTube Trending Shorts API cost?

The current documented cost is At least 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the YouTube Trending Shorts API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/social/youtube/shorts/trending with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call social_youtube_shorts_trending. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/social/youtube/shorts/trending
MCP method
social_youtube_shorts_trending

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/social/youtube/shorts/trending

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/social/youtube/shorts/trending' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Code example

{}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Social Data

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "social_youtube_shorts_trending",
    "arguments": {}
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can YouTube Trending Shorts provide, and how might I use it?

AI answer

Fetches approximately 48 currently trending YouTube Shorts (viral/popular short-form videos) per call, returning each short's title, URL, thumbnail, view count (views), like count (likes), comment count, publish date, channel info, keywords, and duration. Each subsequent call returns a fresh batch of different trending shorts.

Data categoryDocumented fieldsHow to use them
RequestNo fixed field is promisedProvide the required identifiers, filters, or paging inputs listed in the API document.
Responsedata.data, data.platform, data.resourceStatusInspect returned values and source references; availability depends on the request and upstream source.
  • Review YouTube Trending Shorts.
    • Prompt example: “Retrieve YouTube Trending Shorts. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.”
  • Create a Brief From Returned Text.
    • Prompt example: “Retrieve YouTube Trending Shorts and prepare a brief about [my research question] using only text present in the response. Cite the corresponding source links when returned, distinguish quotations from interpretation, and report insufficient text. Do not claim to have read linked pages or infer private information.”
  • Compare Engagement Counts in a Trending Sample.
    • Prompt example: “Retrieve one batch of trending YouTube Shorts. Make a table of titles, links, views, likes and comments using the numeric counts actually returned, keeping missing counts blank. Rank only this returned sample by [views or likes]; do not describe it as an exhaustive platform ranking or calculate unique viewers.”
  • Build a Short-Form Viewing List.
    • Prompt example: “From one returned trending Shorts batch, select entries within [my duration limit] and show each title, channel, duration and link. Use reported durations, retain unknown lengths separately, and do not infer the video’s spoken content from its title.”

These are suggested workflows, not completed lookups. Report missing, restricted, or partial data explicitly; verify the live response before making a decision.

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

One request fetches one page. Copy nextCursor into cursor, or nextPage into page (1–11 for Reels), then run manually. Repeated requests may purchase data again. Completed lookups have a minimum charge of 10 credits, including cached, no-caption, private, restricted and not-found results. Resource status and actual billing status are independent; null credits are unknown, never free. Check usage.billingStatus, usage.chargedCredits and API usage records for the actual charge.

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/social/youtube/shorts/trending
MCP method
social_youtube_shorts_trending
cURL
curl -X POST \
  https://api.nexscope.ai/social/youtube/shorts/trending \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{}'
Request estimate: Estimating…Usage based. The final charge depends on actual usage. Estimating does not run the API or charge credits.API usage records
Response
No response yet. Run the request to see the response here.

Related APIs