Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

xiaohongshu_search_suggest

Read-only

Fetch anonymous Xiaohongshu search suggestions for a partially typed keyword using a browser-minted signed request; no account or login. Returns the keyword, suggestion list items with text and optional highlight flags/search type, plus the upstream search/word request ids. Only suggestions are returned: search results and profiles require login and are not exposed. The signer is a shared warm-browser worker, so calls are slower than the plain page endpoints; if no signer worker is available the tool reports the upstream 503.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Keyword": "<Keyword>"
    },
    "name": "xiaohongshu_search_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
KeywordYesPartially typed search keyword

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses that no account or login is needed, that requests are signed via a shared warm-browser worker making calls slower than plain page endpoints, and that a missing signer surfaces an upstream 503. These are exactly the operational facts an agent needs to set expectations and interpret failures.

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 the core purpose, then layers return shape, exclusions, and latency/error caveats in a logical order. Dense and mostly waste-free, though the return-field enumeration ('highlight flags/search type, plus the upstream search/word request ids') is slightly more detail than needed given an output schema exists.

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 an output schema present, the description needn't redefine return values, yet it still summarizes them; combined with annotations, latency disclosure, and the 503 failure mode, an agent has everything required to call this correctly and interpret results or errors.

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?

Only one parameter with 100% schema coverage, so the baseline is 3-4; the description adds mild value by framing the input as a 'partially typed' keyword, reinforcing prefix-style input, but adds nothing on length or encoding limits.

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 ('Fetch anonymous Xiaohongshu search suggestions') and scopes it to a partially typed keyword, which cleanly separates it from the content-retrieval siblings like xiaohongshu_note and xiaohongshu_explore. An agent can tell this is an autocomplete tool, not a search tool, from the first clause alone.

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?

Explicitly states the exclusion: 'Only suggestions are returned: search results and profiles require login and are not exposed,' which steers the agent away from expecting content. It implies the when (partial keyword / typeahead) but does not name a sibling tool as the alternative for full content retrieval, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources