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

ghl-mcp-server-v2

by zackscriven

ghl_opportunity_create

Create a GoHighLevel opportunity with a contact, pipeline, status, stage, value, and optional custom fields by sending required identifiers and opportunity details to the API.

Instructions

Create Opportunity Endpoint: POST /opportunities/ (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": {
      "body": "<body>"
    },
    "name": "ghl_opportunity_create"
  }
}

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
    • changedInput schema / properties / body / properties / customFields / items / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "fieldValue": {
      -        "description": "Value of the custom field",
      -        "example": "9039160788",
      -        "type": "string"
      -      },
      -      "id": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "6dvNaf7VhkQ9snc5vnjJ",
      -        "type": "string"
      -      },
      -      "key": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "my_custom_field",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "properties": {
      -      "fieldValue": {
      -        "description": "Value of the custom field",
      -        "example": [
      -          "test",
      -          "test2"
      -        ],
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "id": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "6dvNaf7VhkQ9snc5vnjJ",
      -        "type": "string"
      -      },
      -      "key": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "my_custom_field",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "id"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "properties": {
      -      "fieldValue": {
      -        "description": "Value of the custom field",
      -        "example": {
      -          "size": 1024,
      -          "url": "https://example.com/file.pdf"
      -        },
      -        "type": "object"
      -      },
      -      "id": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "6dvNaf7VhkQ9snc5vnjJ",
      -        "type": "string"
      -      },
      -      "key": {
      -        "description": "Pass either `id` or `key` of custom field",
      -        "example": "my_custom_field",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "id"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "fieldValue": {
      +        "description": "Value of the custom field",
      +        "example": "9039160788",
      +        "type": "string"
      +      },
      +      "id": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "6dvNaf7VhkQ9snc5vnjJ",
      +        "type": "string"
      +      },
      +      "key": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "my_custom_field",
      +        "type": "string"
      +      }
      +    },
      +    "title": "customFieldsInputStringSchemaV3",
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "fieldValue": {
      +        "description": "Value of the custom field",
      +        "example": [
      +          "test",
      +          "test2"
      +        ],
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "id": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "6dvNaf7VhkQ9snc5vnjJ",
      +        "type": "string"
      +      },
      +      "key": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "my_custom_field",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id"
      +    ],
      +    "title": "customFieldsInputArraySchemaV3",
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "fieldValue": {
      +        "description": "Value of the custom field",
      +        "example": {
      +          "size": 1024,
      +          "url": "https://example.com/file.pdf"
      +        },
      +        "type": "object"
      +      },
      +      "id": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "6dvNaf7VhkQ9snc5vnjJ",
      +        "type": "string"
      +      },
      +      "key": {
      +        "description": "Pass either `id` or `key` of custom field",
      +        "example": "my_custom_field",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id"
      +    ],
      +    "title": "customFieldsInputObjectSchemaV3",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"CreateDtoV3"
  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 disclose the key safety profile: not read-only, not idempotent, non-destructive, and open-world. The description adds useful operational context in the form of the endpoint, API version, and required OAuth scope ('opportunities.write'), but it does not explain duplicate-handling behavior, side effects, or response expectations for this non-idempotent create.

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?

The description is short and front-loads the action and endpoint. The source-file metadata ('source: v3/opportunities-v3.json') is of limited value to an agent choosing or invoking the tool, but the overall text is efficient.

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?

The schema fully covers the complex nested request body and annotations cover safety and idempotency, but there is no output schema and the description says nothing about what is returned after creation. Endpoint and auth scope are helpful additions, yet the definition remains only minimally complete for a create operation.

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?

The input schema has 100% description coverage, including detailed nested body fields and examples, so the description does not need to restate parameters. It adds no additional parameter semantics beyond what the schema already provides, which is the expected baseline when schema coverage is complete.

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 states a clear verb and resource ('Create Opportunity') and adds the concrete endpoint POST /opportunities/. It does not differentiate against close siblings such as ghl_opportunity_upsert or ghl_opportunity_update, so it is clear but not fully sibling-aware.

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 rather than ghl_opportunity_upsert, ghl_opportunity_update, or other creation paths. The required OAuth scope is noted, but usage conditions and alternatives are left entirely implicit.

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