Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_shorts_trending

Fetch about 48 trending YouTube Shorts in a single call to discover popular clips and surface fresh content ideas; repeat requests can return new Shorts.

Instructions

youtube: Trending Shorts. GET /v1/youtube/shorts/trending. Call it with no arguments. Get about 48 trending Shorts per request. Repeated requests can return new Shorts. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses the per-request volume (~48 items), that results refresh across calls, and a detailed credit-cost model distinguishing success, errors, blocked/timeouts, invalid requests, and cache hits. It stops short of describing the shape of a returned Short or any auth/permission requirement, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the name, route, and invocation rule before the cost detail, and each sentence adds distinct information. The final cost sentence is long, qualifier-heavy boilerplate that could be tightened without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter trending feed with no output schema and no annotations, the definition supplies cost, result volume, and refresh behavior. What is missing is a brief indication of what a returned Short contains, which matters somewhat given there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; the description confirms "no arguments" and that no filtering inputs exist. Nothing more is needed here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"youtube: Trending Shorts" plus the concrete route states the resource and scope unambiguously, and "Get about 48 trending Shorts per request" confirms the action. It does not explicitly contrast itself with channel-scoped siblings like youtube_channel_shorts, leaving that separation to inference from the word "trending".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it with no arguments" tells the agent how to invoke it, and "repeated requests can return new Shorts" implies a polling pattern. There is no explicit statement of when to prefer this over youtube_channel_shorts or youtube_search, so selection guidance remains implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools