Skip to main content
Glama

Extract all structured data from a web page

structured_data
Read-only

Extract all structured data from a web page: every JSON-LD block parsed (Organization, Product, Article, FAQ, Breadcrumb, Event...), microdata item types and RDFa types. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and open-world scope, so the bar is lower, and the description adds real context on top: expected latency (1-3 s), a free tier (20 calls/day per user across free tools), and a paid path ($0.003 per call via x402, USDC on Base). The one gap is that it never says what a failure or an empty result looks like, but the operational profile is well disclosed.

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?

A single front-loaded paragraph: extraction scope first, then performance, then cost. Every sentence carries information, though the billing sentences are comparatively heavy relative to the extraction description and slightly dilute the focus.

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?

For a two-parameter read-only tool with no output schema, the description is largely sufficient: it names the formats parsed and the cost/latency model. It stops short of describing the shape of the returned data (e.g., per-block type/validity fields), which is the main thing an agent assembling a result would still want to know.

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 baseline is 3. The description's pricing sentences restate the payment parameter's purpose (free tier, then x402 payment) already documented in the schema, and the URL requirement is left entirely to the schema. It adds no format, syntax, or constraint detail beyond what the schema already provides.

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 ('Extract all structured data from a web page') and then enumerates exactly what counts as structured data — JSON-LD blocks (Organization, Product, Article, FAQ, Breadcrumb, Event), microdata item types, RDFa types. That level of specificity cleanly separates it from text-oriented siblings like page_text and page_markdown without needing to name them.

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 implied by the payload description — an agent can infer this is the tool for schema.org/JSON-LD/RDFa when text extraction isn't enough — but no explicit when-to-use or when-not-to-use guidance is given, and no alternative sibling is named. The pricing details do inform the call decision but do not address tool selection.

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.