Mentio

Update automation

update_automation

DestructiveIdempotent

Rename, pause (enabled: false) or change an automation. filter and actions each replace the whole of themselves; the change applies to mentions scored from then on.

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": {
      "id": "<id>"
    },
    "name": "update_automation"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Automation id (atm_...)
`name`	No	Automation name, unique in the workspace.
`filter`	No	Replaces the whole filter.
`actions`	No	Replaces every action.
`enabled`	No	false stops it; true runs it again on new mentions.
`idempotencyKey`	No	Optional. A unique value (a UUID) for this call: 1 to 255 visible ASCII characters, no spaces. Calling again with the same key and the same input within 24 hours returns the first result instead of doing it twice.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, but the description earns credit by explaining exactly what destruction means: filter and actions replace the whole of themselves rather than merging. It also discloses the retroactive scope — changes apply only to mentions scored from then on — which annotations cannot express.

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?

Two short sentences with zero filler; the replace semantics and the retroactive rule are front-loaded where an agent will see them before constructing the call.

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 destructive, nested-object mutation with no output schema, the description covers purpose, mutation semantics, and forward-only effect on scoring. It does not mention permissions, whether re-scoring affects existing mentions, or error behavior, but those are secondary against a fully documented schema and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds real meaning by framing filter and actions as full replacements, which matters for an agent deciding whether to fetch the current filter before writing. The 'enabled: false means pause' gloss is partially duplicated by the schema's own enabled description, slightly reducing the added value.

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?

Specific verbs (rename, pause, change) applied to a clear resource (an automation), plus the mechanism for pausing (enabled: false). It doesn't explicitly distinguish itself from siblings like delete_automation or duplicate_keyword, but the resource name makes scope plain.

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 parenthetical 'pause (enabled: false)' implicitly tells the agent how to pause rather than delete, which is useful routing. However, there is no explicit when-to-use/when-not, no mention of prerequisites, and no pointer to create_automation or delete_automation for the adjacent intents.

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

All Mentio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?