Skip to main content
Glama

baidu_search

Scrape Baidu search engine results pages with support for search operators, localization, and pagination controls.

Instructions

Scrape Baidu search engine results pages. Supports Baidu search operators (inurl:, site:, intitle:, etc.) and localization/pagination controls. [Credits: 5 API credits per successful request] Notes: Pagination is offset-based via pn (0, 10, 20, ...) combined with rn (page size, max 50, default 10). Localization is controlled via ct for Chinese script variant. Advanced filters (q5, q6, bs, oq, f, gpc) mimic Baidu's native search operators/URL parameters for finer targeting. Returns: { Baidu_data: [ { title, link, snippet, rank } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fNoSource of the search. E.g., 8 = standard search, 3 = from suggestion list, 1 = from related search.
bsNoSpecifies the preceding search query.
ctNoLanguage restriction. Allowed values: 1 = All languages, 2 = Simplified Chinese, 3 = Traditional Chinese.
oqNoIndicates the original search query when the user arrives via a related search.
pnNoResult offset for pagination. 0 = first page, 10 = second page, 20 = third page, etc.
q5NoFunctions like inurl: or intitle:. Use 1 to search by page title, 2 to search by URL.
q6NoFunctions like site: (e.g., q6=scrapingdog.com).
rnNoMaximum number of results to return. Maximum value is 50. (default: 10)
gpcNoTime range filter for results, specified using Unix timestamps.
htmlNoReturn the full HTML of the Baidu page instead of parsed JSON. (default: false)
queryYesSearch query. Supports Baidu search operators such as inurl:, site:, intitle:, etc.
Behavior5/5

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

No annotations provided, but the description compensates fully. It discloses credit cost (5 API credits), pagination behavior (offset-based via pn/rn), localization (ct parameter), advanced filters (mimicking Baidu operators), and the ability to return HTML instead of parsed JSON. This is rich behavioral context.

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 concise (4 sentences) and well-structured: purpose, cost, pagination, localization, advanced filters, return format. Every sentence provides essential information with no redundancy.

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?

Despite no output schema, the description specifies the exact return format (Baidu_data array with title, link, snippet, rank). With 11 parameters and complex behavior (pagination, localization, operators), the description covers all key aspects, making it complete for selecting and invoking the tool.

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 each parameter has a description. The tool description adds value by grouping parameters (q5, q6, bs, oq, f, gpc) as 'advanced filters' and explaining their combined purpose, and clarifying pagination semantics. This synthesizes usage context beyond individual schema descriptions.

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 clearly states 'Scrape Baidu search engine results pages' with specific verb+resource, and supports Baidu-specific search operators. It distinguishes itself from sibling search tools (e.g., google_search, bing_search) by being Baidu-specific.

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?

The description gives clear context on when to use the tool (for scraping Baidu results) and details pagination/localization settings, but does not explicitly state when not to use it or compare to alternatives. The sibling list includes many search tools, so the name and description sufficiently differentiate it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server