Skip to main content
Glama
kisasa

Shopify MCP Server

by kisasa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-products

Retrieve Shopify products or search by title, with field selection, pagination, filters, sorting, and count-only results to reduce token usage.

Instructions

Get all products or search by title. Supports field selection via 'fields' and 'countOnly' to get just the count.

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for forward pagination
limitNoNumber of products to return (default 10, max 250)
queryNoRaw query string for advanced filtering (e.g. 'status:active vendor:Nike tag:sale')
beforeNoCursor for backward pagination
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, handle, status, createdAt, updatedAt, totalInventory, vendor, productType, tags, mediaCount, priceRange, media, variants
reverseNoReverse the sort order
sortKeyNoSort key for products
countOnlyNoIMPORTANT: Use this to check result set size before fetching data. Returns only { count: N } without any resource data, saving significant context. Recommended before paginating large result sets.
searchTitleNoSearch by title (convenience filter, wraps in title:*...*). Use 'query' for advanced filtering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses only that field selection and count-only mode exist — both already explained in the schema. It says nothing about read-only nature, pagination limits, cost of fetching variants/media, or default result size.

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?

Two short sentences with the capability statement front-loaded and no filler. It is efficient, though it leans on the schema for anything substantive.

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

Completeness2/5

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

A 9-parameter list tool with no annotations and no output schema needs more: nothing explains the return shape, what countOnly returns versus normal results (only the schema hints), or how query/searchTitle/sortKey interact. An agent must read the entire schema to call this safely.

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 the baseline applies: the schema documents pagination, query syntax, sort keys, and field enums in detail. The description's mention of 'fields' and 'countOnly' merely restates what the schema already says.

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 clear verb and resource (list products) plus the search-by-title mode, which distinguishes it from get-product-by-id. It doesn't explicitly name get-product-by-id or get-product-variants-detailed as alternatives, so sibling differentiation is only implied.

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?

'Search by title' implies when searchTitle applies, but the description never says when to use this list tool versus get-product-by-id, get-collection-by-id, or the variants tools, nor when to prefer 'query' over 'searchTitle' (that contrast lives only in the schema).

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