Skip to main content
Glama
Sign In
gapify-mcp-server

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Conversations: Conversation Details

gapify_get_conversation
Read-onlyIdempotent

Retrieve a conversation’s details by display ID from Gapify’s Chatwoot-compatible support API to inspect messages, status, and metadata.

Instructions

Get a conversation's details by its display ID [Conversations] GET /api/v1/accounts/{account_id}/conversations/{conversation_id} Auth: User API key (header api-access-token). Text values may be written in Persian (Farsi) or any other language and are sent unchanged; IDs, numbers and phone numbers may use Persian or Arabic-Indic digits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>",
      "conversation_id": "<conversation_id>"
    },
    "name": "gapify_get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesThe numeric ID of the account
conversation_idYesThe numeric ID of the conversation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the required auth mechanism ('User API key, header api-access-token') and the locale caveat about Persian/Arabic-Indic digits, which affects how IDs may be supplied.

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

Conciseness4/5

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

Front-loads the purpose, then appends endpoint, auth, and encoding notes. Efficient, though the bracketed tag and raw GET path duplicate structured context.

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

Completeness4/5

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

For a simple two-required-param read tool with no output schema, the description covers what an agent needs to call it: purpose, endpoint, auth, and input encoding quirks. Return shape is unspecified, but no output schema exists to lean on.

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 description coverage is 100%, so both required parameters are documented in the schema; baseline is 3. The description adds only tangential meaning (digits may be Persian/Arabic-Indic) and no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('Get a conversation's details') that clearly distinguishes it from list_conversations, filter_conversations, and get_messages. Minor ambiguity: it says 'by its display ID' while the schema param is 'conversation_id' described as the numeric ID, so the identifier semantics are slightly loose.

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 read-only retrieval intent is implied but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives (e.g., use list_conversations to find the ID first). Usage must be inferred from the name.

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

Deploy Server

Other Tools