Skip to main content
Glama

Shopify: List Shipping Zones

list_shopify_shipping_zones
Read-onlyIdempotent

[Shopify Shipping Zones] [What it does] Lists the Shopify Markets countries and regions available to one exact owned Shopify store, plus that store's currency. Shopify only; it does not list existing Shipping Profiles and it does not create or change anything. [When to use] Call after list_stores and before create_shopify_shipping_profile to obtain authoritative country_codes and currency for that exact store. [When not to use] Do not use it for non-Shopify stores, to inspect existing profiles, or to choose a custom profile name, zone name, rate name, or amount. Existing profiles come from list_stores.stores[].shipping_profiles. [How to use] Copy one exact Shopify dsers_store_id from list_stores. Select one or more returned shipping_zones[].country_code values for create_shopify_shipping_profile.country_codes, and copy the returned currency exactly. Choose a zone_name that clearly describes the selected countries. If shipping_zones is empty, stop and do not create a profile with guessed country codes. [Side effects] Read-only; no Shopify or DSers configuration is changed. [Confirmation] None required.

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": {
      "dsers_store_id": "<dsers_store_id>"
    },
    "name": "list_shopify_shipping_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_store_idYesExact owned Shopify DSers store ID copied from list_stores.

Output Schema

NameRequiredDescriptionDefault
currencyYesConnected Shopify store currency to copy into create_shopify_shipping_profile.currency
dsers_store_idYesExact DSers Shopify store ID queried
shipping_zonesYesShopify Markets countries and regions available for the new Shipping Profile
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the side-effects sentence mostly restates them. The description does add genuine behavioral context beyond annotations: the empty-result stop rule preventing guessed country codes, and the note that currency must be copied exactly. It stops short of describing pagination or result size, but the output schema covers the return shape.

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?

Front-loaded bracketed sections make scanning easy and each section carries actionable content (ordering, exclusions, field mapping, abort rule). The label scaffolding is slightly heavy for a one-parameter read tool, but no sentence is filler.

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

Completeness5/5

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

For a simple read tool with an output schema, the description covers everything an agent needs: where the ID comes from, how to map `shipping_zones[].country_code` and `currency` into create_shopify_shipping_profile, and what to do when the list is empty.

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% and the single parameter is documented in the schema, so the baseline would be 3; the description adds meaning by specifying provenance (one exact Shopify `dsers_store_id` copied from `list_stores`) and that only owned stores are valid, which reinforces the schema's numeric pattern constraint.

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?

States a specific verb and resource ("Lists the Shopify Markets countries and regions available to one exact owned Shopify store, plus that store's currency") and immediately delimits the scope by saying it does not list Shipping Profiles and does not create or change anything, which separates it from create_shopify_shipping_profile and list_stores.

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

Usage Guidelines5/5

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

Gives explicit ordering guidance ("Call after `list_stores` and before `create_shopify_shipping_profile`"), a named when-not-to-use list (non-Shopify stores, inspecting existing profiles, choosing names/amounts, with the pointer that existing profiles live in `list_stores.stores[].shipping_profiles`), and an abort condition when the result is empty.

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.