Skip to main content
Glama

Fetch web page

web_fetch
Read-onlyIdempotent

Fetch a public http(s) web page (docs, research). Private and internal addresses are refused. Returns the status and up to 80,000 characters of the body.

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_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral detail beyond them: the address-space restriction (public only), the returned status field, and an explicit 80,000-character truncation cap. It does not cover redirect or error/status-failure behavior, but the additions are substantial.

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 short sentences, front-loaded with the action, then the constraint, then the return shape. Every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description usefully states the return shape (status plus truncated body), and the private-address refusal is disclosed. For a two-parameter open-world fetch tool this is close to complete; only redirects, non-HTML content, and auth-gated pages are unaddressed.

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 50%: project_id is documented in the schema, and url has only a uri format hint. The description partially compensates by constraining url to public http(s), but says nothing about project_id or its relationship to the project_id-or-session choice described in the schema. Baseline 3 is appropriate since the schema still carries half the 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?

"Fetch a public http(s) web page" names a specific verb and resource, and the parenthetical "(docs, research)" plus the public-only constraint make it immediately distinguishable from a search tool like web_search. An agent knows exactly what this returns 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?

The description gives clear context for use (public docs and research pages) and an explicit exclusion (private and internal addresses are refused), which tells the agent when this will fail. It stops short of naming an alternative for cases where fetching is refused, so there is no full when/when-not/alternative routing.

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