Skip to main content
Glama

Fetch Web Pages

fetch
Read-only

Retrieves content from 1–10 URLs, preferring local Firecrawl and falling back to TinyFish only for failed URLs when options are compatible.

Instructions

Fetch 1-10 URLs. Firecrawl Local is preferred; only failed URLs may fall back to TinyFish when options are compatible.

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": {
      "urls": "<urls>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
formatsNo
fallbackNo
providerNoauto
timeoutMsNo
waitForMsNo
onlyMainContentNo
excludeSelectorsNo
includeSelectorsNo

Output Schema

NameRequiredDescriptionDefault
errorsYes
partialYes
resultsYes
attemptsYes
providerYes
warningsYes
artifactIdsNo
requestedProviderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the provider preference order and the restriction that fallback applies only to failed URLs under compatible options, which is real behavioral context not in the annotations. It says nothing about what responses look like per format, timing behavior, or what happens when a URL fails outright.

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 with the core capability front-loaded and no filler. The second sentence is efficient but slightly cryptic; the phrase 'when options are compatible' introduces vagueness without an explanation of which options must match.

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

Completeness2/5

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

With 9 parameters, zero schema descriptions, and an output schema already covering return values, the description is far too thin for the tool's complexity. An agent cannot determine how to set formats, timeouts, wait behavior, or selector filters from the definition alone, though the provider routing rule is a helpful partial disclosure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description must carry the burden, yet it only restates the URLs count (already encoded as minItems/maxItems) and hints at provider/fallback. The meaning of formats, timeoutMs, waitForMs, onlyMainContent, includeSelectors, and excludeSelectors is left entirely unexplained, and 'when options are compatible' is undefined.

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 gives a specific verb and resource ('Fetch 1-10 URLs'), plus the batch-size constraint, so an agent knows immediately this is a bulk URL retrieval tool. It does not explicitly contrast with siblings like browse, crawl, or search, leaving the distinction to be inferred from names alone.

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

Usage Guidelines2/5

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

The only conditional guidance is about provider routing ('Firecrawl Local is preferred; only failed URLs may fall back to TinyFish when options are compatible'), which governs internal behavior rather than when to choose this tool over browse, crawl, or search. There is no statement of when-not-to-use or which sibling covers single-page browsing or site traversal.

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