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

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Integrations: List all the Integrations

gapify_list_integrations
Read-onlyIdempotent

Retrieve all integrations connected to a given account by its ID, so assistants can review available apps before taking action.

Instructions

List the integrations available for the account [Integrations] GET /api/v1/accounts/{account_id}/integrations/apps 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>"
    },
    "name": "gapify_list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesThe numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description earns credit by adding genuinely non-structured context: the required auth mechanism (User API key in an api-access-token header) and the note that text values and digits may arrive in Persian/Arabic-Indic form unchanged. It still omits pagination or result-size behavior, which keeps it from a 5.

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

Conciseness3/5

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

The purpose is front-loaded, which is good, but the block is padded with a raw endpoint path and a generic Persian/Arabic digit boilerplate that is largely irrelevant to a parameterless list call. The sentences are short but not every one earns its place for this specific tool.

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?

For a read-only list tool with a complete one-parameter schema and full annotation coverage, the auth detail is the main missing piece and it is supplied. But with no output schema, the description never indicates what an integration record contains or whether results are paginated, leaving the agent under-informed about the response.

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?

There is a single parameter and schema description coverage is 100%, so the schema already documents account_id as 'The numeric ID of the account'. The description adds nothing further about the parameter, which is the expected baseline when the schema does the heavy lifting.

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 integrations available for the account') plus the underlying endpoint, so the agent knows exactly what is returned. However, it does not distinguish itself from the similarly named siblings gapify_create_integration_hook / gapify_update_integration_hook / gapify_delete_integration_hook, which are a different concept an agent could easily confuse with this one.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites beyond the auth header, and no routing to alternatives (e.g. the integration-hook tools or gapify_raw_request). The agent must infer that a read-only listing is the right call purely from the tool 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