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

ghl-mcp-server-v2

by zackscriven

ghl_opportunity_update_status

Idempotent

Updates a GoHighLevel opportunity's status to open, won, lost, abandoned, or all, and optionally records a lost reason.

Instructions

Update Opportunity Status Endpoint: PUT /opportunities/{id}/status (Version header: v3; source: v3/opportunities-v3.json) OAuth scopes: opportunities.write

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_opportunity_update_status"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateStatusDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description usefully adds the required OAuth scope and API version, but says nothing about side effects of a status change — e.g. whether a lost reason becomes mandatory for "lost" or what happens to pipeline stage data.

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?

Three short lines with the verb and resource front-loaded, then endpoint and scope. No filler, though the parenthetical source-file metadata is of marginal value to an agent choosing a tool.

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?

With a nested body object, 100% schema coverage, rich annotations, and no output schema, the definition is technically callable. What is missing is the operational context an agent needs for a mutation: preconditions (does the opportunity need to exist in a pipeline?), the lost-reason coupling, and what a successful response contains.

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 100%, so the schema already documents id, status, and lostReasonId. The description adds no semantics beyond that — notably it does not explain the dependency between status="lost" and lostReasonId, nor the odd "all" enum value.

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 and resource ("Update Opportunity Status") plus the exact endpoint, so the operation is unambiguous. It does not, however, distinguish this narrow status-only mutation from sibling ghl_opportunity_update, which an agent must infer.

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 when-to-use guidance, no comparison to ghl_opportunity_update, and no note about when a status change is appropriate. The only routing hint is the OAuth scope, which is an authorization fact rather than usage 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