Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_store_create_shipping_zone

Create a new shipping zone for a store location, defining supported countries and optional states to control shipping availability.

Instructions

Create Shipping Zone The "Create Shipping Zone" API allows adding a new shipping zone. Endpoint: POST /store/shipping-zone (Version header: v3; source: v3/store-v3.json) Requires a Sub-Account (location) token.

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": {
      "body": "<body>"
    },
    "name": "ghl_store_create_shipping_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / countries / items / properties / states / items / title
      Added value: +"ShippingZoneCountryStateDto"
    • addedInput schema / properties / body / properties / countries / items / title
      Added value: +"ShippingZoneCountryDto"
    • addedInput schema / properties / body / title
      Added value: +"CreateShippingZoneDto"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare non-read-only, open-world, non-idempotent, and non-destructive behavior. The description adds the POST endpoint, v3 version header, source, and the important Sub-Account token requirement, which is meaningful context beyond annotations, though it does not describe return or error behavior.

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?

The description is short and front-loaded with the operation and endpoint. The first two lines repeat the tool name, and citing 'source: v3/store-v3.json' is mostly boilerplate, but there is no significant wasted length.

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

Completeness4/5

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

For a create tool with a complex nested body schema and rich annotations, the description supplies the endpoint, API version, and authentication prerequisite. No output schema exists, but the description is sufficient for correct invocation and does not need to explain return values.

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%, and the nested body fields are fully documented with descriptions and examples. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states a specific verb and resource ('Create Shipping Zone') and gives the endpoint, so the operation is clear. It distinguishes itself in practice from update/list siblings by being a create operation, though it does not explicitly name those alternatives.

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?

It says the API adds a new shipping zone and requires a Sub-Account token, which gives useful context. However, it does not state when to use this versus ghl_store_update_shipping_zone, ghl_store_list_shipping_zones, or any other sibling, nor does it give exclusions.

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