Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

search_videos

Search YouTube videos by query and return a configurable number of results for AI assistant research and content discovery.

Instructions

Search YouTube videos.

Args: query: Search query string limit: Number of results (default 5, max 50)

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": "search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/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, yet it says nothing about result ordering, relevance ranking, quota/auth requirements, or whether the search is global or scoped. An output schema exists, which relieves it of describing the return shape, but the behavioral profile of the call remains undisclosed.

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 sentence is front-loaded and the args block is tight with no wasted prose. The docstring-style formatting is slightly more verbose than a single sentence would be, but every line carries information.

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 simple two-parameter search with an output schema, the essentials are present: what it searches, the required query, and the limit bounds. It is still thin on how results are selected or ordered, which matters for an agent deciding between this and channel-listing tools.

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 0%, so the description must compensate. It does document both parameters and supplies the max of 50, which the schema does not carry, but "Search query string" adds little beyond the parameter title and nothing about query syntax or matching behavior.

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 gives a clear verb+resource: "Search YouTube videos." An agent immediately knows this is a keyword search over video content. It does not differentiate from siblings such as list_channel_videos, so it stops short of 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 Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives; the sibling list contains channel-scoped listing tools, but the description never says whether to prefer this for keyword search vs. those for enumeration. The agent must infer that from the tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.