Skip to main content
Glama
Sign In
mcp-shopify

mcp-shopify

by cloud9-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

shopify_list_customers

List Shopify customers in paginated batches. Provide limit and page_info to navigate through customer records.

Instructions

List customers with pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
page_infoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 burden of behavioral disclosure, but it only states 'List customers with pagination.' It does not disclose that this is a read-only operation, how pagination works, whether it returns full customer objects, or any limits/rate considerations. This is minimal but not contradictory.

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?

The description is a single front-loaded sentence with no filler: verb, resource, and key behavior are all present. Every word earns its place, and there is no redundant restating of the tool name.

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?

For a tool with no annotations and no output schema, this description is too sparse for fully confident invocation. It mentions pagination but omits how to handle page_info, what default limit applies, whether more pages exist, and what the response structure looks like. Contextual completeness is only slightly better than a bare name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the two params. It vaguely relates to 'pagination' but does not explain that limit controls page size (default 50, max 250) or that page_info is a cursor token. The parameter names are somewhat self-explanatory, but the description adds little semantic value.

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?

The description clearly states the verb ('List'), resource ('customers'), and a key behavior ('with pagination'), which distinguishes it from get_customer and search_customers at a surface level. It does not explicitly state scope or contrast itself with sibling tools, so it misses full clarity.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives like shopify_search_customers or shopify_get_customer. There are no exclusions, prerequisites, or context cues, leaving the agent to infer usage solely from the tool name.

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