Skip to main content
Glama
web-insights-mcp
by nqcthedev

Extract structured data

extract_structured
Read-onlyIdempotent

Extract structured page data as JSON, including schema.org JSON-LD, microdata, Open Graph tags, contacts, headings, and tables for product, pricing, or company research.

Instructions

Extract machine-readable data from a page as JSON: schema.org JSON-LD blocks (parsed, with validity errors), microdata items, Open Graph and Twitter card tags, contact details (mailto emails, tel phone numbers, social profile links, contact pages), the heading outline (h1-h6) and HTML tables (headers + rows). Use it to read product/price/rating/event/organization data, collect a company's public contact channels, or turn a pricing or comparison table into rows. Choose sections with include to keep the response small.

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>"
    },
    "name": "extract_structured"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL. A bare domain like example.com is treated as https://example.com.
includeNoSections to return. Any of: meta, json_ld, microdata, open_graph, contacts, headings, tables. Defaults to all.
max_table_rowsNoMaximum rows returned per table.

Output Schema

NameRequiredDescriptionDefault
urlYes
metaNo
jsonLdNo
statusYes
tablesNo
twitterNo
contactsNo
finalUrlYes
headingsNo
microdataNo
openGraphNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral detail: output is JSON, JSON-LD is parsed with validity errors, tables include headers and rows, and section selection can shrink the response. It does not discuss auth or rate limits, but that is a minor gap against the annotation coverage.

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?

The description is front-loaded with the extraction capability and then gives use cases and an include tip, with no filler. It is dense because it packs several section names and examples into one paragraph, but every clause serves to scope the tool. A 4 reflects good but not maximally crisp structure.

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?

Given three parameters, full schema description coverage, an output schema, and annotations covering the safety profile, the description supplies the remaining context an agent needs: what sections are extracted, why to use it, and how include controls response size. No critical calling detail is missing.

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?

Schema description coverage is 100%, so the schema already explains url, include, and max_table_rows. The description adds only a rationale for using include ('to keep the response small') and does not mention max_table_rows, so it provides little meaning beyond the structured schema. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Extract machine-readable data from a page as JSON,' then enumerates the exact data types returned, including JSON-LD, microdata, Open Graph, contacts, headings, and tables. This is clear enough to distinguish it from a raw fetch or audit tool, though it does not name a sibling or explicitly contrast itself with one, so it falls short of the top calibration.

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?

It gives concrete when-to-use scenarios: reading product, price, rating, event, or organization data; collecting public contact channels; or converting pricing and comparison tables into rows. It also points to the include parameter for keeping responses small. It lacks explicit when-not-to-use guidance or named alternatives, so 4 rather than 5.

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