Skip to main content
Glama

Run Automation Tool

run-automation-tool
Destructive

Start one of the user's automations now, the same as "Run now" in the web app. The AI agent then drives the automation's phones on its own; this returns the run at once with status "queued". Poll get-automation-run-tool with its id until status is done, failed or stopped, then read outcome, result and phone_reports. A run can be refused (the automation is off, a run is already going, the daily limit is reached, no phone is online, or the agent is unavailable); the error says which.

A tiktok_warmup automation (see list-automations-tool) has no daily limit and starts one session per phone at once, so this returns the first one already "running" alongside sessions, the number started, and skipped_busy_slots, the phones left alone because another run already drives them; payload is ignored, it has no parameters.

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>"
    },
    "name": "run-automation-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotsNoRun on only these of the automation's phones, given as `slot` UUIDs from list-phones-tool. Omit to run on all of them.
payloadNoValues for the automation's `payload_parameters`, keyed by name, the same fields its webhook would receive. Omit when it has none.
automation_idYesThe automation `id` from list-automations-tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, so the safety profile is already known; the description adds the crucial async contract (returns immediately with status 'queued') and the exact terminal states to poll for. It also discloses refusal behavior and the warmup-specific return shape (`sessions`, `skipped_busy_slots`, `payload` ignored). The only gap is that it doesn't state side effects on the phones beyond 'drives the automation's phones', though that is implied.

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 web-app analogue, then the polling contract, then the special case. Dense with no filler, though the three-paragraph structure is longer than strictly necessary and the refusal list could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the return fields the agent will need (`id`, `status`, `outcome`, `result`, `phone_reports`, plus the warmup-specific `sessions` and `skipped_busy_slots`). For an async, side-effecting launcher this covers everything needed to call it and follow up correctly.

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 the baseline is 3, but the description adds real meaning: `payload` mirrors what the automation's webhook would receive and is ignored entirely for `tiktok_warmup` automations, which the schema does not say. `slots` semantics are already fully covered by the schema.

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 ('Start one of the user's automations now') and anchors it to a familiar UI action ('Run now' in the web app), which pins down semantics immediately. It also distinguishes itself from get-automation-run-tool (polling) and list-automations-tool (discovery), so an agent can route correctly.

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

Usage Guidelines5/5

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

Explicitly says what to do after calling: poll get-automation-run-tool with the `id` until `status` is done, failed or stopped, then read `outcome`, `result` and `phone_reports`. It also enumerates the refusal conditions (automation off, run already going, daily limit, no phone online, agent unavailable) and carves out a special workflow for `tiktok_warmup` automations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources