Skip to main content
Glama

Shopify: Create Shipping Profile

create_shopify_shipping_profile

[Shopify Shipping Profile] [What it does] Creates one Shipping Profile with one zone and one custom flat rate in one exact Shopify store. Shopify only; WooCommerce, eBay, and other sales channels are rejected before the write. [When to use] Use when the user wants a new Shopify Shipping Profile before publishing products. [When not to use] Do not use it to select an existing profile; read current choices from list_stores.stores[].shipping_profiles. Do not use it for non-Shopify stores or when list_shopify_shipping_zones.shipping_zones is empty. [How to use] First call list_stores, select one exact row whose sales_channel_name equals Shopify case-insensitively, and copy its dsers_store_id. Then call list_shopify_shipping_zones for the same store, copy one or more returned shipping_zones[].country_code values into country_codes, and copy its currency exactly. Choose a zone_name that describes the selected countries, then provide the profile name, custom rate name, and non-negative amount. The service creates exactly one zone and rate. After success, call list_stores again and use the returned profile and location IDs for product publishing. This write is not idempotent; if the result is unknown, inspect Shopify and list_stores and never retry automatically. [Side effects] Creates a Shipping Profile in the selected Shopify store. [Confirmation] Requires explicit confirmation showing the store, profile, zone, countries, rate name, amount, and currency.

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>",
      "profile_name": "<profile_name>",
      "zone_name": "<zone_name>",
      "country_codes": "<country_codes>",
      "custom_rate_name": "<custom_rate_name>",
      "amount": "<amount>",
      "currency": "<currency>"
    },
    "name": "create_shopify_shipping_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesNon-negative flat-rate amount in major currency units, without symbols or separators.
currencyYesCurrency copied exactly from list_shopify_shipping_zones for the same store; Shopify ultimately applies the store currency.
zone_nameYesName of the single delivery zone to create.
profile_nameYesNew Shopify Shipping Profile display name.
country_codesYesOne to 250 unique shipping_zones[].country_code values copied from list_shopify_shipping_zones for the same store. Paste JSON example: ["US","CA"].
dsers_store_idYesExact owned Shopify DSers store ID copied from list_stores.
custom_rate_nameYesDisplay name of the single custom flat rate.

Output Schema

NameRequiredDescriptionDefault
messageYesCreation acknowledgement and verification guidance
profile_nameYesCreated Shopify Shipping Profile name
dsers_store_idYesExact DSers Shopify store ID that received the 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.8/5.0
Behavior5/5

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

Goes well past the annotations: states the write is not idempotent, forbids automatic retry on unknown results, specifies a manual verification path via Shopify and `list_stores`, and mandates an explicit confirmation listing store, profile, zone, countries, rate name, amount, and currency. The non-Shopify rejection and "creates exactly one zone and rate" constraints are behaviors the annotations alone do not convey.

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?

Bracketed section headers make it scannable and front-loaded, with the what/when-not established before the procedure. The "Side effects" line largely restates the opening sentence, and the how-to section is dense enough that it borders on a runbook rather than a description.

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 7-required-parameter mutation with an output schema already available, the description covers preconditions, ordering, platform gating, confirmation, failure handling, and post-write verification. Nothing an agent needs in order to call this correctly and safely is missing.

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 description coverage is 100%, so the baseline is 3; the description earns extra by specifying provenance for values the schema only describes abstractly — `dsers_store_id` from a Shopify row in `list_stores`, `country_codes` from `list_shopify_shipping_zones`, and `currency` copied exactly with Shopify applying the store currency. It does not add format detail for `amount` beyond what the schema pattern already encodes.

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 ("Creates one Shipping Profile with one zone and one custom flat rate in one exact Shopify store") and bounds the scope precisely: single zone, single rate, single store, Shopify only. An agent can distinguish this from the sibling list/read tools without opening the schema.

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?

Explicit "When to use", "When not to use", and named alternatives: read existing choices from `list_stores.stores[].shipping_profiles`, and do not proceed when `list_shopify_shipping_zones.shipping_zones` is empty. It also gives a concrete prerequisite chain (`list_stores` → `list_shopify_shipping_zones` → create) rather than leaving ordering to inference.

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.