Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_jsonld_product_parser

Extract schema.org Product data, including offers, ratings, and reviews, from a page URL or raw HTML for e-commerce analysis.

Instructions

[E-Commerce Intelligence] Extract schema.org Product data (offers, ratings, reviews) from a page Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_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 observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add real behavioral context: the tool performs a network call to ecom.caelaralabs.com, and measured p50/p95 latencies are given, which helps with timeout planning. However, it is silent on what happens when a page has no Product JSON-LD, whether it follows redirects or respects robots, and whether failures return empty results or errors.

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?

Front-loaded with the core action and field list in one sentence, with benchmark and endpoint metadata trailing behind. Every element is short, though the benchmark citation and host string read as boilerplate rather than decision-relevant guidance.

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 and no annotations, the description does well to name the extracted fields (offers, ratings, reviews). But it never says what the return shape is (a single JSON-LD object vs. an array of products) or how missing/unparseable markup is reported, which matters for an extraction tool whose output is undocumented.

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 the schema already explains the url/html alternation ('or supply html'), so the description adds no parameter meaning beyond structured data. Baseline 3 applies.

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?

States a specific verb and resource: 'Extract schema.org Product data (offers, ratings, reviews) from a page'. The parenthetical enumerates the extracted fields, making the scope concrete. It does not differentiate itself from adjacent siblings such as review_sentiment_parser or product_intel_composite, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives like the composite product-intel tool. The only implicit signal is 'from a page', which an agent could infer from the parameter names alone.

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

Deploy Server

Other Tools