rumble_channel_videos_listList videos and Shorts from a Rumble channel. Accepts a channel URL. Returns a list (use cursor when paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Link to the Rumble channel. | |
| cursor | No | Page number from a previous response. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat that. It adds extra behavioral context by noting pagination with a cursor, which is not covered by annotations. This is a useful addition beyond the schema.
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?
The description is two sentences with no fluff. It front-loads the purpose and immediately adds the key pagination note. Every word earns its place; no unnecessary detail.
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 listing tool with read-only and open-world annotations, the description covers the essential aspects: what it lists, input required, and pagination behavior. It doesn't mention output format, but that's not required without an output schema. It's complete enough for an agent to call correctly.
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 coverage is 100%—both url and cursor have descriptions. The description adds minimal semantic value by reiterating that a channel URL is accepted and cursor is for pagination, which the schema already implies. It doesn't go beyond the schema but doesn't conflict. Baseline 3 is appropriate.
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 clearly states the verb 'List' and the resource 'videos and Shorts from a Rumble channel'. It also notes the input (channel URL) and the output behavior (returns a list). This distinguishes it from sibling tools like rumble_search_list or rumble_video_get by targeting channel-level video listing.
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 does not explicitly state when to use this tool over alternatives or when not to use it. It implies usage (when you want to list all videos from a specific channel), but no exclusions or comparison are given. Sibling names like youtube_channel_videos_list suggest similar tools, but no routing guidance is provided.
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.