gapify-mcp-server

Automation Rule: List all automation rules in an account

gapify_list_automation_rules

Read-onlyIdempotent

List automation rules in a Gapify account to inspect existing support workflows before creating, updating, or troubleshooting them.

Instructions

List automation rules in the account [Automation Rule] GET /api/v1/accounts/{account_id}/automation_rules 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_automation_rules"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Query param. The page parameter Example: 1
`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.7/5.0

Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive safety profile, so the bar is lower. The description usefully adds the auth mechanism ('User API key' header api-access-token) and an encoding caveat about Persian/Arabic-Indic digits, which are real behavioral details beyond the annotations. Pagination behavior is not addressed.

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, followed by endpoint, auth and encoding notes, with little waste. The bracketed '[Automation Rule]' tag and raw endpoint path are slightly redundant but not disruptive.

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 read-only list tool whose annotations carry the safety profile and which has no output schema and full parameter documentation, the description covers purpose, endpoint, auth and encoding adequately. Only pagination nuances are left implicit.

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% for both parameters (account_id and page), so the schema already documents them. The description adds no extra parameter meaning, which is the expected baseline 3 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 automation rules in the account'), which distinguishes it from the singular get/add/update/remove siblings. However, it does not explicitly name or contrast those siblings, so the differentiation is by inference rather than statement.

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 'List ... in the account' phrasing, but there is no explicit when-to-use guidance, no mention of when to prefer this over get_automation_rule, and no exclusions or prerequisites stated.

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

Deploy Server