Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baidu_search

Search Baidu's mobile web for normalized result cards (title, URL, snippet, publisher, date) with pagination. Retries on security challenges and returns 503 if all attempts fail.

Instructions

Search Baidu web results. Returns normalized Baidu result cards for a query, read from Baidu's mobile search page: title, destination URL, snippet, publisher, and date, with page-based pagination. Each result's type is web (standard pages), video (video cards), or baike (Baidu Baike encyclopedia entries); answer widgets such as weather, entity panels, and recommendation lists are not returned. Baidu challenges a portion of requests with a security verification page; the service retries across browser profiles and returns 503 if every attempt is challenged, so callers should retry on 503.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based result page; defaults to 1, maximum 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/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 richly: it discloses the returned fields, page-based pagination, the three result `type` values, explicitly which widgets are NOT returned, and the security-verification/503 retry behavior. The error-handling and rate-limit guidance is exactly the kind of operational context an agent needs.

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?

It is dense but front-loaded with purpose before moving into return shape, result types, and failure behavior. Every sentence contributes, though the sentence on result `type` values and the widget exclusion list are somewhat information-heavy for a single paragraph.

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?

There is no output schema, so the description must explain the return shape, and it does: title, destination URL, snippet, publisher, date, plus result types and pagination. Combined with the 503 retry guidance, an agent has everything needed to call and interpret it.

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 `q` and `page` are already documented in the schema. The description adds only a mention of 'page-based pagination,' which is marginal 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?

The description opens with a specific verb+resource: 'Search Baidu web results,' and immediately clarifies it returns normalized result cards from Baidu's mobile search page. This cleanly distinguishes it from other search-engine siblings (yandex_search, bing_search) and from baidu_suggest.

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?

The description describes what the tool returns and its retry-on-503 behavior, giving useful context, but it never states when to use this tool versus alternatives such as baidu_suggest or a different search engine. Usage is implied by the scope rather than explicitly guided.

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