Skip to main content
Glama
kisasa

Shopify MCP Server

by kisasa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-product-by-id

Fetch a specific Shopify product by ID. Specify fields to limit the response size and reduce token usage.

Instructions

Get a specific product by ID. Supports field selection via 'fields' to reduce response size.

Input Schema

NameRequiredDescriptionDefault
fieldsNoIMPORTANT: Always specify this to minimize token usage and avoid flooding context with unnecessary data. Only the listed fields will be fetched from the API and returned. 'id' is always included. If you are unsure which fields are needed, ask the user before fetching all fields. Example: ["id", "title"] returns only product GID and title. Available: id, title, description, descriptionHtml, handle, status, createdAt, updatedAt, totalInventory, priceRange, media, variants, collections, seo, options, tags, vendor, productType
productIdYesThe product ID (e.g. gid://shopify/Product/123 or just 123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only that field selection reduces response size; it says nothing about required access scopes, behavior when the product ID is not found, or what is returned when 'fields' is omitted.

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?

Two short sentences with zero waste, and the core action is front-loaded ahead of the optional field-selection note.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with no output schema this is minimally adequate, but an agent still cannot tell what the default response contains, whether the call can fail on a bad GID, or how it relates to the product-variant and product-media getters.

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 the 'fields' parameter already carries a long, prescriptive enum description. The description only echoes the token-saving rationale, adding no format or semantics beyond the schema. Baseline 3 applies.

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 a specific product by ID'), which distinguishes it from the list-style sibling get-products. It does not name or differentiate against near neighbors like get-product-variants-detailed or get-product-media, so it falls short of 5.

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?

Usage is only implied: you need an ID, so you use this instead of the list tool. There is no explicit statement of when to prefer get-products, get-product-variants-detailed, or when this tool is inappropriate.

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

Deploy Server

Other Tools