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

ghl-mcp-server-v2

by zackscriven

ghl_store_delete_shipping_carrier

DestructiveIdempotent

Deletes a specified shipping carrier by ID using a sub-account token, removing it from the store's shipping options.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
shippingCarrierIdYesID of the shipping carrier that needs to be returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/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 non-redundant operational context: the concrete HTTP method/path, the v3 version header, and the fact that a Sub-Account (location) token is required — an auth constraint an agent must satisfy before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource, which is good, but the first two lines restate each other ('Delete shipping carrier' / 'Delete specific shipping carrier with Id :shippingCarrierId'), and the trailing '(Version header: v3; source: v3/store-v3.json)' is metadata noise for an agent.

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?

Wait — reassessing: with no output schema, a destructive mutation tool should say what breaks when the carrier is deleted (e.g. effect on existing rates/zones) or how failures are reported. The description gives endpoint/auth context but no consequence or error behavior, so this is a gap rather than a strength.

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%, so baseline is roughly 3. The description only mentions shippingCarrierId (redundantly with the schema) and stays silent on the required altId/altType pair; the 'Sub-Account (location) token' phrase only loosely hints at their purpose, and the schema's own shippingCarrierId text ('needs to be returned') is misleading for a delete.

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 ('Delete') and resource ('shipping carrier') and names the identifying key, which distinguishes it cleanly from the sibling get/update/list/create shipping-carrier tools without needing their schemas.

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?

The endpoint line and the 'Requires a Sub-Account (location) token' note imply the prerequisite context, and 'with Id :shippingCarrierId' implies a carrier must already exist. However there is no explicit when-to-use guidance, no warning to first detach the carrier from shipping rates/zones, and no routing to sibling tools.

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