Use the Speak AI MCP server tool test_automation to run one automation once
against one media item to see which way it branches.
What does it do?
Run one automation once against one media item to see which way it branches. This is
a real run, not a dry run, and it works on inactive automations too. Only the run’s
own status notifications are suppressed and translation steps are skipped. Notify
steps still send their email or Slack message, outbound webhooks still fire,
Composio actions still run against the connected third-party account, and AI steps
use credits. Confirm with the user before testing an automation that sends anything
outside Speak. It needs a mediaId and sends no webhook payload, so on an
inbound-webhook automation the payload tokens resolve to empty. Returns a runId;
read the result with get_automation_run.
Parameters
test_automation takes 2 parameters, all of them required.
| Name | Type | Required | Description |
|---|---|---|---|
automationId |
string | Yes | Unique identifier of the automation to test |
mediaId |
string | Yes | Media item to run the automation against |
Behaviour
The Speak AI MCP server publishes these behaviour hints for test_automation.
- Can change data in your workspace.
- Can delete or overwrite data. Use with care.
- Repeating an identical call can have an extra effect.
- Can reach systems outside Speak AI.
Related
- Automations lists the rest of the Automations category.
- Tool reference lists every Speak AI MCP server tool.
- MCP server covers setup, supported clients, and what agents can do once connected.