Clarifo

activate_automation

Idempotent

Switch on a Clarifo automation that is off, so it starts running on its schedule. Use only after showing the user what it does, its schedule, timezone and next run, and the user explicitly agreeing. It then runs and uses the account's Automate allowance until paused.

Args: automation_id: From create_automation_draft or automations. activation_token: The activation_token returned with those settings. If the settings changed since, the call is refused and the current settings are returned. idempotency_key: Optional; leave it out. Clarifo recognises a repeated identical request by its content. Give one only to retry this same request. workspace_id: Optional; the automation's workspace.

Returns: {"status": "automation_activated", "automation_id", "next_run", "schedule", "timezone", "review_url"} or {"error", "failure_kind"}.

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": {
      "automation_id": "<automation_id>",
      "activation_token": "<activation_token>"
    },
    "name": "activate_automation"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	No
`automation_id`	Yes
`idempotency_key`	No
`activation_token`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: the call consumes the account's Automate allowance until paused, and a stale activation_token causes the call to be refused with current settings returned. It also names the return payload keys and the error shape. Annotations already cover idempotency and non-destructiveness, so this is solidly above baseline.

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?

Front-loaded with the action and the confirmation gate, and the Args/Returns blocks are easy to scan. A few phrasings are wordier than needed, notably the multi-line idempotency_key explanation, but nothing is filler.

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?

Covers the mutation's side effects, the confirmation gate, token staleness, quota impact, and the response keys, so an agent can call it without guessing. With an output schema also present, the remaining gaps, such as error failure_kind values, are minor.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden, and it does: automation_id source, activation_token semantics including the refused-when-settings-changed behavior, idempotency_key ('leave it out', content-based dedup, retry-only), and workspace_id. Every parameter gets meaning the schema lacks.

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?

States a specific verb and resource ('Switch on a Clarifo automation that is off') plus the concrete effect ('starts running on its schedule'). This clearly separates it from creation (create_automation_draft) and modification (update_automation) siblings.

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?

Gives an explicit precondition: show the user what the automation does, its schedule, timezone, next run, and get explicit agreement before calling. It also scopes the tool to automations that are 'off'. It does not name a sibling alternative or state what to do when the user declines, so it stops short of full routing guidance.

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

All Clarifo 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.