Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_community_post

Retrieves details of a YouTube community post using its URL, so you can inspect post content and metadata without manual lookup.

Instructions

youtube: Community Post Details. GET /v1/youtube/community-post. Get the details of a community post 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "youtube_community_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the YouTube community post to get

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real cost semantics: 1 credit on success, nothing for errors, blocked, timed-out, invalid, or cached requests. However, it says nothing about permissions, response contents, or rate limiting, so significant behavioral ground is uncovered.

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 purpose is front-loaded in the first two clauses and the cost caveat is short. The leading "youtube: Community Post Details. GET /v1/youtube/community-post." duplicates the name and adds billing boilerplate that is generic across the API, which is minor waste.

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 one-parameter read tool with full schema coverage and no output schema, the essentials are present. Still, an agent cannot tell what "details" a community post returns (text, author, engagement counts), which is the one thing the description could have covered since no output schema exists.

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?

There is a single parameter with 100% schema description coverage that already states it is the URL of the community post. The description adds no format guidance, URL-shape constraints, or examples beyond the schema's own example.

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 states a specific verb and resource ("Get the details of a community post") and names the underlying endpoint, so the singular post-fetch is legible. It does not explicitly distinguish itself from the sibling list tool youtube_channel_community_posts, which keeps it from a 5.

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?

Usage is only implied by the required URL: fetch one post's details. There is no statement about when to prefer this over youtube_channel_community_posts or other post tools, and no preconditions or exclusions are given.

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