Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

jsonld_product_parser

Extract schema.org Product data (offers, ratings, reviews) from a page

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jsonld_product_parser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage URL (or supply html)
htmlNoRaw HTML (or supply url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what happens when a page contains no JSON-LD, whether partial results are returned, or whether any error/empty shape is signaled. The read-only nature is inferable from "extract," but nothing about failure modes, fetch behavior, or coverage is disclosed.

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 with the resource first and the extracted payload parenthetically listed; no filler. It is arguably too short for a parser with unstated fallback behavior, but nothing present is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 usefully names the returned entities (offers, ratings, reviews), which is the most valuable thing it does. However, for a scraper/parser with zero annotation coverage and no explanation of empty-result or invalid-HTML handling, an agent cannot predict outcomes in edge cases.

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% and both parameters are documented in the schema, including the either/or relationship between url and html. The description adds no syntax, format, or precedence detail beyond that, so it meets the baseline for fully-covered schemas without exceeding it.

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?

Names a specific verb and resource ("Extract schema.org Product data") and enumerates the payload it targets (offers, ratings, reviews), so the agent knows exactly what comes back. It does not explicitly say it parses embedded JSON-LD rather than visible markup, nor how it differs from siblings like product_intel_composite, so sibling differentiation rests on the tool name alone.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this parser over product_intel_composite, storefront_xray_composite, or the other product/review tools. It also never states which of url or html to prefer when both are available, or when each is appropriate.

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