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

ghl-mcp-server-v2

by zackscriven

ghl_store_delete_shipping_zone

DestructiveIdempotent

Deletes a store shipping zone by shippingZoneId for a specified location, removing it from the GoHighLevel store configuration.

Instructions

Delete shipping zone Delete specific shipping zone with Id :shippingZoneId Endpoint: DELETE /store/shipping-zone/{shippingZoneId} (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": {
      "shippingZoneId": "<shippingZoneId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_store_delete_shipping_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
shippingZoneIdYesID of the item that needs to be returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context beyond that: the underlying DELETE endpoint, the API version header, and the requirement for a Sub-Account (location) token — the auth prerequisite is exactly the kind of detail annotations cannot express. It stops short of saying what else is removed with the zone (e.g. associated rates) or whether deletion is recoverable.

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 with the verb and resource in the first line, followed by the target parameter and then the endpoint/auth facts. The trailing API metadata (version header, source JSON filename) is mildly noisy but does not obscure the essential information.

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

Completeness3/5

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

For a destructive, three-parameter mutation with no output schema, the description covers endpoint, identifier and auth. It does not address consequences (cascade to shipping rates), confirmation expectations, or failure behavior on an invalid ID, which an agent about to destroy data would want.

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 coverage is 67%, right at the baseline, and the description only clarifies shippingZoneId as the identifier of the zone to delete. Notably the schema's own description for shippingZoneId is wrong ("ID of the item that needs to be returned"), and the description is the only thing correcting that impression. altType (enum) and the altId/altType relationship are left unexplained in both places.

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 ("Delete shipping zone") plus the exact identifier used to target it. Among the many store shipping siblings (get/list/create/update), the destructive operation is unmistakable from the first line.

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?

Usage is only implied: the agent must infer that this is the tool for removing an existing zone when it already has a shippingZoneId. There is no explicit statement of when not to use it, nor a pointer to the get/update siblings for related operations. The one concrete guidance offered is the Sub-Account token prerequisite.

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