Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

Rumble Comments

social_rumble_video_comments
Read-only

Gets all top level comments for a Rumble video by URL. Returns comment text, author, createdAt, createdAtText, likeCount, dislikeCount, and replyCount when comment bodies are public. If Rumble requires sign-in to view the comments, this endpoint returns HTTP 403 with error forbidden and does not charge credits. This is different from a public video with no comments, which returns a successful empty comments array.

Sign-in-required response example:

{
  "success": false,
  "credits_remaining": 100,
  "credits_charged": 0,
  "error": "forbidden",
  "errorStatus": 403,
  "message": "Rumble requires you to sign in to view this video's comments"
}
``` Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. Rumble Comments API View Pricing Gets all top level comments for a Rumble video by URL. 1 credit per request
Gets all top level comments for a Rumble video by URL. Returns comment text, author, createdAt, createdAtText, likeCount, dislikeCount, and replyCount when comment bodies are public. If Rumble requires sign-in to view the comments, this endpoint returns HTTP 403 with error `forbidden` and does not charge credits. This is different from a public video with no comments, which returns a successful empty comments array.

Sign-in-required response example:
```json
{
  "success": false,
  "credits_remaining": 100,
  "credits_charged": 0,
  "error": "forbidden",
  "errorStatus": 403,
  "message": "Rumble requires you to sign in to view this video's comments"
}

Input Schema

NameRequiredDescriptionDefault
urlYesRumble video URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a read-only, non-destructive, open-world profile, and the description still adds real behavior: which fields are populated only when comments are public, that a 403 is a sign-in wall rather than an error in the call, and that no credits are charged in that case. The value is undercut by conflicting pricing statements ("at least 10 Nexscope credits" vs. "1 credit per request"), which leaves the actual cost ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core description and the entire JSON error example are pasted twice verbatim, and leftover marketing boilerplate ("Rumble Comments API View Pricing") is embedded mid-text. The useful content is front-loaded, but roughly half the text is pure duplication and the pricing lines contradict each other.

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 one-parameter lookup with no output schema, the description does the heavy lifting: it enumerates returned fields, explains the empty-array versus 403 distinction, and shows a concrete error payload. Completeness is only dented by the ambiguous per-request credit cost.

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?

There is a single required parameter with 100% schema description coverage ("Rumble video URL"), so the schema already carries the semantics. The description's "by URL" phrasing adds no new detail about accepted formats, short links, or query parameters, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Gets all top level comments for a Rumble video by URL") and scopes it to top-level comments only, which distinguishes it from the sibling reply/thread and video-detail tools. An agent can tell immediately what data this returns.

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?

It explains how to interpret two outcome states (403 forbidden vs. a successful empty array), which is useful decision context, but it never states when to prefer this over social_rumble_video, social_rumble_video_transcript, or a comments-replies equivalent, nor any prerequisites such as URL format expectations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources