gapify-mcp-server

Teams: List Agents in Team

gapify_list_team_agents

Read-onlyIdempotent

Retrieve the list of agents in a specific team via Gapify using account and team IDs. Use it to view team membership and manage agent assignments.

Instructions

List the agents in a team [Teams] GET /api/v1/accounts/{account_id}/teams/{team_id}/team_members 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>",
      "team_id": "<team_id>"
    },
    "name": "gapify_list_team_agents"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	Yes	The ID of the team to be updated
`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.6/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 bar is lower, and the description adds concrete invocation context: the required auth method and header (api-access-token) plus encoding behavior for Persian/Arabic-Indic digits. It still omits return shape and pagination, but the auth disclosure is genuinely useful beyond structured fields.

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 ahead of the endpoint, auth, and encoding notes, and it stays short. The trailing language/digits sentence is generic boilerplate but brief.

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 simple read-only list with full schema coverage and clear annotations, the essentials are present, but with no output schema the description gives no indication of what the response contains or how results are returned.

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 the schema, so the baseline of 3 applies. The description adds no syntax or format detail beyond the schema, and notably does not address the schema's odd 'team to be updated' wording on a read-only list tool.

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 (agents in a team) with the scoping parameter team_id, which separates it from gapify_list_agents. It is clear what the tool does, though it never explicitly names or contrasts the sibling it could be confused with.

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 name and the team_id scope imply the usage (retrieve membership for one team), but there is no explicit when-to-use or when-to-prefer-an-alternative guidance, e.g. versus gapify_list_agents or gapify_list_inbox_agents.

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

Deploy Server