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

ghl-mcp-server-v2

by zackscriven

ghl_store_create_shipping_carrier

Create a shipping carrier for a sub-account by providing carrier name, location/agency ID, services, and callback URL used to fetch shipping rates.

Instructions

Create Shipping Carrier The "Create Shipping Carrier" API allows adding a new shipping carrier. Endpoint: POST /store/shipping-carrier (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_carrier"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / services / items / title
      Added value: +"ShippingCarrierServiceDto"
    • addedInput schema / properties / body / title
      Added value: +"CreateShippingCarrierDto"
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the auth prerequisite (Sub-Account/location token) and version header, which is real value, but says nothing about duplicate-carrier behavior, whether callbackUrl is validated/called externally, or side effects on existing zones/rates.

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?

The endpoint and version/source metadata are front-loaded and useful, but the second line ("The 'Create Shipping Carrier' API allows adding a new shipping carrier") simply restates the name and title. It's short overall, yet one of four lines is pure redundancy.

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 single-parameter creation tool with a rich nested schema and full annotations, this covers the mechanical basics (endpoint, version, token scope). It omits behavior an agent would want before writing data: what happens on duplicate carrier names, and that callbackUrl must be a live public endpoint the CRM will call.

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%, with per-field descriptions and examples for the nested body (name, altId, altType, callbackUrl, services). The description adds no parameter-level meaning at all beyond the token requirement, so the baseline 3 applies while the schema does the work.

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 gives a specific verb and resource ("Create Shipping Carrier"/"adding a new shipping carrier") plus the exact endpoint POST /store/shipping-carrier, so the operation is unambiguous. It does not distinguish this tool from close siblings such as ghl_store_update_shipping_carrier or ghl_store_create_shipping_rate, leaving that differentiation to the name.

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 "create" and the stated endpoint; there is no explicit guidance on when to use this versus updating an existing carrier or creating a shipping rate. The one genuinely useful constraint given is 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