Skip to main content
Glama

Extract page data

extract_page_data

Fetch one public HTML page and return title, meta, Open Graph, JSON-LD, links, headings, feeds, and tables. Same SSRF guard and per-network limit as read_url. Cached 10 minutes by final URL. Does not store the page.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http or https URL. No private addresses, no credentials.
includeNoComma-separated: meta, opengraph, jsonld, links, headings, tables, feeds. Default is all except tables.
max_linksNo1 to 200. Default 100.
max_tablesNo1 to 5. Default 5.

Output Schema

NameRequiredDescriptionDefault
okNo
metaNo
feedsNo
linksNo
jsonldNo
statusNo
tablesNo
headingsNo
final_urlNo
opengraphNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does add real value: SSRF guard, per-network rate limit, a 10-minute cache keyed by final URL, and no page storage. However it omits error behavior for non-HTML or failed fetches, redirect semantics implied by "final URL," and any truncation behavior for very large pages.

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 purpose then behavior, with zero filler. Every sentence contributes either scope, safety/limit context, or caching semantics.

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?

An output schema exists, so the description needn't explain return shapes, and it covers the behaviors an agent most needs: safety guard, rate limit, caching, and statelessness. The remaining gap is failure and redirect handling, which matters for an HTML fetch tool but is a modest omission.

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 schema already documents url, include, max_links, and max_tables with ranges and defaults, making the baseline 3. The description adds a little beyond the schema by mapping the enumerated return sections to the same vocabulary used by the include parameter, plus the hint that caching keys on the final (post-redirect) URL.

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?

"Fetch one public HTML page and return title, meta, Open Graph, JSON-LD, links, headings, feeds, and tables" is a specific verb-plus-resource statement with an explicit enumeration of what comes back. It only partially separates itself from siblings like read_url and fetch_page, hinting at the relationship through the SSRF/limit reference rather than saying which tool to pick.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for structured extraction from a page whereas read_url is referenced only as a shared-guard peer. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing from the field list.

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