ToolSnap MCP

Fetch page metadata

fetch_metadata

Read-only

Extract a public URL's head metadata as JSON—title, description, canonical, Open Graph, Twitter, and JSON-LD—without loading page body text or running JavaScript.

Instructions

Free, read-only. Fetch a public http(s) URL and return its metadata as JSON: url (after redirects), title, description, canonical, robots, author, keywords, lang, charset, og{} and twitter{} (prefix stripped), httpEquiv{}, jsonLd[] (parsed blocks, malformed ones skipped). Absent fields are null or {}. Reads only the first 512 KB, follows up to 5 redirects, 10 s timeout; private and local hosts are rejected and non-2xx responses error with the HTTP status. Runs no JavaScript, so tags injected client-side are not seen. Not for body text: use fetch_extract (plain text) or fetch_html (raw HTML).

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http:// or https:// URL. Local and private hosts are rejected.
`headers`	No	Headers to forward for pages behind login: Authorization, Cookie, X-API-Key only. Dropped if a redirect leaves the original host.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.6Oct 25, 2026

changedInput schema / properties / headers / description

Previous value: -"Headers to forward (Authorization, Cookie…)."New value: +"Headers to forward for pages behind login: Authorization, Cookie, X-API-Key only. Dropped if a redirect leaves the original host."

changedInput schema / properties / url / description

Previous value: -"Page URL."New value: +"Public http:// or https:// URL. Local and private hosts are rejected."

Changed2 schema fields changedv0.1.1Oct 22, 2026

addedInput schema / properties / headers

Added value: +{
+  "description": "Headers to forward (Authorization, Cookie…).",
+  "type": "object"
+}

changedInput schema / properties / url / description

Previous value: -"URL to fetch (http:// or https://)."New value: +"Page URL."

AddedJun 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Even though readOnlyHint is already set, the description adds substantial operational detail: 512 KB read cap, 5-redirect limit, 10 s timeout, private/local host rejection, non-2xx error behavior, and no JavaScript execution.

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?

Front-loads the core purpose, then packs output shape, limits, security behavior, and alternatives into a dense but waste-free paragraph.

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?

No output schema is present, yet the description fully specifies the JSON return shape, null/{} handling for missing fields, malformed jsonLd behavior, and error conditions, leaving nothing essential unexplained.

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%, so both url and headers are already documented. The description reinforces the public/private URL rule but adds almost nothing about the headers parameter, so baseline 3 is appropriate.

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 and resource — fetching a public URL's <head> metadata — and enumerates the returned fields, which clearly distinguishes it from fetch_extract and fetch_html.

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?

Explicitly excludes body-text use and names the two alternatives, fetch_extract for plain text and fetch_html for raw HTML, so the routing decision is unambiguous.

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

Deploy Server