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

ghl-mcp-server-v2

by zackscriven

ghl_store_create_shipping_rate

Create a shipping rate in a GoHighLevel store shipping zone by supplying the zone ID and rate details, including pricing, conditions, and carrier options.

Instructions

Create Shipping Rate The "Create Shipping Rate" API allows adding a new shipping rate. Endpoint: POST /store/shipping-zone/{shippingZoneId}/shipping-rate (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>",
      "body": "<body>"
    },
    "name": "ghl_store_create_shipping_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
shippingZoneIdYesID of the item that needs to be returned

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.8/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 genuinely new information beyond annotations by disclosing the required auth scope (Sub-Account/location token) and the exact POST endpoint, though it says nothing about failure modes or what happens if the zone is invalid.

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 block is short and the endpoint/auth lines are front-loaded and useful. But two of the four lines are pure restatement of the tool name and title, which dilutes the signal; trimming them would leave a tighter definition.

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 non-idempotent mutation with full schema coverage and annotations present, the description covers auth scope and the target endpoint, which is enough to invoke it. It omits any mention of behavior on invalid shippingZoneId or duplicate rates, and with no output schema there is no return-value burden, so it sits at minimum viable.

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 DTO is fully documented with per-field descriptions and examples, so the schema does the heavy lifting. The description adds only indirect context via the endpoint path, confirming shippingZoneId is a path parameter, but contributes no field-level semantics of its own.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb+resource (create a shipping rate) and the endpoint path reveals it is scoped under a shipping zone, which distinguishes it somewhat from ghl_store_update_shipping_rate and ghl_store_create_shipping_carrier. However, the first two lines are essentially a restatement of the tool name and add no differentiating detail about what a 'shipping rate' is in this system.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus update_shipping_rate, create_shipping_carrier, or upsert_settings. The only contextual hint is the prerequisite note that a Sub-Account (location) token is required, which is useful but does not constitute when-to-use guidance.

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