Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rednote_note_comments

Fetch public Rednote note comments anonymously via signed web API requests. Pass a note URL or ID to get comment text, counters, author cards, replies, and pagination cursors without login.

Instructions

Anonymous Rednote note comments. Returns one page of a public Rednote note's comments using a browser-minted signed request against Rednote's web API, with no account or login. Pass a rednote.com /discovery/item/ or /explore/ note URL; an xsec_token is accepted but not required for comments. Each item includes the comment id, text, like/sub-comment counters, creation time, IP location when exposed, a public author card, and up to five replies; has_more and cursor continue pagination. The request is signed by a shared warm-browser worker, so latency is higher than a plain feed read; when no signer worker is available or the upstream refuses the signed session the endpoint fails closed with 503.

Input Schema

NameRequiredDescriptionDefault
urlNoRednote note URL (/discovery/item/<id> or /explore/<id>; xsec_token optional). Pass url or note_id.
cursorNoPagination cursor from a previous response
note_idNo24-character hex note id (alternative to url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses anonymous access with no login, signed browser-worker requests, higher latency, fail-closed 503 behavior, and the shape of returned comment data including pagination.

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?

The description is front-loaded with purpose and efficiently includes return fields, pagination, and failure behavior. It is somewhat dense and repeats the signing concept, but most sentences earn their place.

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 and no annotations, so the description must compensate. It does: it lists returned comment fields, pagination controls, and the 503 failure mode, leaving little ambiguity for an agent calling this tool.

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 description coverage is 100%, so the schema already defines url, cursor, and note_id. The description adds little beyond the schema: it restates URL forms and optional xsec_token but does not clarify note_id or cursor semantics beyond what is already documented.

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 clearly states the verb and resource: it returns one page of a public Rednote note's comments. It also scopes the result to comments rather than note content, but it does not explicitly differentiate this tool from sibling note or comment tools.

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?

The description explains how to invoke it with a Rednote note URL and notes that xsec_token is optional. It also explains cursor-based pagination, but it gives no explicit when-to-use/when-not-to-use guidance against alternatives such as rednote_note.

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