deepseek-search-fetch-mcp

Overview Schema Source Related Servers Discussions Admin

fetch

Retrieve a single web page from an absolute HTTP/HTTPS URL and return its title and full Markdown content for reading or analysis.

Instructions

Fetch a single web page via the DeepSeek Fetch API and return its title and full content in Markdown. The URL must be an absolute HTTP/HTTPS URL with a host and must not contain embedded credentials.

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": {
      "url": "<url>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the backing API and that output is a title plus full Markdown body, but says nothing about rate limits, authentication, payload size limits, timeouts, or what happens on unreachable pages or non-HTML content.

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?

Two sentences, front-loaded with the action and the return value, followed by the input constraint. Every clause carries information; no filler.

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 one-parameter read tool with an output schema, the description covers purpose, return shape, and input validity, which is nearly sufficient. Remaining gaps are operational: failure modes, size ceilings, and any access restrictions on fetched pages.

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 0%, so the description must compensate, and it does: it defines the required URL as absolute HTTP/HTTPS with a host and forbids embedded credentials. That adds real validation meaning beyond the bare 'url: string' schema, though it doesn't mention encoding or query/fragment handling.

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?

The description gives a specific verb (fetch) and resource (a single web page) and specifies the return payload (title and full content in Markdown). It contrasts implicitly with the sibling 'search' by emphasizing 'a single web page', but never names the sibling, so differentiation is left to inference.

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?

No explicit when-to-use or when-not-to-use guidance and no reference to the 'search' sibling, so an agent must infer that this tool is for one known URL rather than discovery. It does supply hard usage constraints — absolute HTTP/HTTPS, host required, no embedded credentials — which is genuine eligibility guidance.

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