Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Get product details from a URL

get_product_details
Read-only

Find out what a product is and what it costs, from its page URL.

USE THIS WHEN you have the URL of ONE specific product — a store listing, a marketplace item, a manufacturer's page — and you need its fields rather than its prose. Typical jobs: comparing the same item across several stores, tracking a price over time, checking whether something is in stock, ingesting a catalogue, or getting a product photo URL.

DO NOT USE THIS FOR search-results or category pages (it returns one product, not a list), pages behind a login or paywall, or pages that are not about a product. It also cannot reach private or internal addresses.

RETURNS name, description, brand, sku, price (a number), currency (ISO 4217), availability (in_stock | out_of_stock | preorder | unknown), images (up to 5 absolute URLs copied from the page, never invented) and variants. See the output schema for the exact shape. Any field the page does not state comes back null rather than guessed.

HOW: the page is rendered in a real headless browser before extraction, so JavaScript-built pages work where a plain fetch returns an empty shell.

COST $0.01 USDC per call over x402 (the quote lists every network you can pay on: Base, and Solana where offered). No account, no API key, nothing to install, and no gas — the facilitator sponsors it. Call once WITHOUT the payment argument to get back the payment requirements, sign a payment for the quoted amount with your own wallet, base64-encode the x402 payload, and call again with that string as payment.

EVERY RESPONSE SAYS WHERE EACH FIELD CAME FROM. provenance.declared lists the fields whose values match what the merchant published in schema.org JSON-LD — their own number, the one they publish for Google. provenance.inferred lists the ones a model read off the page, which might be a strikethrough price or a neighbouring product. Act on declared values; verify inferred ones if the decision matters.

A URL that redirects to what looks like a DIFFERENT page — a discontinued item bouncing to its category listing — is refused free of charge rather than answered with the wrong product. Retry with allow_redirect: true if you want whatever the URL resolves to.

A failed extraction is not charged. Repeat calls for the same URL within 300 seconds are re-served from a recent render and marked cached: true with the render's original fetchedAt.

Call try_it_free first if you want to see real output before spending anything.

When to use: You have the URL of one product page. Use instead: compare_products for 2-5 URLs (one payment); try_it_free to see the output first. Returns: product (name, price, currency, availability, brand, sku, images, variants), provenance of each field, and the page fetched.

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute https:// URL of a single product page. Not a search or category page.
paymentNoBase64-encoded x402 payment payload. Omit on the first call to receive payment requirements.
allow_redirectNoDefault false. By default a URL that redirects to what looks like a different page (a discontinued item bouncing to its category listing) is refused free of charge, because extracting it would return a real product that is not the one you asked for. Set true if you want whatever the URL resolves to.

Output Schema

NameRequiredDescriptionDefault
pageYes
cachedYesTrue when this answer was re-served from a recent render rather than produced now. Re-serving is still a paid call; it is faster, and the data is as old as cache_age_seconds says.
statusYes
productYes
redirectYesPresent only when the browser landed somewhere other than the URL you gave. The data describes `final`, not `requested`.
provenanceYesWhere each field came from. `declared` matches what the merchant published in schema.org data — their own number. `inferred` was read off the page by a model. Null fields appear in neither. Treat a declared price as a fact and an inferred one as a reading.
settlementYesBase64 x402 settlement receipt, when the facilitator returned one.
cache_age_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / provenance
      Added value: +{
+  "additionalProperties": false,
+  "description": "Where each field came from. `declared` matches what the merchant published in schema.org data — their own number. `inferred` was read off the page by a model. Null fields appear in neither. Treat a declared price as a fact and an inferred one as a reading.",
+  "properties": {
+    "declared": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inferred": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "source": {
+      "enum": [
+        "json-ld",
+        "meta",
+        "json-ld+meta",
+        "none"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "declared",
+    "inferred"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "status",
-  "product",
-  "page",
-  "cached",
-  "cache_age_seconds",
-  "redirect",
-  "settlement"
-]New value: +[
+  "status",
+  "product",
+  "page",
+  "cached",
+  "cache_age_seconds",
+  "provenance",
+  "redirect",
+  "settlement"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true, so the description carries the real burden and does: it discloses the $0.01 x402 payment workflow, the no-account/no-gas model, headless-browser rendering, free-of-charge refusal on cross-page redirects, uncharged failed extractions, 300-second caching with `cached: true`, and the declared-vs-inferred provenance distinction. This is exactly the context beyond annotations that changes how an agent calls the tool.

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

Conciseness3/5

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

Front-loaded and well-sectioned with headers, but the trailing 'When to use / Use instead / Returns' block repeats content already stated in the body (the single-URL condition, compare_products, try_it_free, and the field list). That duplication costs it, though the middle sections are dense and earn their space.

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 a paid, mutation-free, open-world extraction tool with an output schema, this covers every decision point an agent needs: when to use it, when not to, cost and payment mechanics, failure/refund behavior, caching, and provenance semantics. The output schema exists, so the return-value restatement is a bonus rather than a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond it: it spells out the two-call payment dance (call without `payment` to get requirements, sign, base64-encode the x402 payload, call again with it) and the rationale for `allow_redirect` matching the schema note. It reinforces rather than merely restates, though it does not add syntax the schema lacks.

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?

Opens with a specific verb+resource+scope: 'Find out what a product is and what it costs, from its page URL.' It explicitly differentiates from siblings by naming compare_products (2-5 URLs), read_page/page_brief territory (prose rather than fields), and try_it_free, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit USE THIS WHEN conditions ('URL of ONE specific product — store listing, marketplace item, manufacturer's page'), an explicit DO NOT USE list (search/category pages, login/paywalled pages, non-product pages, private/internal addresses), and names alternatives with the condition that selects them (compare_products for 2-5 URLs, try_it_free to preview).

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

All Tollkit 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