GoHighLevel MCP Server

create_opportunity

Create a sales opportunity in GoHighLevel CRM by providing contact ID, title, deal value, and win probability.

Instructions

Create an opportunity

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": {
      "contact_id": "<contact_id>",
      "title": "<title>",
      "value": "<value>",
      "probability": "<probability>"
    },
    "name": "create_opportunity"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Opportunity title
`value`	Yes	Deal value in dollars
`status`	No	Opportunity status	open
`contact_id`	Yes	Contact ID
`probability`	Yes	Win probability (0-100)
`response_format`	No	Response format	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'Create an opportunity' without mentioning side effects, permission requirements, or error conditions. Essential behavioral context is missing.

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

Conciseness2/5

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

The description is extremely concise (one sentence), but it lacks substantive content. It fails to provide context beyond the tool name. While not verbose, it sacrifices informativeness for brevity.

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

Completeness2/5

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

For a create tool with 6 parameters (4 required) and no output schema or annotations, the description is underspecified. It does not mention return values, success conditions, or validation rules. The agent lacks sufficient context to use the tool correctly.

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 each parameter having a clear description in the schema. However, the tool description adds no additional meaning beyond what the schema already provides. The description does not enhance the agent's understanding of parameter usage.

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 states 'Create an opportunity', which is a clear verb+resource combination. However, it essentially restates the tool name without additional context to differentiate it from sibling tools like update_opportunity or create_contact. The purpose is clear but lacks any specificity.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The agent receives no guidance on context.

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