GoHighLevel MCP Server

list_opportunities

Retrieve paginated sales opportunities from your CRM. Use limit and offset to control results.

Instructions

List opportunities

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_opportunities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of results
`offset`	No	Pagination offset
`response_format`	No	Response format	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 14, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only, paginated, or authentication requirements. It only repeats the name, leaving the agent uninformed about side effects or limitations.

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

Conciseness3/5

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

Three words is concise but lacks substance. It is not overly verbose, yet the brevity comes at the cost of usefulness.

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?

Given the tool's three parameters and no output schema, the description is critically incomplete. It does not explain what is returned, how pagination works, or how response_format affects output. The agent cannot determine if this tool is appropriate for the task.

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% (all parameters have descriptions). The description does not add new parameter information but also does not contradict the schema. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List opportunities' essentially restates the tool name without clarifying what 'opportunities' are in this context (e.g., CRM deals, sales leads). It fails to differentiate from siblings like get_opportunity (which retrieves a single record).

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 such as get_opportunity for a specific record or search_contacts for different resources. The description provides no context about filtering or pagination.

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