Skip to main content
Glama

Fetch Page Content

infobroker_fetch_page
Idempotent

Fetch a URL and extract clean content through the configured renderer chain (Jina Reader primary, native-HTTP fallback; Wikipedia, Internet Archive, arXiv, and Stack Exchange alternatives).

Instructions

Fetch a URL and extract clean content through the configured renderer chain (Jina Reader primary, native-HTTP fallback; Wikipedia, Internet Archive, arXiv, and Stack Exchange alternatives). Use when you have a URL and need readable text, passages ranked against a question, or the page's last-updated date. Do NOT use for topic search (use infobroker_search_web) or cross-source claim verification (use infobroker_verify_claims). question returns passages ranked against it, sized by passage_size and capped by max_passages; crawl bounds the same-origin crawl to config caps; extract adds JSON-LD, OpenGraph, and microdata; renderer pins a single backend, and when it is omitted the configured chain runs with native_fetch as the keyless fallback when Jina is slow, throttled, errors, or serves an anti-bot challenge. max_length truncates the returned text only; a truncated page is written in full to a temp file. Makes external HTTP calls and needs no API key. A fresh knowledge-base copy is returned before an outbound fetch when available. Fetched pages auto-index into the knowledge base unless the content policy flags them (see infobroker_manage_kb): flag mode returns without storage, block mode refuses. Unreachable URLs return an [ERROR] envelope with remediation; when a DOI resolves, a blocked page falls back to Crossref metadata or an open-access copy, then to an Internet Archive snapshot, and reports meta.fallback_kind. Paywalls, access restrictions, and anti-bot blocks return access_blocked; connectivity failures return network_error; a non-http(s) URL returns invalid_input naming the read tool. Success returns an [OK] envelope with status, provider, results, and meta.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the extracted page text directly instead of a JSON envelope (single URL; not with crawl or extract)
urlYesURL to fetch: a single URL, or up to five URLs fetched in parallel
crawlNoBounded same-origin crawl: recursively fetch same-origin pages up to config caps (default off)
extractNoReturn structured metadata (JSON-LD, OpenGraph, microdata) alongside the content (default off)
questionNoQuestion to extract ranked passages for, instead of returning the whole page
rendererNoRenderer: omit to run the configured content-fetch chain (`jina` primary, then native HTTP), or pin one of jina, native_fetch, wikipedia, internet_archive, arxiv, or stack_exchange
max_lengthNoMaximum characters to return (default 50000)
detect_dateNoDetect and report the page's date (default from config; applies to plain, crawl, and extract responses — crawl and extract read document metadata, not headers)
max_passagesNoNumber of passages to return (default from config)
passage_sizeNoTarget words per passage (default from config)

Output Schema

NameRequiredDescriptionDefault
metaNo
errorNo
statusYes
noticesNo
resultsNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.16
    • changedInput schema / properties / detect_date / description
      Previous value: -"Detect and report the page's last-updated date (default from config)"New value: +"Detect and report the page's date (default from config; applies to plain, crawl, and extract responses — crawl and extract read document metadata, not headers)"
    • changedInput schema / properties / renderer / description
      Previous value: -"Renderer: jina (default), native_fetch, wikipedia, internet_archive, arxiv, or stack_exchange"New value: +"Renderer: omit to run the configured content-fetch chain (`jina` primary, then native HTTP), or pin one of jina, native_fetch, wikipedia, internet_archive, arxiv, or stack_exchange"
  2. Changed2 schema fields changedv2026.10.30
    • addedInput schema / properties / raw
      Added value: +{
      +  "default": false,
      +  "description": "Return the extracted page text directly instead of a JSON envelope (single URL; not with crawl or extract)",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "error": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "remediation": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "meta": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "notices": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "provider": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "enum": [
      +        "ok",
      +        "error"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "provider"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / crawl
      Added value: +{
      +  "default": false,
      +  "description": "Bounded same-origin crawl: recursively fetch same-origin pages up to config caps (default off)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / extract
      Added value: +{
      +  "default": false,
      +  "description": "Return structured metadata (JSON-LD, OpenGraph, microdata) alongside the content (default off)",
      +  "type": "boolean"
      +}
  4. Changed9 schema fields changedv0.1.1
    • addedInput schema / properties / detect_date
      Added value: +{
      +  "description": "Detect and report the page's last-updated date (default from config)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / max_length / description
      Added value: +"Maximum characters to return (default 50000)"
    • addedInput schema / properties / max_passages
      Added value: +{
      +  "description": "Number of passages to return (default from config)",
      +  "type": "number"
      +}
    • addedInput schema / properties / passage_size
      Added value: +{
      +  "description": "Target words per passage (default from config)",
      +  "type": "number"
      +}
    • addedInput schema / properties / question
      Added value: +{
      +  "description": "Question to extract ranked passages for, instead of returning the whole page",
      +  "type": "string"
      +}
    • addedInput schema / properties / renderer / description
      Added value: +"Renderer: jina (default), native_fetch, wikipedia, internet_archive, arxiv, or stack_exchange"
    • addedInput schema / properties / url / anyOf
      Added value: +[
      +  {
      +    "description": "URL to fetch",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Multiple URLs to fetch in parallel (max 5)",
      +    "items": {
      +      "type": "string"
      +    },
      +    "maxItems": 5,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / url / description
      Previous value: -"URL to fetch"New value: +"URL to fetch: a single URL, or up to five URLs fetched in parallel"
    • removedInput schema / properties / url / type
      Removed value: -"string"
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: discloses that it makes external HTTP calls with no API key, that it auto-indexes pages into the knowledge base with flag/block policy modes (consistent with readOnlyHint=false), that truncation writes the full page to a temp file, and that a KB copy is served before an outbound fetch. Error taxonomy (access_blocked, network_error, invalid_input) and DOI fallback ordering with meta.fallback_kind are spelled out, which is exactly the behavioral context annotations cannot carry.

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-loads purpose, then the routing exclusions, then parameter behavior, then error semantics — a sensible progression. It is dense and long, but nearly every clause carries operational information; only the final envelope/error sentence overlaps with what the output schema already provides.

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?

For a 10-parameter, multi-backend fetch tool with side effects on the knowledge base, this covers triggers, exclusions, fallback order, storage policy, truncation side effects, and failure modes. Return shapes are covered by the output schema, so the extra envelope detail is redundant rather than missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine cross-parameter meaning: question output is sized by passage_size and capped by max_passages, crawl is bounded by config caps, extract layers in JSON-LD/OpenGraph/microdata, renderer pins one backend while omission runs the chain with native_fetch as keyless fallback, and max_length truncates only the returned text. This is more than a restatement of the schema, though it largely mirrors the already-thorough per-parameter descriptions.

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?

Opens with a specific verb and resource ('Fetch a URL and extract clean content') and names the renderer chain, which is the tool's distinguishing mechanism. It also explicitly separates itself from infobroker_search_web and infobroker_verify_claims, so an agent can route without opening any 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?

States the positive trigger ('when you have a URL and need readable text, passages ranked against a question, or the page's last-updated date') and two explicit exclusions with named alternatives ('Do NOT use for topic search... or cross-source claim verification'). When/when-not/alternatives are all present.

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