UCP Checker & Router

Get Product Details

get-product-details

Read-only

Get full product details including variant IDs from a UCP-enabled store.

Use after search-catalog to see a product's full declared detail, including its variants.
Pass the Product ID from search results to get all variants with their IDs.

Example: domain: "allbirds.com", productId: "gid://shopify/Product/123456"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	The store domain (e.g., "allbirds.com")
`productId`	Yes	The product ID from search-catalog results (e.g., "gid://shopify/Product/123456")

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds that it returns variant IDs and applies to UCP-enabled stores. It does not disclose any side effects or additional behavioral constraints, but given the read-only annotation, the description provides modest added context.

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

Conciseness4/5

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

The description is composed of a clear purpose statement, usage guidance, and a concrete example, all in a few sentences. The structure front-loads the purpose and places the example last, making it easy to scan.

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?

For a two-parameter, read-only tool with no output schema, the description explains what it returns (full product details with variant IDs) and how to obtain the required input (from search-catalog). This covers the essential information an agent needs to call it correctly.

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 both parameters are described. The description adds the semantic that productId should come from search-catalog results, giving the agent a concrete source for the value and clarifying the relationship between the tools.

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?

The description uses a specific verb ('Get') with a clear resource ('full product details including variant IDs') and references UCP-enabled stores. It distinguishes itself from search-catalog by positioning as a follow-up, so an agent can tell them apart.

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?

It explicitly states 'Use after search-catalog' and explains the flow of passing the Product ID from search results. This gives clear context for when to invoke this tool, though it doesn't list alternatives or exclusions for when not to use it.

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

All UCP Checker & Router tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: domain status, store capabilities, product variants, categories, store listings, aggregate search, single-store search, and policies. The only similar pair, search-all and search-catalog, is clearly differentiated by scope in their descriptions.

Naming Consistency5/5

All tool names follow the same lowercase hyphenated verb_noun pattern, such as check-domain, list-stores, and search-catalog. Verbs are consistently placed first and accurately describe each action.

Tool Count5/5

Eight tools is well within the ideal range, and each tool serves a distinct step in the UCP discovery and shopping workflow. There are no redundant or extraneous tools.

Completeness4/5

The set covers UCP checking, store and category discovery, single-store and multi-store product search, product details, and policy lookup. Direct cart or checkout operations are absent, but discover-store can reveal such capabilities, making the core discovery workflow reasonably complete.

Resources

Need Help?