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

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Conversations API: List all conversations

gapify_client_list_conversations
Read-onlyIdempotent

List every conversation for a given contact using inbox and contact identifiers, so assistants can review support history or find a thread before replying.

Instructions

List all conversations for the contact [Conversations API] GET /public/api/v1/inboxes/{inbox_identifier}/contacts/{contact_identifier}/conversations 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": {
      "inbox_identifier": "<inbox_identifier>",
      "contact_identifier": "<contact_identifier>"
    },
    "name": "gapify_client_list_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_identifierYesThe identifier obtained from API inbox channel
contact_identifierYesThe source id of contact obtained on contact create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the required auth scheme ('User API key' in an `api-access-token` header) and the caveat that Persian/Arabic-Indic digits and multilingual text pass through unchanged, which matters for matching identifiers and output.

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 in one sentence, then gives endpoint, auth, and an encoding caveat compactly. The digit/language sentence is somewhat boilerplate for a list call but is short and does not bloat the definition.

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?

Covers scope and auth adequately for a read-only list call, but with no output schema it says nothing about the return shape, pagination, or whether empty results are possible. An agent knows how to call it but not what to expect back.

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% and both parameters are documented in-schema, so the baseline is 3. The description adds nothing about format beyond the URL template, and the multi-language digit note is at best tangential to how the identifiers should be supplied.

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 and resource ('List all conversations for the contact') and pins the scope via the GET path with inbox and contact identifiers. This distinguishes it from the broader gapify_list_conversations, though it does not explicitly contrast with the near-identical sibling gapify_list_contact_conversations.

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?

Usage is only implied by the scoping path: you need an inbox and contact identifier, so it is for per-contact conversation retrieval. It never names when to prefer this over gapify_list_contact_conversations or gapify_filter_conversations, nor any prerequisites beyond auth.

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