Skip to main content
Glama

Get product

get_product
Read-only

Fetch one catalog product in the selected workspace by product id or SKU — returned in any status (draft, active, or archived; check the status field) — with every catalog field: prices, cost, stock and trackInventory, availability, variant fields, all attributes (characteristics) and translations, identifiers, weight and dimensions, images, videos, bundle components and related products; plus its model, warehouse and supplier by name, supplierOffers (what the supplier last said: quantity, restock date, purchase price, state), every sales channel with its listing and moderation state, the collections it is in and its model's review summary; channelTexts (the title and bullet points written for a channel such as Amazon, per language), safetyDocuments (safety PDFs a marketplace receives) and gpsr (the manufacturer and EU responsible person with their emails, each from the brand, else the supplier). A bundle's stock and cost are derived from its components. Provide exactly one known identifier; use search_products first when unsure (search covers active products only).

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

Input Schema

NameRequiredDescriptionDefault
idNoThe product id returned by search_products.
skuNoThe product SKU returned by search_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The product id returned by the matching search/list tool."New value: +"The product id returned by search_products."
  3. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"The product id returned by the matching search/list tool."
    • addedInput schema / properties / sku / description
      Added value: +"The product SKU returned by search_products."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations it discloses non-obvious behavior: any status is returned including draft and archived (with a warning to check the status field), and bundle stock and cost are derived from components. It also notes the gpsr fallback from brand to supplier. It does not say what happens on a miss (error vs empty) or which wins when both identifiers are supplied.

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

Conciseness2/5

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

The core purpose is front-loaded, but the body is a single 200-word run-on sentence enumerating a dozen field groups separated by semicolons, which is hard to scan. Because there is no output schema the enumeration has some value, yet it should have been a structured list rather than a wall of embedded clauses.

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

Completeness4/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 carries the return-value burden and does so thoroughly — enumerating prices, stock, variants, attributes, translations, channels, safetyDocuments and gpsr. Gaps are error behavior and identifier conflict resolution, which matter but are secondary for a read-only lookup.

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 coverage is 100% and both parameters are already documented as coming from search_products, so the baseline applies. The description does add one constraint the schema does not express — "exactly one known identifier" — but that is the only semantic increment.

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 and resource ("Fetch one catalog product") plus the lookup key (product id or SKU) and scope ("in the selected workspace"), and explicitly contrasts itself with search_products. An agent can distinguish it from get_product_pricing, list_channel_products and the other product siblings 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 Guidelines5/5

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

Ends with explicit routing: "Provide exactly one known identifier; use search_products first when unsure (search covers active products only)." That names both the alternative tool and the condition that selects it, and explains why a search may be needed (archived/draft items are invisible to search).

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