Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get YouTube channel

youtube_channel_get
Read-onlyIdempotent

Fetch YouTube channel details by ID, handle, or URL and return channel metrics and identifiers for building snapshot baselines.

Instructions

Get YouTube channel details by channel id, handle, or URL. Optional inputs: channelId, handle and url. Returns channel metrics and identifiers for snapshot baselines.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional YouTube channel URL for the request.
handleNoOptional YouTube channel handle for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
channelIdNoOptional YouTube channel id for the request.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results include channel metrics and identifiers, but it never explains precedence when multiple identifiers (channelId, handle, url) are supplied simultaneously or what happens on a lookup miss — a real gap for a tool with three overlapping lookup keys.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence largely duplicates schema content, which is the only wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a four-field lookup schema, a rich annotations block and no output schema, the definition supplies what an agent needs to call it correctly: the action, the three identifier options, and the shape of the return (metrics plus identifiers). Missing precedence rules among the identifiers and the absence of an output schema are the only residual gaps, and the annotations carry the safety burden.

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%, so the baseline is 3. The description's sentence listing the optional inputs merely restates what the schema already documents and adds no precedence or format detail beyond it.

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 YouTube channel details") and enumerates the three identifier forms accepted (id, handle, URL), so an agent knows what the tool retrieves. It does not distinguish itself from sibling channel getters (kick_channel_get, vimeo_channel_get, etc.), but the platform is unambiguous in the name.

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 or when-not-to-use guidance and no reference to alternatives such as youtube_channel_search_list for resolving a channel. The phrase "for snapshot baselines" hints at an intended use case but is too terse to route an agent between this tool and its 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