Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rednote_note

Fetch public Rednote note details anonymously from a note URL or ID and return normalized JSON with media, text, tags, author, and engagement counters.

Instructions

Anonymous Rednote note detail. Returns one public Rednote note's normalized detail by rendering the note page in a warm anonymous browser and reading the page's own server-rendered noteDetailMap. No account, login, or note token is required: pass a rednote.com /discovery/item/ or /explore/ URL. Returns note id, media type, title, description text, topic tags, image URLs, an optional video URL with duration, publish time, a public author card, and integer like/collect/comment/share counters. A login modal may be drawn over the page but the note state is still populated. If the note is removed or the page does not expose its state, the endpoint returns 404; if no browser page can be warmed it fails closed with 503.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/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 burden and does so well: it discloses the anonymous warm-browser rendering approach, that a login modal may overlay the page while state is still populated, and explicit 404 and 503 failure semantics. This is exactly the behavioral context an agent needs before calling.

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-loaded with purpose, then mechanism, inputs, and return fields; every sentence is informational. It is dense and slightly long due to the full enumeration of returned fields, but nothing is filler.

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?

With no output schema and no annotations, the description still documents the return shape (id, media type, title, text, tags, media URLs, author card, counters), the auth-free access model, and the error cases. An agent has everything needed to call it and interpret outcomes.

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 coverage is 100%, so the url and note_id parameters are already documented in the schema. The description restates the accepted URL forms but adds no format or precedence detail (url vs note_id) beyond the schema, so the 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 ('Returns one public Rednote note's normalized detail') and even names the underlying mechanism (server-rendered noteDetailMap). An agent can distinguish this note-detail tool from rednote_explore or rednote_note_comments without opening a schema.

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?

Explains input prerequisites clearly ('No account, login, or note token is required: pass a rednote.com /discovery/item/<id> or /explore/<id> URL'), giving strong context for when this applies. It does not explicitly say to use rednote_explore/search to obtain a note id first, so there is a small gap versus full alternative routing.

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