Skip to main content
Glama
Sign In

x402-data-gateway

by io.github.epistemedeus
OverviewDiscussionsAdmin

Extract Web Page as Structured JSON

extract

Fetch a public HTTP(S) page and return compact extraction signals for programmatic inspection: title, meta description, Open Graph/Twitter metadata, JSON-LD, headings, links, text excerpt, and AI-readiness flags. Use read instead when you need the page body as LLM-ready Markdown rather than metadata or a link inventory. Does not execute JavaScript; follows redirects and applies SSRF, timeout, and response-size guards. Payment challenge and credentials are bound to GET https://agents.samedaydesk.com/extract, not mcp://. Retry the identical authorized arguments and credential.

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP(S) URL. Choose extract for metadata, JSON-LD, headings, links, and a bounded text excerpt; use read for longer bounded Markdown. Content is fetched without JavaScript rendering. Check status/sourceOk/error/capture; ok means a typed extract record, not source completeness.
textExcerptLimitCharsNoOptional excerpt budget. Default 1200. Maximum 40000. Rejected before fetch. Does not purchase /read or change the price.

Output Schema

NameRequiredDescriptionDefault
okYes
urlYes
langYes
textYes
errorYes
linksYes
titleYes
jsonLdYes
statusYes
captureYes
twitterYes
finalUrlYes
headingsYes
sourceOkYes
canonicalYes
fetchedAtYes
openGraphYes
aiReadinessYes
contentTypeYes
descriptionYes
requestedUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / textExcerptLimitChars
      Added value: +{
+  "description": "Optional excerpt budget. Default 1200. Maximum 40000. Rejected before fetch. Does not purchase /read or change the price.",
+  "maximum": 40000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed7 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTP(S) URL. Choose extract for metadata, JSON-LD, headings, links, and a text excerpt; use read for cleaned full-body Markdown. Content is fetched without JavaScript rendering."New value: +"Public HTTP(S) URL. Choose extract for metadata, JSON-LD, headings, links, and a bounded text excerpt; use read for longer bounded Markdown. Content is fetched without JavaScript rendering. Check status/sourceOk/error/capture; ok means a typed extract record, not source completeness."
    • addedOutput schema / properties / capture
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bodyBytes": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "bodyTruncated": {
+      "type": "boolean"
+    },
+    "charset": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "charsetSource": {
+      "enum": [
+        "content-type",
+        "html-meta",
+        "default-utf-8",
+        "invalid-charset-fallback"
+      ],
+      "type": "string"
+    },
+    "javascriptExecuted": {
+      "const": false,
+      "type": "boolean"
+    },
+    "markdownLimitChars": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "maxBodyBytes": {
+      "type": "integer"
+    },
+    "method": {
+      "const": "http-get-no-javascript",
+      "type": "string"
+    },
+    "textExcerptLimitChars": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "textTruncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "method",
+    "javascriptExecuted",
+    "maxBodyBytes",
+    "textExcerptLimitChars",
+    "markdownLimitChars",
+    "bodyBytes",
+    "bodyTruncated",
+    "textTruncated",
+    "charset",
+    "charsetSource"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / error
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / finalUrl
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / requestedUrl
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / sourceOk
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / required
      Previous value: -[
-  "ok",
-  "url",
-  "status",
-  "contentType",
-  "title",
-  "description",
-  "canonical",
-  "lang",
-  "openGraph",
-  "twitter",
-  "jsonLd",
-  "headings",
-  "links",
-  "text",
-  "aiReadiness",
-  "fetchedAt"
-]New value: +[
+  "ok",
+  "requestedUrl",
+  "finalUrl",
+  "url",
+  "status",
+  "sourceOk",
+  "error",
+  "contentType",
+  "title",
+  "description",
+  "canonical",
+  "lang",
+  "openGraph",
+  "twitter",
+  "jsonLd",
+  "headings",
+  "links",
+  "text",
+  "aiReadiness",
+  "capture",
+  "fetchedAt"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "aiReadiness": {
+      "additionalProperties": false,
+      "properties": {
+        "hasCanonical": {
+          "type": "boolean"
+        },
+        "hasDescription": {
+          "type": "boolean"
+        },
+        "hasJsonLd": {
+          "type": "boolean"
+        },
+        "hasOpenGraph": {
+          "type": "boolean"
+        },
+        "hasTitle": {
+          "type": "boolean"
+        },
+        "schemaTypes": {
+          "items": {},
+          "type": "array"
+        }
+      },
+      "required": [
+        "hasJsonLd",
+        "hasOpenGraph",
+        "hasTitle",
+        "hasDescription",
+        "hasCanonical",
+        "schemaTypes"
+      ],
+      "type": "object"
+    },
+    "canonical": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contentType": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fetchedAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "headings": {
+      "additionalProperties": false,
+      "properties": {
+        "h1": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "h2": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "h1",
+        "h2"
+      ],
+      "type": "object"
+    },
+    "jsonLd": {
+      "items": {},
+      "type": "array"
+    },
+    "lang": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "openGraph": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "status": {
+      "type": "integer"
+    },
+    "text": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "twitter": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "url",
+    "status",
+    "contentType",
+    "title",
+    "description",
+    "canonical",
+    "lang",
+    "openGraph",
+    "twitter",
+    "jsonLd",
+    "headings",
+    "links",
+    "text",
+    "aiReadiness",
+    "fetchedAt"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL to extract"New value: +"Public HTTP(S) URL. Choose extract for metadata, JSON-LD, headings, links, and a text excerpt; use read for cleaned full-body Markdown. Content is fetched without JavaScript rendering."
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: no JavaScript execution, redirect following, SSRF/timeout/response-size guards, and the payment/credential binding to the GET endpoint rather than mcp://, plus retry semantics. These are exactly the non-obvious operational traits an agent needs before calling a fetcher.

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 action and return set, followed by routing, behavioral limits, and payment/retry notes. Dense but every sentence carries information; the payment-binding sentence is slightly cryptic but not redundant.

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?

For a two-parameter fetch tool with an output schema available, the definition covers purpose, the sibling routing decision, JS/redirect/guard behavior, and auth/retry handling. An agent has everything needed to call it correctly and interpret failure via status/sourceOk/error.

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 description coverage is 100%, so the schema already documents url and textExcerptLimitChars (default 1200, max 40000, rejected pre-fetch). The description adds only the general notion of a bounded excerpt, which is already implied upstream; it does not add new semantics, so the high-coverage baseline applies with a slight bump for reinforcing the budget concept.

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 (Fetch) and resource (public HTTP(S) page) and enumerates the returned artifact set (title, meta, OG/Twitter, JSON-LD, headings, links, excerpt, AI-readiness flags). It explicitly contrasts itself with the `read` sibling, so an agent can distinguish the two without opening either 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?

Names the alternative tool and the exact condition that selects it: 'Use `read` instead when you need the page body as LLM-ready Markdown rather than metadata or a link inventory.' The url parameter description reinforces the same routing rule, leaving nothing to inference.

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

All x402-data-gateway toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources