Skip to main content
Glama

Extract structured data from a web page

contrie_extract
Read-only

Extract structured data from one public web page. Describe the fields you want in natural language and/or pass a JSON Schema for the exact shape. Returns JSON plus metadata: qualityScore (0-100; structured acceptance also requires success and valid), grounding (value presence, not field attribution), high-level progress and credits charged. Also returns groundingFields, a per-field grounding verdict with page excerpts, so you can see which extracted values have matching source text; this does not establish factual truth or correct field association. metadata.binding, when present, lists the paths of fields whose value is on the page while the passages about that field state a different value. Requires authentication: sign in with your Contrie account (OAuth), or send an API key in the Authorization header. A small set of recorded sample requests works without either. An accepted answer costs 1, 3, 8 or 15 credits; a refused one costs 0. Each plan caps one request's credits, rendering included (Free 3, Builder 5, Pro 17); an answer above the cap is refused and costs 0. Not a crawler or a search engine: one page per call. Eligible JavaScript shells can use bounded browser rendering; successful rendered answers add 2 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe public web page to extract from
maxAgeNoAccept page bytes from your account fetched up to this many seconds ago; origin expiry may be shorter. Default 0 bypasses cache reads/writes. Query/fragment/user-info URLs and restricted origin responses are never cached.
renderNoauto (default): render in a browser only if the page is a JavaScript shell; always: render first; never: plain fetch only. Only a successful rendered result adds 2 credits.
schemaNoJSON Schema subset, max 10,000 serialized UTF-8 bytes: object/array/string/number/integer/boolean, properties, required, items, enum
extractNoWhat to extract, in natural language (e.g. "product name, price, and stock status")
idempotencyKeyNoStable request ID, 8–200 visible ASCII characters. Reuse the same ID and inputs to recover a completed response for 24 hours without another extraction or charge. Use a new ID for deliberately new work. Requires authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / render / description
      Previous value: -"auto (default): render in a browser only if the page is a JavaScript shell; always: render first; never: plain fetch only. Rendering adds 2 credits."New value: +"auto (default): render in a browser only if the page is a JavaScript shell; always: render first; never: plain fetch only. Only a successful rendered result adds 2 credits."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: discloses credit costs (1/3/8/15), zero cost on refusal, per-plan caps (Free 3, Builder 5, Pro 17), the 2-credit rendering surcharge, auth requirements, sample-request exception, and exactly what the returned grounding verdicts do and do not prove. This is unusually rich behavioral context.

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?

Purpose is front-loaded and each clause carries information, but the description is dense and long – the credits/caps/pricing detail is thorough perhaps beyond what is needed to select and call the tool. Still, little is wasted for a tool with this much behavioral surface.

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?

There is no output schema, so the description carries the return-shape burden and does so thoroughly (qualityScore semantics, grounding meaning and its limits, groundingFields, metadata.binding, progress, credits). Auth, cost, and scope prerequisites are all covered, leaving no gap that would block correct invocation.

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 baseline is 3, but the description adds real meaning: it clarifies the interplay of NL fields vs Schema and ties rendering/cost behavior to the render parameter and cache behavior to maxAge. Guidance is useful though not exhaustive on enum edge cases.

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 and resource ('Extract structured data from one public web page') and immediately bounds scope with 'Not a crawler or a search engine: one page per call', which cleanly separates it from batch/read/verify siblings. An agent can tell what it does without opening the schema.

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

Usage Guidelines4/5

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

Explains how to drive it (describe fields in natural language and/or pass a JSON Schema) and gives an explicit when-not ('not a crawler or search engine'), plus auth and cache conditions. It stops short of naming which sibling to use for multi-page or monitoring work, so routing is left to inference.

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