Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get YouTube video

youtube_video_get
Read-onlyIdempotent

Fetch details for a single YouTube video using its URL or 11-character ID to retrieve channel and publish-time metadata.

Instructions

Get a single YouTube video by URL. Requires url. Channel lives under channel (not author); publish time is publishedAt. Pass the video link or 11-character id in url, e.g. {"url":"dQw4w9WgXcQ"}; there is no videoId field.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_video_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the YouTube video. Shorts URLs are also supported.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoOptional preferred language for returned text when the source supports localization.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered and the bar is lower. The description earns credit beyond that by disclosing return-field naming conventions (channel lives under `channel` not `author`; publish time is `publishedAt`), which matters because there is no output schema. It says nothing about pagination-free single-object returns or rate limits, keeping it from a 5.

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?

Three short sentences, front-loaded with the core action and followed by field-naming caveats and a parameter example — no filler. The middle field-naming sentence is telegraphic, but every clause carries information the agent would otherwise get wrong.

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?

With no output schema, the description compensates partially by naming the key returned fields (channel, publishedAt), which is unusually helpful. It does not say what else a video response contains (title, description, statistics) or what happens on invalid/private videos, but the essentials for a correct call are present.

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 coverage is 100%, so a 3 is the baseline, but the description adds real meaning the schema lacks: `url` accepts either a full link or an 11-character video id, and explicitly there is no `videoId` field — a concrete anti-error hint for an agent that would otherwise invent one. It also gives a worked example, though it does not touch the required `context`, `llm_model`, or `conversation_id` parameters.

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 first sentence states a specific verb and resource: fetch one YouTube video by URL. It is easily separated from transcript and comments siblings by name and scope, but it never explicitly contrasts itself with them (e.g. youtube_video_transcript_get for transcripts, youtube_channel_get for channel-level data), so the differentiation stays implicit.

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 implied by 'Get a single YouTube video' — the agent infers it is for metadata about one known video rather than search or listing. There is no explicit when-to-use, no when-not-to-use, and no named alternative, so the agent must reason from the sibling names to route correctly.

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