agentdiet

extract_structured_data

Read-onlyIdempotent

Extract machine-readable structured data from a web page: Schema.org JSON-LD objects, OpenGraph metadata, HTML tables parsed as JSON row arrays, fenced code blocks, section headings, and links. WHEN TO USE: Call this tool for pricing tables, API specifications, product metadata, or code snippets; use distill_webpage for narrative Markdown or recon_webpage_skeleton for a lightweight heading outline. WHEN NOT TO USE: Do not use for narrative prose extraction or binary files. PARAMETER INTERACTIONS: Provide either url or html (when html is supplied, url is not fetched and only labels the cache key). Omit agent_id and tx_hash during your 5 free calls. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.001 per call ($0.0005 cached). Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: extract_structured_data(url='https://docs.stripe.com/api')

Input Schema

Name	Required	Description
`url`	Yes	Target public HTTP(S) webpage URL to fetch (or builtin://stripe-docs for a built-in benchmark page). Private/loopback IPs are blocked.
`html`	No	Optional raw HTML string (up to ~1.9MB) to process directly without network fetching. When provided, url is not fetched and only labels the cache entry.
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://docs.stripe.com/api"
+  }
+]

Changed12 schema fields changedOct 18, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

changedInput schema / properties / html / description

Previous value: -"Raw HTML (up to ~1.9MB) to process instead of fetching url. When set, url only labels the cache entry."New value: +"Optional raw HTML string (up to ~1.9MB) to process directly without network fetching. When provided, url is not fetched and only labels the cache entry."

changedInput schema / properties / tx_hash / description

Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."

addedInput schema / properties / tx_hash / maxLength
```
Added value: +256
```
addedInput schema / properties / tx_hash / minLength
```
Added value: +10
```

changedInput schema / properties / url / description

Previous value: -"Public http(s) URL to fetch, or builtin://stripe-docs for a demo page. Private and metadata IPs are blocked."New value: +"Target public HTTP(S) webpage URL to fetch (or builtin://stripe-docs for a built-in benchmark page). Private/loopback IPs are blocked."

addedOutput schema / properties / data / description
```
Added value: +"Structured tool output payload."
```

addedOutput schema / properties / roi_proof / description

Added value: +"Token compression and cost-savings verification metrics."

addedOutput schema / properties / status / description

Added value: +"Execution status ('ok' or 'payment_required')."

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "type": "object"
+    },
+    "roi_proof": {
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedOct 16, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."

changedInput schema / properties / html / description

Previous value: -"Optional raw HTML string"New value: +"Raw HTML (up to ~1.9MB) to process instead of fetching url. When set, url only labels the cache entry."

changedInput schema / properties / html / maxLength
```
Previous value: -99999New value: +1900000
```

changedInput schema / properties / tx_hash / description

Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."

changedInput schema / properties / url / description

Previous value: -"Target webpage URL"New value: +"Public http(s) URL to fetch, or builtin://stripe-docs for a demo page. Private and metadata IPs are blocked."

changedInput schema / properties / url / maxLength
```
Previous value: -99999New value: +2048
```

Changed3 schema fields changedOct 16, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+  "type": "string"
+}

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}

Changed5 schema fields changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / html / maxLength
```
Added value: +99999
```
- addedInput schema / properties / html / minLength
```
Added value: +1
```
- addedInput schema / properties / url / maxLength
```
Added value: +99999
```
- addedInput schema / properties / url / minLength
```
Added value: +1
```
First observedOct 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description goes well beyond them: 1-hour caching with <5ms hits, a 5-free-call trial, a non-fatal payment-required quote with Stripe/Base/Solana settlement paths, and the fact that failed calls are never charged. This is the pricing and failure-mode 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 core purpose followed by labeled WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS blocks, with the pricing detail last. The pricing paragraph is dense but each sentence carries operative information (free-call count, quote-not-error behavior, retry credentials); slightly overlong, keeping it just below a 5.

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?

An output schema exists, so return-value explanation is unnecessary, and the description instead covers routing, parameter interaction, caching, and the payment lifecycle. For a paid, cached, network-fetching extractor, nothing an agent needs to invoke it successfully is 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 already 100%, so the baseline is 3, but the description adds genuine cross-parameter semantics: url or html is either/or, and when html is supplied the url only labels the cache key rather than being fetched. It also clarifies that agent_id and tx_hash should be omitted during the free calls, which the individual schema descriptions only imply.

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 (extract) and resource (structured data from a web page) and enumerates the concrete artifact types returned: JSON-LD, OpenGraph, HTML tables as JSON rows, code blocks, headings, links. It also names the sibling tools it is distinct from, so an agent can route correctly without opening a 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?

Explicit WHEN TO USE with concrete scenarios (pricing tables, API specs, product metadata, code snippets) and explicit alternative routing to distill_webpage for narrative Markdown and recon_webpage_skeleton for a lightweight outline. WHEN NOT TO USE closes the remaining ambiguity (narrative prose, binary files).

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

All agentdiet tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?