Tools

Bot Studio

Read your automations and their versions, and draft a new version for someone to review.

A project's automations are made of three parts: a flow, its numbered versions, and a pointer that says which version is live for each instance. These tools read all three and can create a new version. None of them can move a pointer, so none of them can change what customers see.

Tool	Reads	Writes
`list_flows`	Flows	Nothing
`list_flow_versions`	Versions and live pointers	Nothing
`create_flow_version`	Nothing	A new draft version

There is no tool to edit an existing version or to publish one. Publishing is done by a person, in Bot Studio.

list_flows

The Bot Studio flows configured for a project: which automations exist and what type each one is.

Use it to answer "what does the bot do here" before looking at versions.

project_slugstringrequired

The project to read.

limitintegerdefault: 25

Rows to return, from 1 to 100.

list_flow_versions

Every version of a project's flows, and which version each instance currently points at. The version a pointer names is the one serving customers.

project_slugstringrequired

The project to read.

limitintegerdefault: 25

Rows to return, from 1 to 100.

Flow definitions can be large. If a result is withheld as RESULT_TOO_LARGE, ask for fewer rows with limit.

create_flow_version

Drafts a new flow version for an instance. The version is saved but not activated: no pointer moves, so live traffic is unaffected until a person publishes it in Bot Studio.

The version is recorded under the connected account and marked as drafted through MCP, so whoever reviews it can see an assistant wrote it. The draft is also written to the audit log.

project_slugstringrequired

The project the version belongs to.

typestringrequired

Which configuration the version is for: system_configuration, error_handler, web_hook_configuration, text_replacers, external_systems_configuration or vector_config. Call list_flow_versions to see which types the project uses.

instance_idintegerrequired

The instance the version belongs to.

versionintegerrequired

The new version number. Read the current highest from list_flow_versions and add one.

flowobjectrequired

The flow definition.

A successful call returns the saved version and a reminder of what happens next:

Example result

{
  "data": { "…": "…" },
  "_meta": {},
  "next_step": "Draft saved. It is not live. A person has to publish it in Bot Studio, which is the only place the pointer can be moved."
}

Drafts are visible to everyone in the project who can open Bot Studio. Ask your assistant to show you the flow it intends to save before it calls create_flow_version.

Ask it things like

"What does the live greeting configuration in acme-store say to new customers?"
"Draft a new version of our error handler that offers a human agent after two failed replies. Show me the flow before saving it."