WebExtract

Extract web page

extract_url

Read-only

Fetch a public web page (robots.txt respected) and return clean Markdown plus fixed-schema JSON: article metadata, product/price, tables. Free 50 calls/day per IP; pass 'Authorization: Bearer ' for prepaid credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`tables`	Yes
`product`	Yes
`markdown`	Yes
`metadata`	Yes
`final_url`	Yes
`fetched_at`	Yes
`word_count`	No
`schema_version`	Yes
`markdown_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "fetched_at": {
+      "type": "string"
+    },
+    "final_url": {
+      "type": "string"
+    },
+    "markdown": {
+      "type": "string"
+    },
+    "markdown_truncated": {
+      "type": "boolean"
+    },
+    "metadata": {
+      "properties": {
+        "authors": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "canonical_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "description": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "image": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "language": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "modified_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "published_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "site_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "product": {
+      "properties": {
+        "availability": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "brand": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "currency": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "description": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "gtin": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "image": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "price_high": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "rating": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "sku": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "source": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "tables": {
+      "items": {
+        "properties": {
+          "caption": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "checks": {
+            "properties": {
+              "column_count": {
+                "type": "integer"
+              },
+              "consistent_width": {
+                "type": "boolean"
+              },
+              "row_count": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "headers": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "index": {
+            "type": "integer"
+          },
+          "rows": {
+            "items": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "word_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "url",
+    "final_url",
+    "fetched_at",
+    "schema_version",
+    "markdown",
+    "metadata",
+    "product",
+    "tables"
+  ],
+  "type": "object"
+}

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses real operational behavior: robots.txt is honored, the free tier is capped at 50 calls/day per IP, and prepaid credits require an 'Authorization: Bearer <key>' header. These are exactly the constraints an agent needs to avoid surprise failures. It stops short of covering failure modes such as blocked pages or non-HTML content.

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?

Two tight sentences with no filler, front-loading what the tool does before the operational constraints. The second sentence packs quota and auth details densely but every clause is actionable.

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 return-value structure need not be explained, and the description nonetheless summarizes it. Auth, quota, and scope are all covered. The one missing piece for this tool's complexity is disambiguation from page_markdown, which is absent.

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?

There is a single parameter with 100% schema description coverage ('Public http(s) URL'), so the schema already carries the semantics. The description only echoes the public-URL constraint, adding nothing material beyond what the schema states; baseline 3 applies.

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?

States a concrete verb and resource — fetch a public web page and return Markdown plus fixed-schema JSON — and even enumerates the JSON payload categories (article metadata, product/price, tables). It is clear, but it never distinguishes itself from the sibling page_markdown, leaving the agent to guess which extractor 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: 'public web page' and 'robots.txt respected' signal the accepted scope, and the auth/credit sentence hints at paid traffic. There is no explicit when-to-use, no when-not-to-use, and no routing to page_markdown, so the agent must infer the boundary between the two tools.

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

All WebExtract tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?