gapify-mcp-server

Contacts: Get Contactable Inboxes

gapify_get_contactable_inboxes

Read-onlyIdempotent

Retrieve the inboxes through which a contact can be reached; provide the account ID and contact ID to get the available channels.

Instructions

List the inboxes through which a contact can be reached [Contacts] GET /api/v1/accounts/{account_id}/contacts/{id}/contactable_inboxes 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>",
      "id": "<id>"
    },
    "name": "gapify_get_contactable_inboxes"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	ID of the contact
`account_id`	Yes	The numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description usefully adds the required auth mechanism (User API key in the api-access-token header) and notes Persian/Arabic-Indic digit handling for inputs, going beyond the structured safety metadata.

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?

The purpose is front-loaded in one clear sentence, followed by compact endpoint and auth lines. The final localization sentence is somewhat generic and not specific to this endpoint, but it is short and relevant to input formatting.

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-parameter read-only list tool, the description covers purpose, endpoint, auth, and input encoding. It does not describe the shape of the returned inbox list, which is a minor gap given no output schema exists, but the core information an agent needs to call it correctly is present.

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 the schema already documents account_id and id, making 3 the baseline. The description adds meaningful input-format context by noting that IDs and numbers may use Persian or Arabic-Indic digits, which directly affects how those parameters 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 (List) and resource (inboxes through which a contact can be reached), and includes the exact HTTP endpoint. It implies a contact-scoped filter, which separates it from gapify_list_inboxes, but it never explicitly names or contrasts with any sibling tool.

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 lets an agent infer that this is used when the reachable inboxes for a specific contact are needed, but it gives no explicit when-to-use guidance, prerequisites, or alternatives such as gapify_list_inboxes or gapify_create_contact_inbox.

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

Deploy Server