Skip to main content
Glama
Sign In

Desearch

by io.github.Desearch-ai
OverviewDiscussionsAdmin

Extract Page Content

extract
Read-only

Extract a public URL and return its content as plain text, markdown or HTML using Desearch. Markdown keeps headings, lists and tables. Text is the page's main content; set full_page for every section, such as opening hours or fee tables. A js_required error means the page needs js: true; blocked means the site refused or showed a bot check. Preferred over web-crawl for new integrations. API docs: https://www.desearch.ai/docs/api-reference/get-web-extract

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

Input Schema

NameRequiredDescriptionDefault
jsNoRender JavaScript before reading the page.
urlYesPublic URL to read, example: 'https://desearch.ai'
waitNoPost-load wait in milliseconds when JavaScript rendering is enabled.
formatNoContent format to return: 'text' (default), 'markdown' (headings, lists, tables and code) or 'html'.
full_pageNoOnly with format 'text': return all visible text of the page (every section, table and notice) instead of only its main content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Content format to return: 'html' or 'text'."New value: +"Content format to return: 'text' (default), 'markdown' (headings, lists, tables and code) or 'html'."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "html",
-  "text"
-]New value: +[
+  "html",
+  "text",
+  "markdown"
+]
    • changedInput schema / properties / full_page / description
      Previous value: -"With format 'text', return all visible text of the page (every section, table and notice) instead of only its main content."New value: +"Only with format 'text': return all visible text of the page (every section, table and notice) instead of only its main content."
  2. Changed1 schema field changed
    • addedInput schema / properties / full_page
      Added value: +{
+  "description": "With format 'text', return all visible text of the page (every section, table and notice) instead of only its main content.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds real behavioral value beyond them: what markdown preserves, that default text is main-content only, and how two failure modes (js_required, blocked) should be handled. It does not describe rate limits or response size, keeping it just under 5.

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?

Sentences are front-loaded with the action and format defaults, then move to options, error recovery, and alternatives in a logical order. Nearly every clause carries actionable information, with only the docs link being optional padding.

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?

With no output schema, the description correctly explains the return formats and what each contains. Combined with the error-handling guidance and the full_page caveat, an agent has everything needed to call this tool correctly on the first attempt.

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 coverage is 100%, so the baseline is 3, but the description earns extra credit by clarifying intent: full_page is described as a remedy for sections like opening hours or fee tables, and js:true is tied to the js_required error. This adds decision-relevant meaning beyond the schema text.

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?

States a specific verb (extract) and resource (public URL content) plus the three return formats and underlying service (Desearch). It also distinguishes itself from web-crawl, so an agent can separate it from siblings without opening the schema.

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?

Explicitly names web-crawl as the alternative and gives the condition that selects this tool ('preferred over web-crawl for new integrations'), plus when to set full_page. It does not address the other plausible sibling (fetch) or state when NOT to use extract, so it falls short of a full 5.

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

All Desearch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources