Skip to main content
Glama
Sign In

Desearch

by io.github.Desearch-ai
OverviewDiscussionsAdmin

Crawl Web Page (Legacy)

web-crawl
Read-only

Crawl a public URL and return its content as plain text or HTML on the legacy Desearch /web/crawl route. The SDK marks webCrawl deprecated in favor of extract; this tool stays for parity with that route. Prefer extract for new integrations. API docs: https://www.desearch.ai/docs/guide/apis/extract-api

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": "web-crawl"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds important lifecycle context by disclosing deprecation and route parity, though it does not detail JS-rendering behavior or mention markdown output despite the schema supporting it.

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 front-loaded with purpose, then follows with deprecation status, the preferred alternative, and a docs link. Every sentence adds useful context without repetition or waste.

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 legacy read-only crawl tool with full schema coverage, the description covers purpose, lifecycle status, and the preferred alternative. It lacks return-value details such as truncation behavior or the schema-supported markdown format, but no output schema exists and the core calling context is present.

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?

Schema coverage is 100%, so all five parameters are fully documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 states a specific verb and resource: 'Crawl a public URL and return its content as plain text or HTML.' It explicitly labels the tool as legacy and names the preferred sibling, extract, so an agent can distinguish it from alternatives 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 Guidelines5/5

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

It gives explicit guidance: 'Prefer extract for new integrations' and explains that this tool exists 'for parity with that route.' This covers both when to use it (legacy compatibility) and when to use the alternative instead.

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