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

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Contact Labels: List Labels

gapify_list_contact_labels
Read-onlyIdempotent

Retrieve all labels assigned to a contact using account ID and contact identifier to inspect its categorization.

Instructions

List the labels of a contact [Contact Labels] GET /api/v1/accounts/{account_id}/contacts/{contact_identifier}/labels 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>",
      "contact_identifier": "<contact_identifier>"
    },
    "name": "gapify_list_contact_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesThe numeric ID of the account
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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint, openWorldHint), so the bar is lower, and the description goes beyond them by disclosing the exact endpoint, the required auth header ('api-access-token'), and a data-handling note about Persian/Arabic-Indic digits being accepted unchanged. It does not mention pagination or result ordering.

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?

Purpose is front-loaded in the first clause, followed by the route, auth, and locale note. It is compact and mostly earns its space, though restating the raw HTTP path is somewhat redundant for an agent that already has the schema.

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 two-parameter read-only list tool with no output schema and rich annotations, the description covers purpose, auth, endpoint, and a locale caveat that could matter for identifier input. Return-value shape is the only unaddressed item, and no output schema exists to carry it.

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% and both parameters carry their own descriptions, so the schema does the heavy lifting. The description adds nothing about account_id or contact_identifier formats, so the baseline of 3 applies.

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 the labels of a contact'), which is clearly distinct from the many sibling list tools and from the write counterpart gapify_set_contact_labels. It never names that sibling to sharpen the contrast, so it stops short of the top band.

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 implied by the name and the purpose sentence — this is the read-side of contact label management — but the description gives no explicit when-to-use or when-not-to-use guidance and never points to gapify_set_contact_labels or gapify_list_contacts as alternatives.

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