Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_webhook_trigger

Create a webhook trigger on a workflow and receive a one-time plaintext token for authentication. The token is shown once and must be handled immediately.

Instructions

Create a webhook trigger on a workflow. Returns the trigger AND its plaintext token — shown ONCE and never retrievable again. Hand the token to your human immediately; do not store it in an entity field.

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>",
      "triggerId": "<triggerId>"
    },
    "name": "create_webhook_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerIdYesThe id of the trigger node in the workflow document.
workflowIdYesThe workflow's id.
expectedInputSchemaNoJSON schema the incoming payload must match. Defaults to {}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It transparently discloses that the plaintext token is returned once and is never retrievable again, emphasizing its ephemeral nature. However, it does not mention potential side effects like whether the trigger is immediately active or if it can be created multiple times for the same workflow/trigger.

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 three sentences, starting with the purpose and then critical security information. Every sentence adds value; no wasted words. It is well-structured and easy to parse.

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 no output schema, the description explains the return value (trigger and token) and addresses token sensitivity. It covers the essential behavioral context for invocation. However, it doesn't mention prerequisites like the workflow must exist or the trigger node ID must be valid, but these are implied by the parameter names.

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%, so baseline is 3. The description does not add parameter-specific details beyond what the schema already provides; it focuses on the return value. This is acceptable since the schema clearly documents the parameters.

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 clearly states the tool's action: 'Create a webhook trigger on a workflow.' It specifies the resource (webhook trigger) and verb (create), distinguishing it from sibling tools like list_webhook_triggers, rotate_webhook_trigger, and delete_webhook_trigger.

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

Usage Guidelines4/5

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

The description provides critical usage guidance: the returned token is shown once and must be handed to the human immediately, with an instruction not to store it in an entity field. This informs the agent how to handle the output responsibly. While it doesn't explicitly state when not to use this tool or alternatives, the security guideline is strong.

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