Skip to main content
Glama

LinkVet

Extract JSON-LD / schema.org structured data

schema_extract
Read-onlyIdempotent

Extract schema.org structured data from a page: every JSON-LD block (flattening @graph), the list of @types (Product, Article, Recipe, Event, Organization, FAQPage...), up to 30 typed items with their fields (prices, ratings, dates, authors), plus microdata itemtypes. Great for pulling clean product/article facts.

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": "schema_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety/idempotency is covered. The description usefully adds behavioral detail beyond that: @graph flattening, a cap of "up to 30 typed items," and inclusion of microdata itemtypes — a real extraction limit an agent should know. It does not say what happens when a page has no structured data or when the URL fetch fails.

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?

A single front-loaded sentence: verb and resource come first, then the enumerations of what is returned. The parenthetical examples (Product, Article, prices, ratings) earn their place by concretizing output shape, though the trailing "Great for..." clause is slightly promotional in tone.

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?

With no output schema, the description must carry the return-value burden, and it does — it describes the JSON-LD blocks, @type list, typed item fields, and microdata in enough detail to set expectations. For a one-parameter read tool this is close to complete; only empty-result and fetch-failure behavior are unaddressed.

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 (url) at 100% schema description coverage, so the schema already defines it. The description adds nothing about the URL beyond "from a page" — no note on http/https requirements, redirects, or whether non-public/authenticated pages are supported. Baseline 3 is appropriate since the schema does the work.

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?

"Extract schema.org structured data from a page" gives a specific verb (extract) and a specific resource (schema.org/JSON-LD structured data), then enumerates the artifact types returned (@graph blocks, @types, typed items, microdata itemtypes). That makes it clearly distinct from generic fetch/read tools like read_page or page_metadata, though it never names those siblings explicitly.

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?

The closing line "Great for pulling clean product/article facts" implies the intended use case (getting parsed commerce/editorial data rather than raw HTML), but there is no explicit when-to-use/when-not guidance and no named alternative such as read_page or page_metadata for pages lacking structured data.

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