Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_search_typeahead

Fetch live YouTube search autocomplete suggestions for a partial or complete query to reveal what users see in the search dropdown.

Instructions

youtube: Search Typeahead. GET /v1/youtube/search/typeahead. Get the live autocomplete suggestions shown in YouTube's search dropdown. 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_typeahead"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPartial or complete YouTube search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the GET endpoint and a detailed cost model (1 credit on success; errors, blocked/timeout, invalid requests and cache hits are free). It stops short of describing rate limits or the shape of the returned suggestions, but the charging behavior is unusually well disclosed.

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 one sentence, followed by the endpoint and cost rules. The cost sentences are slightly verbose with their list of failure cases, but each clause conveys real billing information rather than filler.

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 single-parameter read tool this covers what it returns conceptually, the endpoint, and billing behavior. The remaining gap is that no output schema exists and the description does not say how suggestions are structured or ordered, which would help an agent parse the response.

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?

Only one parameter, and schema coverage is 100% with the schema already saying 'Partial or complete YouTube search query' and giving an example. The description adds no syntax, length, or language guidance beyond that, so baseline 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 and resource: 'Get the live autocomplete suggestions shown in YouTube's search dropdown.' That is clearly distinct from a full youtube_search, though the description never names the sibling it differs from, so differentiation is implied rather than explicit.

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?

The phrase 'live autocomplete suggestions' implies the use case (query completion/typeahead) but there is no explicit when-to-use, when-not-to-use, or named alternative such as youtube_search for actual results. Usage is inferable, not stated.

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