Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Rumble

rumble_search_list
Read-onlyIdempotent

Search Rumble videos and Shorts by keyword to find relevant content and return a paginated list for browsing or research.

Instructions

Search Rumble for videos and Shorts by keyword. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "rumble_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query text for Rumble content.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile needs no restating. The description adds only the list-shaped return and cursor pagination hint, saying nothing about result limits, rate limits, or the conversation_id sequencing constraint that the schema flags.

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 purpose and with no filler. "Requires query" mildly duplicates the schema's required list, costing a sliver of efficiency.

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 search tool with full schema coverage, no output schema, and annotations covering the safety profile, the description gives the essentials. The one notable omission is the conversation_id echo/sequential-call rule, which is a non-obvious operational constraint left entirely to the schema.

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 coverage is 100%, so every parameter is already documented, and the description adds no syntax, format, or constraint detail beyond restating that query is required. Baseline 3 applies when the schema carries the semantic load.

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 gives a specific verb and resource ("Search Rumble for videos and Shorts by keyword") and names the content types covered, which separates it from retrieval siblings like rumble_video_get. It stops short of explicitly contrasting itself with rumble_channel_videos_list or other Rumble tools, so it is clear but not fully differentiated.

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?

Keyword-search intent is implied by "Search ... by keyword," and the cursor note gives light pagination guidance ("use cursor when paginated"). However, there is no explicit statement of when to prefer this over channel- or video-level siblings, nor any prerequisite or exclusion 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