Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Rumble channel videos

rumble_channel_videos_list
Read-onlyIdempotent

Retrieve videos and Shorts from a Rumble channel by URL, then use the returned cursor to page through additional results.

Instructions

List videos and Shorts from a Rumble channel. Requires url. Returns a list (use cursor when paginated).

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_channel_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Rumble channel.
cursorNoPage number from a previous response.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two useful facts beyond that: the result is a list including Shorts, and pagination is cursor-based. It says nothing about rate limits, empty channels, or ordering.

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 resource stated first and the operational note second; nothing is wasted. It is arguably over-terse for a five-parameter tool, but there is no filler or repetition.

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?

For a read-only paginated list tool with full schema coverage and no output schema, the description covers the essentials: what it returns and how to page. It omits the conversation_id echo handshake and any expectation about response shape, which are handled in the schema but not reinforced here.

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 schema fully documents url, cursor, context, llm_model and conversation_id, and the baseline of 3 applies. The description only echoes that url is required and cursor is for pagination, adding no format or behavior detail beyond the schema.

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?

"List videos and Shorts from a Rumble channel" gives a specific verb (list) and resource (channel videos/Shorts) scoped to the Rumble platform, so an agent can separate it from rumble_search_list or rumble_video_get. It stops short of naming a sibling explicitly, which keeps it out of the top band.

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?

The only guidance is "Requires `url`" and "use cursor when paginated," both of which restate the schema. There is no statement of when this tool is preferred over rumble_search_list, rumble_video_get, or the other platform channel-video siblings, and no exclusions or prerequisites.

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