Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baidu_suggest

Get Baidu search-box autocomplete suggestions for a query prefix, in Baidu's ranking order. Returns up to 10 completions, including Chinese, for keyword research or query expansion.

Instructions

Suggest Baidu search queries. Returns Baidu search-box autocomplete completions for a query prefix, in Baidu's own ranking order. Baidu never returns more than 10 suggestions per prefix; Chinese prefixes are supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query prefix
countNoSuggestions to return; defaults to 10, clamped to 1..10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/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 disclose real behavioral traits: results come in Baidu's own ranking order, Baidu caps suggestions at 10 per prefix, and Chinese prefixes are supported. It omits auth/rate-limit details, but for a read-only suggest endpoint this is solid context beyond the schema.

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?

Three short sentences, front-loaded with the core purpose, and every sentence adds information (ranking order, hard 10-item cap, Chinese support). No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter tool with no output schema and no annotations, the description covers purpose, ranking behavior, result cap, and language support. It could note the return shape (list of strings) more explicitly, but it is nearly complete.

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 both parameters are already documented ('Search query prefix' and the 1..10 clamp). The description reinforces the prefix semantics and the 10-item ceiling but adds no new parameter-level detail, matching the baseline 3.

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?

States a specific verb (suggest) and resource (Baidu search queries / search-box autocomplete completions for a prefix), which is clear and brand-specific. It does not explicitly contrast with siblings like baidu_search or other *_suggest tools, but the verb+resource pairing is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by 'for a query prefix' and 'autocomplete completions', so an agent can infer this is the autocomplete/typeahead tool. However, there is no explicit when-to-use guidance, no when-not, and no named alternative (e.g., baidu_search for full search results).

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