Skip to main content
Glama
thenavidm

ScrapeCreators MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Comments

rumble_comments

Fetch top-level comments for a Rumble video by URL. Returns text, author, timestamps, like/dislike and reply counts, or a sign-in-required error without charging credits.

Instructions

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

Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesRumble video URL.
accountNoNamed private ScrapeCreators account; selects credentials, not a remote account ID.
confirmNoMust be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark readOnlyHint=false/openWorld/idempotent=false, but the description adds the real behavioral payload: credit consumption, the confirm=true gate, a 403 'forbidden' outcome that charges no credits, and that read-like POSTs do not publish to social platforms. This is exactly the extra context annotations cannot convey.

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?

Front-loads what it does, then return fields, then error semantics, then the illustrative 403 JSON, then the credit/confirm note. Every block earns its place, though the inline JSON example is slightly heavy for the amount of new information it carries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly enumerates the returned fields (comment text, author, createdAt, createdAtText, likeCount, dislikeCount, replyCount) and documents both success and failure shapes. An agent has everything needed to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description reinforces the meaning of confirm (credit-consuming approved call) and ties url to a Rumble video URL. It adds modest interpretive value over the schema's own descriptions.

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, resource, and scope: 'Gets all top level comments for a Rumble video by URL.' The Rumble platform qualifier separates it cleanly from the many sibling comment tools (youtube_comments, instagram_comments, tiktok_comments, facebook_comments) and from rumble_video/rumble_transcript.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: it requires confirm=true, may consume paid credits, and distinguishes the sign-in-required 403 case from a genuinely empty comment set. It stops short of explicitly naming alternatives or when-not-to-use conditions, so it is strong context rather than full routing 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