Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xiaohongshu_explore

Anonymous Xiaohongshu explore/channel feed. Returns one page of the anonymous Xiaohongshu explore feed as normalized note cards: note id, a ready-to-call note_url carrying its short-lived xsec_token, type, title, cover image, like count…

Instructions

Anonymous Xiaohongshu explore/channel feed. Returns one page of the anonymous Xiaohongshu explore feed as normalized note cards: note id, a ready-to-call note_url carrying its short-lived xsec_token, type, title, cover image, like count, and a public author card. Omit channel_id for the upstream default recommendation feed; use channel_id with an id from the channels list returned by this endpoint for a category feed. The upstream serves one server-rendered page per channel (typically 20-33 cards) and has no credential-free cursor, so there is no pagination. Search, user profiles, comments, and note detail without a feed token are not available on this anonymous surface. The xsec_token in note_url is short-lived; call /xiaohongshu/note promptly with the returned note_url, and re-run this endpoint for a fresh token when it expires.

Input Schema

NameRequiredDescriptionDefault
channel_idNoOptional explore channel id from the channels list in a previous response. Unknown values are rejected; omit for the default feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses anonymous access, one server-rendered page per channel with typical card counts, absence of pagination, short-lived xsec_token behavior, and the unavailable surfaces. This gives an agent the operational constraints needed before calling the tool.

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

Conciseness5/5

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

The description is front-loaded with purpose and return shape, followed by parameter usage, pagination limits, unavailable surfaces, and token handling. Every sentence contributes operational information, and there is no redundant or filler text.

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?

For a feed tool with no output schema and no annotations, the description supplies the return card fields, pagination behavior, parameter semantics, token lifecycle, and explicit limitations. Nothing an agent needs to invoke it correctly or interpret its result appears to be missing.

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 description coverage is 100%, so the schema already documents the single optional channel_id parameter. The description adds meaningful context beyond the schema by explaining that unknown values are rejected, that the id comes from the channels list returned by this endpoint, and that omission selects the upstream default feed.

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?

The description states a specific verb+resource: it returns the anonymous Xiaohongshu explore/channel feed as normalized note cards. It also distinguishes this feed tool from unavailable surfaces like search, user profiles, comments, and note detail, making the tool's scope clear without needing to inspect siblings.

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

Usage Guidelines5/5

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

It explicitly explains when to omit channel_id for the default recommendation feed, when to supply a channel_id from the channels list, and that there is no pagination due to the lack of a credential-free cursor. It also routes the agent to the correct follow-up endpoint by instructing prompt use of note_url before the xsec_token expires.

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