Skip to main content
Glama

Check a product link now

check_product_link
Read-onlyIdempotent

Fetch one product page live and return whether it still exists, its current price and stock. Use it on a url from search_products before quoting a price to the shopper. Only allowlisted retailer and brand-store urls; robots.txt is honoured. status: live, out_of_stock, dead (gone), blocked (retailer refused; hand the shopper the url), not_allowed, unreadable. No key needed.

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

Input Schema

NameRequiredDescriptionDefault
urlYesProduct page url, e.g. the url field of a search_products result.

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
priceNo
titleNo
statusNo
currencyNo
checked_atNo
availabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing the allowlist restriction, robots.txt compliance, the 'no key needed' auth situation, and per-status handling guidance ('blocked (retailer refused; hand the shopper the url)'). That last point tells the agent what to do with a failure, not just that it happened.

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?

Front-loaded with the action and return, then routing guidance, then constraints, then a compact status enumeration. Every clause carries information; nothing is restated from the schema or annotations.

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?

For a one-parameter read whose output schema already defines the return shape, the description supplies everything remaining: preconditions, allowlist/robots constraints, auth, and the meaning plus handling of each status value. Nothing an agent needs in order 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.

Parameters4/5

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

Schema coverage is 100% with a single url parameter already well documented, so the schema carries most of the weight. The description still adds value by tying the url to its source ('a url from search_products') and constraining it to one product page, which the schema alone does not convey.

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?

States a specific verb and resource ('Fetch one product page live') plus exactly what it returns: existence, current price and stock. The word 'one' scopes it against bulk siblings, so an agent can tell it apart from search_products or find_retailers without opening a schema.

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?

Gives explicit timing and provenance: 'Use it on a url from search_products before quoting a price to the shopper,' which names both the sibling that supplies input and the workflow step. It stops short of stating when not to call it (e.g., bulk checks or non-product pages), but the 'one product page' framing implies that boundary.

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