Skip to main content
Glama

Get product details

get_product_details
Read-onlyIdempotent

Get product details, variants, prices, shipping and catalogue availability for search results. Keep the search country and currency. Use include_media for all picture links and available video. Returned links are affiliate links.

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": {
      "product_ids": "<product_ids>"
    },
    "name": "get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoDelivery country (ISO 3166-1 alpha-2). Default: client location, else DE.
currencyNoPrice currency. Default follows the delivery country.
product_idsYesIDs from search results.
include_mediaNoAdd all image links and available video.

Output Schema

NameRequiredDescriptionDefault
itemsYes
countryYes
currencyYes
checked_atNo
availabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description is not required to restate them. It adds genuinely new behavior: returned links are affiliate links, media is only included on request via include_media, and results include catalogue availability — all context an agent cannot get from the annotations.

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?

Four short sentences with zero filler, front-loaded with what is returned before parameter guidance and the affiliate disclaimer. Every sentence carries distinct information an agent needs.

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 an output schema present, the description does not need to specify return structure, and it appropriately stops at a summary plus the affiliate-link caveat. For a simple four-parameter read tool with full schema coverage, this is nearly complete; only explicit sibling routing is absent.

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 all four parameters are documented structurally, establishing a baseline of 3. The description adds some meaning beyond the schema by instructing that country and currency should mirror the originating search and by clarifying that include_media returns all picture links plus available video, but it does not explain the product_ids limit of 10 or the ID format.

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 ('Get product details') and enumerates exactly what is retrieved: variants, prices, shipping, catalogue availability. The phrase 'for search results' signals it operates on IDs produced by search, giving partial differentiation from search_products, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

'Keep the search country and currency' and 'for search results' imply this is a follow-up call after a product search, which is useful implied usage context. However, it never states when to prefer search_products or show_pictures instead, nor any prerequisite or exclusion, so the routing logic is left to inference.

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