Skip to main content
Glama
Sign In

Vera

by ae.waggle
OverviewDiscussionsAdmin

Read product data from a page

extract_products
Read-only

Read one public product page and return the product data it publishes in its structured markup: name, brand, SKU or GTIN, and offers with price, currency and availability. Prices are what the page states, never guessed. Set marketplace to amazon, walmart or shopee for those product pages; these parsers are best-effort and large marketplaces often block automated requests. Costs 1 credit; a failed call costs nothing.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full public http(s) address of the product page.
marketplaceNoSet to "amazon", "walmart" or "shopee" for a product page on that marketplace.
idempotency_keyNoOptional. Send the same key (16 to 128 letters, digits, _ . : -) to retry this exact call safely: a retry within 24 hours returns the first result and is not charged again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes well beyond them: prices are 'what the page states, never guessed' (data fidelity), the marketplace parsers are best-effort and frequently blocked (failure mode), and billing is disclosed as 1 credit with failed calls free. These are exactly the operational traits an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: what it returns first, then the marketplace routing and reliability caveat, then the cost model. No filler, and the most decision-relevant information is front-loaded.

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 no output schema, the description compensates by enumerating the returned fields (name, brand, SKU/GTIN, offers with price/currency/availability) and covers cost, retry safety and failure modes. Nothing an agent needs to call this correctly 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 baseline is 3. The description restates the marketplace enum values already present in the schema and adds only a light characterization of those parsers; it says nothing about url or idempotency_key beyond what the schema already documents.

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?

Names a specific verb (read) and resource (one public product page) and enumerates the returned fields: name, brand, SKU/GTIN, and offers with price, currency and availability. This is clearly distinguishable from siblings like extract_contacts, company_profile or scrape, which target other page types or raw HTML.

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?

Scopes usage to 'one public product page' and tells the agent exactly when to set marketplace (amazon, walmart, shopee pages), plus warns that these parsers are best-effort and often blocked. It does not name an alternative sibling (e.g. scrape) for pages without structured markup, so the routing guidance is clear but not fully explicit about exclusions.

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

All Vera toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources