rumble_search_listSearch Rumble for videos and Shorts by keyword. Returns a list (use cursor when paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query text for Rumble content. | |
| cursor | No | Page number from a previous response. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations assert readOnlyHint and openWorldHint, covering safety. The description adds that it returns a list and mentions cursor-based pagination, which goes beyond annotations. However, it does not describe the list item structure, error behavior, or rate limits, so it only partially enriches the behavioral picture.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One concise sentence that front-loads the core purpose and includes a critical operational detail (pagination) without any filler. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only search with two well-documented parameters, the description covers the essentials: what it searches, that it returns a list, and pagination guidance. However, without an output schema, it does not explain what fields the returned list contains or any sorting/filtering nuances, leaving a moderate gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both query and cursor are already documented. The description reinforces that query is a keyword and implies pagination via cursor, but adds little beyond the schema. Baseline of 3 is appropriate because the schema handles parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Search), a specific resource (Rumble videos and Shorts), and a keyword basis. This clearly distinguishes it from sibling Rumble tools like rumble_channel_videos_list or rumble_video_get, and from similar search tools on other platforms.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a pagination usage hint ('use cursor when paginated') but does not explicitly state when to use this tool versus alternatives like rumble_channel_videos_list for channel-specific content. The usage context is implied by the tool name and platform, but exclusions are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.