Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rednote_search_suggest

Fetches anonymous Rednote search suggestions for a partially typed keyword, returning suggested text, highlight flags, and search type without account login.

Instructions

Anonymous Rednote search suggestions. Returns search suggestions for a partially typed keyword using a browser-minted signed request against Rednote's web API. Suggestions are anonymous and need no account or login; each item carries the suggested text plus optional highlight flags and the suggestion's search type. Only the suggestion list is returned: Rednote search results require a logged-in session and are not exposed. 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 the endpoint fails closed with 503.

Input Schema

NameRequiredDescriptionDefault
keywordYesPartially typed search keyword

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 burden and does so well: it discloses the signing requirement (browser-minted signed request via a shared warm-browser worker), that no auth is required, the per-item return shape (text, optional highlight flags, search type), elevated latency, and the fail-closed 503 behavior when no signer is available.

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 the definition, then scope, output, and latency/failure notes in order of usefulness. Every sentence carries information, though the signer/latency sentence is denser than needed and could be split.

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 single-parameter read tool with no annotations and no output schema, the description covers purpose, auth, return shape, latency, and failure mode — everything an agent needs to decide to call it and to interpret the result.

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% and there is a single required parameter, so the schema already documents `keyword` as a partially typed search keyword. The description's phrasing mirrors rather than extends the schema, which is the expected baseline-3 outcome when structured data does the work.

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 first two sentences give a precise verb (returns search suggestions) and resource (Rednote's autocomplete endpoint) for a specific input ('partially typed keyword'). It also carves out of scope what it is not ('Rednote search results ... are not exposed'), though a near-identical sibling (xiaohongshu_search_suggest / rednote_explore) is never named to disambiguate.

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?

Usage context is clear: call it with a partially typed keyword, no account or login needed. The exclusion of full search results is stated explicitly. What's missing is an explicit 'use this instead of X when Y' routing statement against the large family of sibling suggest/search tools.

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