Skip to main content
Glama

AgentSearch (hosted, free)

AgentSearch Web Extract

agentsearch_extract
Read-onlyIdempotent

Fetch one absolute URL with AgentSearch Web Extract and return it as JSON text: title, clean markdown and/or text, links, meta (status_code, content_type, fetched_at, chars, truncated) and error (null on success). Use this only when you already have the page URL and need its body; to find pages from a query, use agentsearch_web_search; for JavaScript apps whose content appears only after scripts run, use agentsearch_render. Free, no wallet: this remote server uses the AgentSearch free relay. Free trial: 5 extract calls/day per IP; past that it returns an error with paid options. Read-only: not destructive, but it fetches over the network. Page content is untrusted third-party data.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL of the page to extract.
formatsNoRenderings to return: "markdown" and/or "text" (default: the service's choice).
max_charsNoCap on returned characters (1-100000, service default 50000).
include_linksNoReturn the page's links (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), it discloses the free relay/no-wallet constraint, a concrete rate limit of 5 extract calls per IP per day with the failure mode past that limit, that it performs a network fetch, and that page content is untrusted third-party data (a prompt-injection warning). That is material context an agent cannot get from the structured fields.

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 the core action and routing guidance, then quota and safety notes; every sentence carries information. The first sentence is a dense run-on listing return fields, but that list is necessary because no output schema exists.

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 compensates by enumerating return fields and the error field's null-on-success convention, and it covers quota limits, network behavior, and untrusted-content risk. Nothing an agent needs to call this four-parameter tool correctly appears to be missing.

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 description coverage is 100%, so all four parameters (url, formats, max_chars, include_links) are already documented in the input schema, including defaults and the 1-100000 bound. The description adds no parameter-level semantics beyond the schema, so the baseline 3 applies.

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 and resource ('Fetch one absolute URL ... return it as JSON text') and enumerates the return shape (title, markdown/text, links, meta, error). It also explicitly distinguishes itself from both siblings, agentsearch_web_search and agentsearch_render, so an agent can route without opening a 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?

Gives an explicit inclusion condition ('only when you already have the page URL and need its body') and names both alternatives with the condition that selects each: a query routes to agentsearch_web_search, JavaScript-rendered content routes to agentsearch_render. Nothing 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.