Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel_shorts

Retrieve a YouTube channel's Shorts by channel ID or handle, sort by newest or popular, and use continuation tokens to page through results.

Instructions

youtube: Channel Shorts. GET /v1/youtube/channel/shorts. Provide one of: channelId, handle, continuationToken. Get channel Shorts. publishDate is an ISO 8601 timestamp with an offset when available, otherwise null; date-only values are not returned. 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_channel_shorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by newest or popular
handleNoYouTube channel handle. Provide handle or channelId.
channelIdNoYouTube channel ID. Provide channelId or handle.
continuationTokenNoUse continuationToken from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 substantial work: it discloses the credit cost on success, that errors/blocked/timed-out/invalid/cache-hit requests are free, pagination via continuationToken, and publishDate formatting/nullability rules. It still omits auth requirements, rate limits, and any sense of response shape, which keeps it below a 5.

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?

The identity and addressing requirements are front-loaded and the whole thing is a short paragraph with no filler. The trailing pricing sentence about not-found/empty results is self-referential ('where that operation's published cost says so') and costs more words than it delivers.

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

Completeness3/5

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

For a no-annotation, no-output-schema tool, the description covers cost, entry conditions, and pagination reasonably well. It leaves the return payload entirely undescribed and says nothing about the sort parameter, so an agent still cannot predict what the response will contain beyond a publishDate field.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented, including the handle/channelId alternatives. The description's 'provide one of' phrasing reinforces the one-of addressing constraint but adds nothing about the sort parameter's behavior or default.

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?

States a specific verb and resource: 'Get channel Shorts' plus the endpoint GET /v1/youtube/channel/shorts, scoped to a single channel via channelId/handle. It is clearly distinguishable from a channel-wide listing, though it never explicitly contrasts with youtube_shorts_trending or youtube_channel_videos.

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?

'Provide one of: channelId, handle, continuationToken' gives the required addressing modes and implies pagination via continuationToken. However, there is no explicit when-to-use guidance versus youtube_shorts_trending or youtube_channel_videos, and no statement of when this call is inappropriate.

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