Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_webhook_triggers

Retrieve all webhook triggers for a workflow without exposing secret tokens, which are shown only once upon creation or rotation.

Instructions

List a workflow's webhook triggers. Secrets are never returned — a trigger's token is shown only once, when it is created or rotated.

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": {
      "workflowId": "<workflowId>"
    },
    "name": "list_webhook_triggers"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowIdYesThe workflow's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description correctly discloses a critical behavioral trait: secrets are never returned and tokens are shown only upon creation or rotation. This goes beyond the basic purpose and helps the agent understand security implications.

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

Conciseness5/5

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

The description is two sentences long, front-loaded with the primary action, and each sentence adds distinct value: the first states the purpose, the second adds a crucial behavioral note. No extraneous text.

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?

Given the tool's simplicity (one required parameter, no output schema, no annotations), the description adequately covers the key aspects: what it does and a notable behavior (secrets not returned). It could mention the output shape or pagination, but it is sufficient for a list tool with this context.

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?

The schema coverage is 100% and the only parameter (workflowId) is described in the schema. The description adds no additional semantic value beyond framing it as 'a workflow's webhook triggers,' so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the verb 'List' and the resource 'webhook triggers' scoped to a workflow, which clearly distinguishes it from sibling tools like list_conditional_triggers or list_cron_schedules.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The purpose is clear from the name, but the lack of comparison with siblings like list_conditional_triggers leaves the agent to infer usage context.

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