Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

conversations_search_conversation

Read-onlyIdempotent

Find and filter GoHighLevel conversations using criteria like contact, status, assignee, date range, and message type.

Instructions

Search Conversations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoId of the conversation
sortNoSort paramater - asc or desc
limitNoLimit of conversations - Default is 20
queryNoSearch paramater as a string
sortByNoThe sorting of the conversation to be filtered as - manual messages or all messages
statusNoThe status of the conversation to be filtered - all, read, unread, starred
endDateNoEnd date filter for dateAdded field (Unix timestamp in milliseconds)
mentionsNoUser Id of the mention. Multiple values are comma separated.
contactIdNoContact Id
followersNoUser IDs of followers to filter conversations by. Multiple IDs can be provided as comma-separated values.
startDateNoStart date filter for dateAdded field (Unix timestamp in milliseconds)
assignedToNoUser IDs that conversations are assigned to. Multiple IDs can be provided as comma-separated values. Use "unassigned" to fetch conversations not assigned to any user.
locationIdNoLocation Id Defaults to GHL_LOCATION_ID when omitted.
scoreProfileNoId of score profile on which conversations should get filtered out, works with scoreProfileMin & scoreProfileMax
startAfterDateNoSearch to begin after the specified date - should contain the sort value of the last document
lastMessageTypeNoType of the last message in the conversation as a string
scoreProfileMaxNoMaximum value for score
scoreProfileMinNoMinimum value for score
sortScoreProfileNoId of score profile on which sortBy.ScoreProfile should sort on
lastMessageActionNoAction of the last outbound message in the conversation as string.
lastMessageDirectionNoDirection of the last message in the conversation as string.
Behavior1/5

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

The description adds no behavioral information beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). It does not disclose that it returns matching conversations, supports pagination, or any other operational characteristics, leaving agents with no clue about the tool's 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 extremely concise but under-specified. For a tool with 21 parameters, a single phrase is not appropriately structured or informative; it fails to guide the agent on how to interpret or use the tool.

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

Completeness1/5

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

Given the tool's complexity (21 parameters) and lack of an output schema, the description provides no useful context about what the tool does, what it returns, or how to use it effectively. An agent would be completely lost.

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 already provides descriptions for all 21 parameters (100% coverage), so the description adds no additional meaning. The high schema coverage sets a baseline of 3, and the description does not supplement it with greater context.

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

Purpose1/5

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

The description 'Search Conversations' is a tautology of the tool name, providing no specific verb-resource detail, no indication of what is searched or returned, and no differentiation from sibling search tools like conversations_get_conversation or contacts_search_contacts_advanced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 tool versus alternatives. It does not mention that it is a search/list operation, suggest typical filter combinations, or reference more specific tools like conversations_get_conversation for single-conversation retrieval.

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

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