Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Rumble video transcript

rumble_video_transcript_get
Read-onlyIdempotent

Retrieve captions for a Rumble video from its URL when available, enabling transcript review and analysis.

Instructions

Get captions for a Rumble video when available. 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": "rumble_video_transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Rumble video.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the conditional 'when available', signaling that results may be empty — a real behavioral detail beyond the annotations — but says nothing about the returned caption format or error behavior.

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, front-loaded with the purpose. The 'Requires `url`' clause is largely redundant given the schema marks url required and lists it first, keeping it just short of a 5.

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?

The tool has 3 required parameters (including analytics and conversation-sequencing params) and no output schema, so the description carries the burden of describing the return value — caption text format, segmentation, or what happens when captions are absent. That gap leaves it only minimally adequate for a transcript-extraction tool.

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 all documented in-schema, so the baseline is 3. The description's 'Requires `url`' merely repeats a schema fact rather than adding syntax or format detail.

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 captions for a Rumble video.' An agent can distinguish it from rumble_video_get (metadata) by the word 'captions', though it does not explicitly name the sibling. The slight mismatch between 'captions' in the description and 'transcript' in the name/title is not resolved.

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?

'when available' hints at the precondition that captions may not exist, which is genuinely useful. However, no alternative is named for the failure case (e.g., rumble_video_get or a different caption source), and there is no explicit when-not guidance.

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