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

ghl-mcp-server-v2

by zackscriven

ghl_store_delete_shipping_rate

DestructiveIdempotent

Delete a specific shipping rate from a GoHighLevel store using its shipping zone ID and rate ID, with location or agency context for the request.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
shippingRateIdYesID of the shipping rate that needs to be returned
shippingZoneIdYesID of the shipping zone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/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 structurally. The description adds real value with the auth requirement (location token) and the exact endpoint, but says nothing about side effects — e.g., whether the parent shipping zone is affected or what happens to existing orders referencing the rate.

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 action, then the identifier, then the endpoint and auth note — a sensible escalation of detail. The opening 'Delete shipping rate' duplicates the title, and the source-file reference ('v3/store-v3.json') is arguably metadata rather than guidance, but nothing is bloated.

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 four-required-parameter destructive call with no output schema, the definition covers endpoint and auth but omits the two things an agent most needs: whether altId/altType must point to the owning location, and whether deletion is blocked or cascaded when the rate is in use.

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 75%, just below the threshold where the schema would carry the burden alone. The description names only shippingRateId, leaving the equally required altId (Location/Agency Id) and the altType enum unaddressed, so it does not compensate for the gap — the baseline 3 applies.

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?

States a specific verb (delete) and resource (shipping rate) and pins it to exact identifiers, with the REST path confirming the zone→rate hierarchy. An agent can distinguish it from ghl_store_delete_shipping_zone and ghl_store_delete_shipping_carrier, though no sibling is named explicitly.

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 by the verb — there is no statement of when to delete vs. deactivate/update, and no mention of alternatives such as ghl_store_update_shipping_rate. The one genuinely useful guideline is the prerequisite that a Sub-Account (location) token is required.

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