Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_conversation_export_messages_by_location

Read-onlyIdempotent

Export messages from a specific location with cursor-based pagination. Filter by channel, date range, conversation, or contact to retrieve targeted message history.

Instructions

Export messages by location ID Export messages for a specific location with cursor-based pagination support. Response includes messageType (string), source, and subType fields. The channel parameter is optional - if not provided, all non-email message types will be returned including activity messages (opportunity updates, appointments, etc.). Endpoint: GET /conversations/messages/export (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.readonly Pagination params: limit, cursor — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of messages to return per page
cursorNoCursor for pagination. Pass the nextCursor from previous response to get next page.
sortByNoField to sort bycreatedAt
channelNoFilter by message channel. Optional - when not provided, all non-email message types will be returned including activity messages (opportunity updates, appointments, etc.). To fetch email messages, you must explicitly set channel=Email.
endDateNoEnd date to filter messages by
contactIdNoFilter messages by contact ID
sortOrderNoSort orderdesc
startDateNoStart date to filter messages by
locationIdYesLocation ID to filter messages by
conversationIdNoFilter messages by conversation ID
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: cursor-based pagination, default channel behavior (all non-email types including activity messages), OAuth scopes, and endpoint details. This goes well beyond annotations without contradiction.

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 concise and well-structured. It front-loads the main purpose, followed by pagination details, channel behavior, and then technical metadata (endpoint, OAuth scopes). Every sentence serves a purpose without redundancy.

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 10 parameters and no output schema, the description covers the core functionality and pagination but only partially describes the response structure (lists only three fields: messageType, source, subType). It does not mention pagination response fields or the full set of return values. The agent may need to infer additional response structure from the pagination mention.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining the channel parameter's default behavior (returns all non-email types including activity messages unless channel=Email is set) and that limit/cursor are for pagination. This provides context that the schema alone does not.

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 purpose: export messages by location ID. It specifies the verb (export), resource (messages by location), and provides additional scope details such as cursor-based pagination, response fields, and channel behavior. This distinguishes it from other conversation tools like ghl_conversation_get_messages.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context for when to use the tool (e.g., for exporting messages with pagination, channel behavior). However, it does not explicitly state when not to use it or provide direct comparisons to sibling tools such as ghl_conversation_get_messages. Implicit guidance is present but not explicit.

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