Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitch clip

twitch_clip_get
Read-onlyIdempotent

Retrieves metadata and playback URLs for a Twitch clip from its link, so you can inspect clip details or embed and play the video directly.

Instructions

Get metadata and playback URLs for a Twitch clip by URL. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Twitch clip.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds only that the return includes metadata and playback URLs, which is genuinely useful, but it omits failure modes (deleted clips, region locks) and whether multiple playback qualities are returned.

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 short sentences with the resource and input requirement front-loaded and zero filler. Nothing could be removed without losing information.

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 simple read-only lookup with full schema coverage and complete annotations, the definition covers purpose and required input adequately. The remaining gap is that no output schema exists, and the description only gestures at the response shape ('metadata and playback URLs') without saying which fields or whether multiple quality variants come back.

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%, with url, context, llm_model and conversation_id each documented in the schema itself, so the schema carries the parameter burden. The description restates only that url is required, adding no syntax or format detail (e.g., clip URL patterns or slugs) beyond the schema's 'Link to the Twitch clip.'

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 names a specific verb (get) and resource (Twitch clip metadata and playback URLs), and the platform qualifier 'Twitch' implicitly separates it from the kick_clip_get sibling. It does not explicitly contrast with that sibling, which keeps it below 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 Guidelines3/5

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

'By URL' with the explicit 'Requires `url`' statement tells the agent the accepted input form, which is a real usage constraint. However, there is no when-to-use versus when-not guidance, no mention of alternatives such as kick_clip_get, and no note about behavior on expired or private clips.

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