Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel_community_posts

Fetch community posts from a YouTube channel using a channel ID or handle, with continuation tokens to page through results.

Instructions

youtube: Channel Community Posts. GET /v1/youtube/channel/community-posts. Provide one of: channelId, handle, continuationToken. Get community posts from a YouTube channel. Can pass channelId or handle. 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_community_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoYouTube channel handle
channelIdNoYouTube channel ID
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

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the billing model in detail (1 credit on success, free for errors/blocked/timeouts/invalid/cache hits) and implies a read-only GET, but it says nothing about authentication requirements, rate limits, or how pagination terminates beyond the presence of a continuation token.

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

Conciseness3/5

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

The route and purpose are front-loaded, which is good, but the parameter constraint is stated twice ('Provide one of...' then 'Can pass channelId or handle') and the final two sentences of billing boilerplate are wordy and partly redundant. Roughly a third of the text is pricing fine print rather than invocation guidance.

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?

With only three well-documented parameters and no output schema, the description covers enough to call the tool, and the cost model is a bonus. It still leaves the agent guessing about how to detect the next page beyond the mention of continuationToken, and about whether an empty list is a normal outcome or an error.

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%, including an example handle ('NASA') and an explanation of the continuationToken, so the baseline is 3. The description only restates the one-of constraint for the three parameters and adds no new meaning such as token expiry or whether channelId and handle can be combined.

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?

The description names a specific resource and verb ('Get community posts from a YouTube channel') and even gives the underlying route 'GET /v1/youtube/channel/community-posts', so the agent knows exactly what the tool returns. It does not explicitly distinguish itself from the sibling 'youtube_community_post' (singular), which fetches a single post, so sibling differentiation is only implicit.

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?

It states the input requirement 'Provide one of: channelId, handle, continuationToken' and repeats 'Can pass channelId or handle', which is useful identifier guidance. However, it gives no guidance on which identifier to prefer, no when-not-to-use conditions, and no routing to alternatives such as the single-post or other channel-listing siblings.

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