Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_search

Search YouTube videos, channels, playlists, Shorts, and live streams by query; filter by type, region, duration, upload date, or sort order to locate relevant content.

Instructions

youtube: Search. GET /v1/youtube/search. Search YouTube videos, channels, playlists, Shorts and live streams. 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": {
      "query": "<query>"
    },
    "name": "youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType of content to search for
queryYesSearch query. Use intitle: for stricter title matching, e.g. intitle:"Foursquare Swarm". YouTube may broaden quoted queries when no fresh exact matches exist.
regionNoTwo-letter country code for the proxy location.
sortByNoSort by
durationNoDuration of the video. Only applies to videos (not shorts).
uploadDateNoUpload date
includeExtrasNoInclude like/comment counts and descriptions; slows the response. Use /v1/youtube/video for full details.
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.2/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 burden. It does well on the billing surface: 1 credit on success, free on errors, blocked, timed-out, invalid requests and cache hits, and a caveat on not-found/empty results. It says nothing about auth requirements, rate limits, result counts, or what a response contains.

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?

Purpose is front-loaded in the first clause, followed by cost semantics. The 'youtube: Search.' prefix plus the raw endpoint line are mildly redundant, and the final not-found billing sentence is wordy, but nothing is superfluous in a harmful way.

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 an 8-parameter search tool with no annotations and no output schema, the description covers purpose and cost but omits return-shape expectations, result-volume behavior, and how pagination results are charged. The schema fills in parameter detail, but the agent still lacks guidance on what comes back and how to route between sibling searches.

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% and all 8 parameters are documented in the schema, including the intitle: syntax and continuationToken semantics. The description adds nothing about parameters, so the baseline of 3 applies.

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 ('Search') and resource (YouTube), then enumerates the content types covered: videos, channels, playlists, Shorts and live streams. It does not distinguish itself from near-by siblings such as youtube_channel_search or youtube_search_hashtag, so an agent cannot tell which to prefer from this text alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only contextual signal is the credit-cost explanation, which affects willingness to call the tool but does not tell the agent how this search differs from other YouTube or social search 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