Skip to main content
Glama

create_opportunity

Add a new sales opportunity to a GoHighLevel pipeline by providing the contact, deal name, pipeline stage, and optional details like value and status.

Instructions

Create a new GoHighLevel opportunity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactIdYesThe contact ID this opportunity belongs to.
pipelineIdYesThe pipeline ID where the opportunity should be created.
pipelineStageIdYesThe stage ID where the opportunity should be placed.
nameYesThe opportunity or deal name.
monetaryValueNoThe monetary value of the opportunity.
statusNoInitial status such as open, won, lost, or abandoned.
assignedToNoUser ID to assign the opportunity to.
sourceNoLead source or deal source.
Behavior1/5

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

No annotations provided, and the description does not disclose any behavioral traits such as required permissions, side effects, or idempotency. The description is too minimal to inform the agent about behavior.

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 a single sentence but lacks necessary detail for an 8-parameter tool. It is under-specified, sacrificing 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?

No output schema exists, and the description does not explain return values or error states. Missing context about prerequisites such as contact existence or pipeline validity.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond what is in the schema, meeting the baseline.

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?

Description clearly states it creates an opportunity, but does not differentiate from siblings like update_opportunity or search_opportunities. The verb and resource are present, but no distinguishing details.

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 guidance on when to use this tool versus alternatives. Siblings like update_opportunity and search_opportunities exist, but no exclusions or context are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Snack-JPG/ghl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server