deepseek-search-fetch-mcp

Overview Schema Source Related Servers Discussions Admin

search

Run web queries via the DeepSeek API to return structured results with titles, URLs, snippets, summaries, content, dates, authority, and rerank scores; supports advanced query operators.

Instructions

Search the web via the DeepSeek Search API. Returns structured results (title, url, snippet, summary, content, site, date, authority and rerank score). The query supports operators: site:, -site:, "exact phrase", -keyword, lang:zh,en, after:YYYY-MM-DD, before:YYYY-MM-DD.

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": "search"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`query`	Yes
`localization`	No
`need_content`	No
`ori_question`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about authentication, rate limits, cost, latency, result caps, or error behavior. The enumeration of result fields describes output shape rather than behavior, and that shape is already covered by the output schema.

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?

Two dense sentences with the core purpose front-loaded and no filler. The result-field enumeration (title, url, snippet, summary, content, site, date, authority, rerank score) is somewhat wasted space given an output schema already exists.

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

Completeness2/5

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

For a five-parameter tool with zero annotation coverage and no schema descriptions, the definition leaves too much unresolved: four parameters are undocumented, and nothing explains defaults or how results are ranked or paginated. The output schema excuses return-value explanation, but not the input-side gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must document five parameters; it only meaningfully covers 'query' via the operator list. 'count', 'localization', 'need_content', and 'ori_question' are never explained, leaving four of five parameters opaque to the agent.

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 and resource: 'Search the web via the DeepSeek Search API'. The purpose is unmistakable and separable from the sibling 'fetch', though it never explicitly contrasts the two (search for discovery vs. fetch for a known URL).

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and the sibling 'fetch' is never mentioned, so an agent must infer that this is the discovery tool and fetch is for retrieval of a known resource. The operator syntax is helpful but is search syntax, not usage policy.

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

fetchA
searchC