AgentFetch API

Get page contents

get_page_contents

Read-onlyIdempotent

Fetch a public web page live and return its main content as clean Markdown, plain text or HTML. Use this when you have a specific URL and need its current content. Works best on articles, docs, product and listing pages. Does not log in, submit forms or execute JavaScript (yet).

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The public URL to fetch (http or https, at most 8,192 characters).
`format`	No	Output format. Prefer markdown.	markdown
`country`	No	Fetch the page as seen from this country, e.g. 'de', 'gb', 'us'.	us
`verbosity`	No	'compact' = main content only, 'full' = whole page body.	compact
`max_characters`	No	Maximum characters of content to return (default 8000, smaller than the REST API's 100000 to save context). Raise it when the content is cut.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered. The description adds genuinely new behavioral context: the tool does not log in, submit forms, or execute JavaScript, which tells an agent that JS-rendered pages may return incomplete content — a real limitation not visible in any structured field. It stops short of covering rate limits, caching, or what happens to the truncated remainder, keeping it below a 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?

Three tight sentences: capability first, then the selection condition, then the limitations. Every sentence earns its place, and the most decision-relevant content (what it returns, when to reach for it) is front-loaded with 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 five-parameter read-only fetch tool with full schema coverage and no output schema, the description covers purpose, usage, and key behavioral limits. The only minor gap is truncation handling at max_characters (what the agent sees when content is cut), which is left entirely to the schema.

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 five parameters (url, format, country, verbosity, max_characters) are already documented in the input schema, including defaults, enums, and lengths. The description only echoes the format choices ("Markdown, plain text or HTML") without adding meaning to country, verbosity, or truncation behavior. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb-and-resource statement: "Fetch a public web page live and return its main content as clean Markdown, plain text or HTML." It names the exact output formats and the resource, so an agent knows precisely what the tool produces and cannot confuse it with the unrelated sibling get_account_status.

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 an explicit when-to-use condition ("when you have a specific URL and need its current content") and explicit when-not-to-use cases ("Does not log in, submit forms or execute JavaScript"), plus the page types it suits best ("articles, docs, product and listing pages"). No alternative tool is named, but none is needed given the applicable tool set, so the guidance is essentially complete.

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

All AgentFetch API tools Inspect

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

Need Help?