AutomateSocials

Change a workflow

update_workflow

Changes a workflow that already exists: its steps, its name, or when it runs. Pass only what changes. Call get_workflow first when you are changing the steps, since the list you pass replaces the ones that are there. Its run history is kept.

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_workflow"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The workflow, by id or by its name.
`name`	No
`runAt`	No	For a one-off: an ISO time.
`steps`	No	The complete new list of steps, in order.
`context`	No
`timeOfDay`	No	HH:MM in the project timezone.
`daysOfWeek`	No	0 is Sunday.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only mark this as a non-read-only, non-destructive, non-idempotent, open-world mutation. The description goes further by disclosing what is overwritten (the existing step list) and what survives (run history), which is exactly the context an agent needs to avoid data loss. Nothing here contradicts the annotations.

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?

Four short sentences, zero padding, with the replacement hazard and the get_workflow prerequisite front-loaded. Every sentence carries a distinct operational fact.

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 7-parameter mutation with a nested step schema and no output schema, the description covers the highest-risk behaviors (replacement of steps, partial update, prerequisite read). It could have noted that some step kinds consume credits, though the schema already flags the costly fields.

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?

At 71% schema coverage the schema documents most fields, but the description adds two things the schema cannot say: that omitted fields are left alone, and that the steps array is a full replacement rather than a merge. That replaces-whole-list warning is the critical semantic an agent would otherwise get wrong.

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?

States a specific verb and resource plus the three dimensions it can change (steps, name, schedule), which tells an agent exactly what the tool touches. 'A workflow that already exists' implicitly separates it from create_workflow, but the sibling is never named.

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?

'Pass only what changes' establishes patch semantics, and 'Call get_workflow first when you are changing the steps' gives an explicit prerequisite tied to a specific condition. It stops short of naming create_workflow or delete_workflow as alternatives for other intents.

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

All AutomateSocials 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?