Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

get_video_metadata

Retrieve metadata for a YouTube video, including title, description, views, and likes, by supplying its 11-character video ID.

Instructions

Get metadata for a YouTube video (title, description, views, likes, etc.).

Args: video_id: YouTube video ID (11 characters)

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": {
      "video_id": "<video_id>"
    },
    "name": "get_video_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Get' implies a read, but it says nothing about API quota cost, auth requirements, or what happens for private/deleted/region-blocked videos, all of which are real failure modes for this resource.

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

Conciseness5/5

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

Two lines, front-loaded with the purpose, then a focused Args note. Every sentence earns its place and nothing is padded.

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?

An output schema exists, so return fields need not be explained. With one documented parameter, the essentials are covered, but the absence of any behavioral context (quota, errors, ID provenance) leaves the definition merely adequate for a networked getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema alone says nothing about video_id. The description compensates by naming the parameter and adding a real constraint — it must be an 11-character YouTube video ID — which is meaningfully more than the bare schema provides.

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-resource pair ('Get metadata for a YouTube video') and enumerates the returned fields (title, description, views, likes), which makes it distinguishable from siblings like get_transcript or get_comments. It stops short of explicitly contrasting itself with those siblings.

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 guidance on when to prefer this over get_chapters, get_transcript, or search_videos, nor any stated prerequisites (e.g., the ID must come from a search result). Usage is only implied by the tool name.

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