Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Extract structured page data

web-intelligence_structured-page-extract
Read-onlyIdempotent

Extract caller-defined fields from one public webpage. A field is returned only when a selector, JSON-LD property, or matching meta tag contains it. Otherwise the value is null. Price $0.05 USDC. POST /api/v1/web-intelligence/structured-page-extract. An unpaid call returns the x402 payment terms and does not run.

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>",
      "schema": "<schema>"
    },
    "name": "web-intelligence_structured-page-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl, string, length 8 to 2000. Required.
schemaYesschema, array. Required.

Output Schema

NameRequiredDescriptionDefault
fieldsNofields. Array.
sourcesNosources. Array.
finalUrlNofinalUrl. String.
warningsNowarnings. Array.
httpStatusNohttpStatus. Number.
contentTypeNocontentType. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
requestedUrlNorequestedUrl. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the null-fallback rule ('a field is returned only when a selector, JSON-LD property, or matching meta tag contains it. Otherwise the value is null'), the price ($0.05 USDC), and the critical failure mode that an unpaid call returns x402 payment terms and does not run. Missing only secondary traits like rate limits or behavior on JS-rendered pages.

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?

Five short sentences, front-loaded with purpose and fallback semantics before the operational details. The endpoint string is somewhat redundant with tool metadata, but nothing else is wasted.

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?

With an output schema, full annotation coverage, and 100% parameter description coverage, the description supplies the only missing pieces an agent needs: the resolution/fallback rule and the payment-gating behavior. Nothing essential to calling it correctly is absent.

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 100%, so baseline is 3; the description earns above that by explaining what a schema entry actually resolves against (selector, JSON-LD property, or meta tag) and what happens when none match. This adds genuine semantic meaning to the 'selector' and 'attribute' fields that the schema alone does not convey.

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 a precise resource ('caller-defined fields from one public webpage'), which implicitly but clearly distinguishes it from fixed-schema siblings like website-metadata-extract or website-contact-extract. An agent knows exactly what this tool returns 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 Guidelines3/5

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

Usage is only implied: 'caller-defined fields' and 'one public webpage' suggest when to pick this over fixed-extraction siblings, but no alternative is named and no explicit when-not condition is given. It is adequate but leaves routing between siblings 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