Skip to main content
Glama
Sign In
scrapingdog-mcp

scrapingdog-mcp

by 0pen1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

baidu_search

Run Baidu searches and get parsed JSON results, with support for Chinese-language filtering, pagination, and result count control.

Instructions

Run a Baidu search via Scrapingdog (/baidu/search). Returns parsed results as JSON. Supports Chinese-language restriction (ct), pagination (pn), and result count (rn).

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": {
      "query": "<query>"
    },
    "name": "baidu_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctNoLanguage restriction: 1 = all, 2 = Simplified Chinese, 3 = Traditional Chinese.
pnNoResult offset for pagination. 0 = first page, 10 = second, 20 = third, etc.
rnNoMaximum number of results to return.
htmlNoReturn the full raw HTML of the Baidu results page.
queryYesThe Baidu search query. Supports inurl:, site:, intitle: operators.
api_keyNoOverride the configured Scrapingdog API key for this call. If omitted, the key is read from SCRAPINGDOG_API_KEY or a local .env file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It does disclose that calls go through Scrapingdog and that results are returned as parsed JSON, and it highlights key options. However, it omits authentication requirements, rate-limit or cost implications, and behavior when the 'html' parameter is true.

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 two concise sentences that front-load the core action and return format, then list the important supported options. There is no fluff or repetition, and every sentence earns its place.

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

Completeness3/5

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

For a simple search tool with a fully documented input schema, the description is mostly adequate. However, because there is no output schema and no annotations, it only vaguely promises 'parsed results as JSON' without describing the structure of those results or error behavior, making it complete enough but not thorough.

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?

The input schema already documents all six parameters with 100% coverage, so the baseline is 3. The description adds little beyond restating that ct handles Chinese-language restriction, pn handles pagination, and rn handles result count—details already present in the schema.

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 'Run' and clearly identifies both the tool ('a Baidu search') and the implementation endpoint ('via Scrapingdog (/baidu/search)'). It also states the return type ('parsed results as JSON') and the tool's name distinguishes it from sibling search engines like google_search and bing_search.

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 implies the tool is for Baidu searches, but it does not explicitly contrast it with sibling tools such as google_search, bing_search, or duckduckgo_search. It provides no alternative recommendation, exclusion criteria, or conditions for when Baidu should be used over other engines.

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