Skip to main content
Glama
DeepSeek Search Everywhere MCP

DeepSeek Search Everywhere MCP

deepseek_fetch

Read-onlyIdempotent

Read a known web page as clean Markdown and use optional selectors to return only relevant sections, snippets, or paging ranges.

Instructions

Read one web page as clean Markdown, or only the part of it you need.

Use it when you already know the URL. Flat $0.00075 per call; up to 20,000 chars by default (max_chars). One optional selector narrows the text: section=, query= (relevant excerpts, no LLM), offset=/limit= (paging) or find_text=. A 404 on a PDF or Reddit URL falls back to the search index. Content is sanitized (images neutralized, hidden text stripped).

When NOT to use: finding pages by topic (deepseek_search), several URLs (deepseek_fetch_many), fields as JSON (deepseek_extract), or a multi-source answer (deepseek_research).

Returns: {"ok": True, "url": str, "title": str, "content": str, "truncated": bool, "cost_usd": float, "notes": [...]}.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTP or HTTPS URL to fetch (must be public, no private IP/intranet)
cleanNoRemove Markdown backslash escapes from the page text (default True)
limitNoMax characters to return from offset (mutually exclusive with selectors)
queryNoSearch page content for query terms and extract best matching snippets
offsetNoCharacter offset to start reading from (mutually exclusive with selectors)
refreshNoBypass local cache and fetch fresh page from upstream (default False)
sectionNo1-based section number to extract from document (mutually exclusive)
find_textNoLocate text snippet and return surrounding context (mutually exclusive)
max_charsNoMax characters of page text to return (default 20000)
max_snippetsNoMax snippets to return when using query selector (1-5, default 3)
strip_boilerplateNoRemove cookie banners, navigation and site UI boilerplate (default True)
fallback_to_searchNoOn 404, fall back to searching exact URL in index (default True)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv3.0.0
    • addedInput schema / properties / clean / description
      Added value: +"Remove Markdown backslash escapes from the page text (default True)"
    • addedInput schema / properties / fallback_to_search / description
      Added value: +"On 404, fall back to searching exact URL in index (default True)"
    • addedInput schema / properties / find_text / description
      Added value: +"Locate text snippet and return surrounding context (mutually exclusive)"
    • addedInput schema / properties / limit / description
      Added value: +"Max characters to return from offset (mutually exclusive with selectors)"
    • addedInput schema / properties / max_chars / description
      Added value: +"Max characters of page text to return (default 20000)"
    • addedInput schema / properties / max_snippets / description
      Added value: +"Max snippets to return when using query selector (1-5, default 3)"
    • addedInput schema / properties / offset / description
      Added value: +"Character offset to start reading from (mutually exclusive with selectors)"
    • addedInput schema / properties / query / description
      Added value: +"Search page content for query terms and extract best matching snippets"
    • addedInput schema / properties / refresh / description
      Added value: +"Bypass local cache and fetch fresh page from upstream (default False)"
    • addedInput schema / properties / section / description
      Added value: +"1-based section number to extract from document (mutually exclusive)"
    • addedInput schema / properties / strip_boilerplate / description
      Added value: +"Remove cookie banners, navigation and site UI boilerplate (default True)"
    • addedInput schema / properties / url / description
      Added value: +"HTTP or HTTPS URL to fetch (must be public, no private IP/intranet)"
  2. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / fallback_to_search
      Added value: +{
      +  "default": true,
      +  "title": "Fallback To Search",
      +  "type": "boolean"
      +}
  3. Changed3 schema fields changedv2.1.1
    • addedInput schema / properties / find_text
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Find Text"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Limit"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Offset"
      +}
  4. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / max_snippets
      Added value: +{
      +  "default": 3,
      +  "title": "Max Snippets",
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Query"
      +}
    • addedInput schema / properties / section
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Section"
      +}
  5. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / strip_boilerplate
      Added value: +{
      +  "default": true,
      +  "title": "Strip Boilerplate",
      +  "type": "boolean"
      +}
  6. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, yet the description still adds material facts: a flat per-call cost ($0.00075), the 20,000-char default cap, the 404-to-search-index fallback for PDF and Reddit URLs, and that content is sanitized (images neutralized, hidden text stripped) — all of which affect whether an agent should call it and what it can trust in the output.

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?

Front-loaded with purpose, then pricing and limits, then selector behavior, then exclusions, then return shape — a sensible triage order for an agent. It is dense but nearly every sentence carries distinct information; the parenthetical default restatements (max_chars, offset=/limit=) are slight redundancy against a schema that already documents defaults.

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?

For a 12-parameter fetch tool, the definition covers cost, truncation behavior, sanitization, fallback policy, selector exclusivity, and output shape. An output schema exists, so the inline 'Returns' summary is a convenience rather than a gap, and nothing an agent needs to call it correctly is missing.

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 the baseline is 3. The description still earns above baseline by grouping section/query/offset/limit/find_text into a single 'one optional selector' concept, reinforcing that only one may be used, and by characterizing query as 'relevant excerpts, no LLM' — a cost/semantics hint the schema does not state.

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?

Opens with a specific verb and resource: 'Read one web page as clean Markdown, or only the part of it you need.' The single-page scope plus the partial-extraction capability is stated up front, and the 'When NOT to use' block names the sibling that handles several URLs (deepseek_fetch_many) and topic search (deepseek_search), so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Explicit positive condition ('Use it when you already know the URL') and an explicit negative routing block covering topic search, multiple URLs, JSON field extraction, and multi-source answers, each mapped to a named alternative. Nothing about tool selection is left to inference.

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