Skip to main content
Glama
theAIhomegirl

ghl-mcp-server

Search Conversations

conversations_search_conversation
Read-onlyIdempotent

Search conversations with filters for status, contact, assignee, date range, and message type to locate specific CRM records.

Instructions

Search Conversations Returns a list of all conversations matching the search criteria along with the sort and filter options selected. [GET /conversations/search] Scopes: conversations.readonly.

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.
locationIdYesLocation Id
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.
Behavior3/5

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

Annotations already indicate a read-only, non-destructive, idempotent operation. The description adds that it returns a list with sort/filter options and specifies the endpoint and scopes. It doesn't contradict annotations and adds some context, but doesn't disclose pagination or rate limits.

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

Conciseness5/5

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

The description is very concise, with the main purpose front-loaded in the first sentence, followed by endpoint and scopes. No redundant filler.

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 complexity (21 parameters, no output schema), the description is sparse. It doesn't mention pagination, defaults beyond what the schema notes, or any usage examples. Agents need more guidance on constructing searches, such as combining filters or using startAfterDate for pagination.

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 descriptions cover 100% of parameters, so the description doesn't need to add parameter details. It doesn't add anything beyond what the schema provides; it relies entirely on the schema for parameter meaning.

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

Purpose5/5

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

The description clearly states the tool's function: searching conversations and returning a list matching criteria. It distinguishes from single-conversation retrieval by emphasizing 'list of all conversations' and includes the endpoint and scopes.

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. It doesn't mention that for a single conversation by ID you should use get_conversation, or that for messages within a conversation you'd use get_messages. The description only states what it does, not when to choose it.

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

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