Wayfront

Automation Write Tool

automation-write

Destructive

Create, update, toggle or delete pipeline automation rules. Every action requires pipeline_id. Read automation-read first for supported triggers, conditions and actions. Active rules can trigger downstream writes, webhooks or Slack messages. Status-sync-managed rules cannot be edited.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Rule name. Required for "create"/"update".
`action`	Yes	Action to perform.
`actions`	No	Action list ({type, params}). Valid types + their params come from the "list" catalog. At least one action is required for "create"/"update".
`conditions`	No	Condition list ({field, operator, value}); all must pass (AND). Use fields/operators from the "list" catalog for the chosen trigger. Pass an empty array for no conditions.
`pipeline_id`	Yes	The pipeline the automation belongs to. Required for every action.
`automation_id`	No	Automation ID. Required for "update", "toggle", and "delete". Use "list" to discover IDs.
`trigger_event`	No	The trigger event slug (e.g. "order.status.changed"). Must be valid for the pipeline type — see the "list" catalog. Required for "create"/"update".
`description_cache`	No	Optional human-readable summary of the rule (use real names, not IDs).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description discloses important side effects (downstream writes, webhooks, Slack messages) and a restriction (status-sync-managed rules cannot be edited), going beyond the annotations' destructiveHint. This gives the agent a clear picture of consequences.

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 concise and well-structured, using a few short sentences. It states the core function, key requirements, and important caveats without unnecessary elaboration.

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 write tool with no output schema, the description covers the essential context: it lists supported actions, mentions the need to read the catalog, and highlights side effects and edit restrictions. It does not describe return values, but that is a minor gap for this tool type.

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% and the description does not add much beyond it. It reiterates that pipeline_id is required and references the 'list' catalog, but these details already exist in the parameter descriptions. The baseline for high coverage is 3, and no significant extra meaning is added.

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 tool's function with a specific verb ('Create, update, toggle or delete') and a clear resource ('pipeline automation rules'). This distinguishes it from the sibling automation-read tool.

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 advises reading automation-read first for supported triggers/conditions/actions, giving a clear usage order. While it doesn't explicitly say 'use this when you need to modify automations', the intent is obvious and the guidance is helpful.

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

All Wayfront tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?