Skip to main content
Glama

fetch_meta

Read-onlyIdempotent

Extract a page's head metadata—title, description, canonical, Open Graph, Twitter Card, icons, feeds, and JSON-LD—from a URL to preview it before reading the full content.

Instructions

GET a URL and extract its head metadata: title, description, canonical, language, robots directive, Open Graph / Twitter Card / article: properties, icon links, RSS/Atom feed links, and any JSON-LD (schema.org) blocks. Keys that appear more than once (e.g. multiple og:image tags) are additionally returned via ogAll/twitterAll/articleAll arrays. Lists are capped: at most 100 icons, feeds, JSON-LD blocks and values per *All key, and 1000 keys per og/twitter/article; a JSON-LD block nested deeper than 64 levels is dropped. When anything is cut, truncated names the collections affected. Ideal for previewing a page before fully reading it.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to extract metadata from
max_bytesNoDefault 2MiB — metadata lives in <head>
timeout_msNo
user_agentNo
max_redirectsNo
allow_private_hostsNoAllow loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / allow_private_hosts / description
      Added value: +"Allow loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way."
  2. First observedv0.6.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description goes well beyond them: it discloses truncation caps (100 per *All key, 1000 og/twitter/article keys, 64-level JSON-LD nesting), the `truncated` signal, and the default byte budget. This is exactly the behavioral context an agent needs before calling.

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-loaded with the core verb and return shape, then truncation rules. The cap/depth details are dense but each sentence conveys actionable constraints, so waste is minimal.

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 does the heavy lifting on return shape (field list, *All arrays, `truncated` flag), which is strong. It falls short only on undocumented tuning parameters (timeout, user_agent, redirects), a minor gap for a fetch tool.

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%, and the schema itself documents url, max_bytes, and allow_private_hosts. The description adds nothing about timeout_ms, user_agent, or max_redirects, so half the parameters remain unexplained in prose. Baseline 3 is appropriate given partial schema coverage.

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?

States a specific verb (GET a URL) and resource (head metadata), then enumerates exactly which metadata classes are returned (title, canonical, OG/Twitter, JSON-LD, feeds, icons). This clearly separates it from siblings like fetch_html_to_markdown or fetch_reader that return body content.

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?

'Ideal for previewing a page before fully reading it' gives a clear use context and implicitly contrasts with the full-read siblings. However, it never names an alternative tool explicitly (e.g. fetch_reader or fetch_html_to_markdown) or states when not to use it.

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