GoHighLevel MCP

ghl_get_order

Retrieve a specific GoHighLevel order by its ID to access complete order details.

Instructions

Get a specific order by ID.

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": {
      "orderId": "<orderId>"
    },
    "name": "ghl_get_order"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Get' which implies a read operation, but does not mention response format, error conditions, authorization needs, or any other behavioral traits. For a tool with no annotations, this is a significant gap.

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

Conciseness5/5

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

The description is a single sentence, highly concise, and front-loaded with the core purpose. No redundant information is present, earning a perfect score for conciseness.

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

Completeness4/5

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

Given the low complexity (one parameter, no output schema), the description is largely sufficient for a basic get-by-id operation. It clearly states what the tool does and what input is required. However, without an output schema or annotation, it could benefit from mentioning what the response returns, but this is not critical for a simple read.

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 0%, but the description's phrase 'by ID' directly explains the purpose of the single orderId parameter. However, it merely restates the schema's field name and adds minimal semantic value beyond that. The description partially compensates for the lack of parameter details but could be more explicit.

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?

The description uses a specific verb ('Get') and resource ('a specific order') with a clear identifier ('by ID'), which distinguishes it from sibling tools like ghl_get_orders (plural) that likely list orders. It unambiguously states what the tool does.

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 description implies usage for fetching a single order by ID, but it does not explicitly differentiate from alternatives like ghl_get_orders or provide when-to-use/when-not-to-use guidance. The context is clear but no exclusions or alternative references are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server