Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_opportunity_search

Read-onlyIdempotent

Search opportunities with filters by status, pipeline, stage, contact, assigned user, and more. Supports pagination to navigate large result sets.

Instructions

Full pagination/filter surface confirmed present: q, status, campaignId, id, order, endDate, startAfter, startAfterId, date, country, page, limit, getTasks, getNotes, getCalendarEvents, locationId (required), pipelineId, pipelineStageId, contactId, assignedTo. To page past the first result set, either increment page with limit, or read startAfter/startAfterId off the previous response's meta and pass them back in — required to reach results beyond the first ~100 records on large pipelines. Search Opportunity Endpoint: GET /opportunities/search (Version header: v3; source: v3/opportunities-v3.json) OAuth scopes: opportunities.readonly Pagination params: startAfter, startAfterId, page, limit — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query (max 75 characters)
idNoOpportunity Id
dateNoStart date
pageNoPage number for pagination
limitNoLimit Per Page records count. will allow maximum up to 100 and default will be 20
orderNoSort order for results (e.g. added_asc, added_desc, name_asc, name_desc)
statusNoFilter by opportunity status
countryNoFilter by country code (ISO 3166-1 alpha-2)
endDateNoEnd date
getNotesNoget Notes in contact
getTasksNoget Tasks in contact
contactIdNoContact Id
assignedToNoFilter by assigned user identifier
campaignIdNoCampaign Id
locationIdYesLocation Id
pipelineIdNoPipeline Id
startAfterNoStart After
startAfterIdNoStart After Id
pipelineStageIdNoStage Id
getCalendarEventsNoget Calender event in contact
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds the need for pagination to overcome the ~100 record limit, which is valuable behavioral context beyond annotations.

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?

The description is a single paragraph with some redundancy (pagination mentioned twice). It could be more structured and concise.

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?

Given the complex pagination and 20 parameters, the description lacks explanation of the return value structure. However, annotations compensate somewhat, making it moderately complete.

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% with parameter descriptions. The description only enumerates the parameters without adding new semantic information beyond what the schema already provides.

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 clearly states it is a search tool for opportunities, listing all filter parameters and pagination details. However, it does not differentiate from the sibling tool ghl_opportunity_search_advanced.

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?

The description provides pagination instructions but lacks guidance on when to use this tool versus other opportunity search/retrieval tools. No explicit context for selection among siblings.

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/zackscriven/ghl-mcp-server'

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