Skip to main content
Glama

Fetch page

fetch_page

Alias of read_url. Same markdown result, including title, final URL, status, approx_tokens, and any Content-Signal header.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http or https URL. No private addresses, no credentials.
max_charsNoMaximum characters of text. Default 20000, maximum 100000.

Output Schema

NameRequiredDescriptionDefault
okNo
errorNo
titleNo
statusNo
markdownNo
final_urlNo
truncatedNo
content_typeNo
approx_tokensNo
content_signalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden, and it does add some value by naming return fields and implying redirect handling via 'final URL' and error state via 'status'. It says nothing about permissions, rate limits, JS rendering, or whether the fetch is read-only, which for a network-fetching tool leaves meaningful gaps.

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?

Two short sentences, front-loaded with the alias relationship and then the return payload, with no filler. Minor redundancy since the returned fields are also captured by the output schema, but the sentence still earns its place as a quick equivalence signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The alias relationship is fully covered and an output schema exists so return values needn't be spelled out again. What's missing is guidance on choosing between this and read_url, plus any behavioral context for a network tool that has zero annotations behind it.

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%, with both url and max_chars fully documented including defaults and maximums, so the baseline is 3. The description adds nothing about parameter behavior such as how max_chars interacts with truncation of the markdown result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes the tool's identity explicit as an alias of read_url and states it returns markdown with title, final URL, status, approx_tokens, and a Content-Signal header. An agent can immediately tell this retrieves page content identically to a known sibling, though the verb (fetch/retrieve) is only implied via the alias rather than stated.

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

Usage Guidelines3/5

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

Saying 'Alias of read_url' implicitly tells the agent the two are interchangeable, which is useful routing information. However, it never states when to prefer fetch_page over read_url, nor any exclusions such as private addresses or credentialed URLs (those constraints live only in the schema).

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.

Resources