Journey group tools

A journey group bundles related journeys under one name so they can be audited together. Six tools.

list_journey_groups

List journey groups for a project, each with its member journeys and journey count.

Name	Type	Required
project_id	string	yes

Returns: the project’s groups, each with its members. Not paginated.

create_journey_group

Create a journey group for a project. The group is created empty; add journeys with set_journey_group_members.

Name	Type	Required
organization_id	string	yes
project_id	string	yes
name	string	yes
description	string	no

Returns: the created group.

update_journey_group

Update a journey group’s name or description.

Name	Type	Required
organization_id	string	yes
journey_group_id	string	yes
name	string	no
description	string	no

Does not change membership.

Returns: the updated group.

delete_journey_group

Delete a journey group. The member journeys themselves are not deleted, only the grouping.

Name	Type	Required
organization_id	string	yes
journey_group_id	string	yes

Returns: the confirmation line Deleted journey group: <id>.

set_journey_group_members

Set the full member list of a journey group.

Name	Type	Required	Notes
organization_id	string	yes
journey_group_id	string	yes
journey_ids	string[]	yes	The complete desired set of members.

REPLACE semantics. The list you send becomes the membership; it is not a delta. Sending one id leaves the group holding exactly one journey.

Returns: the group with its updated journey count and members.

run_journey_group

Start an audit for every journey in a group — one run per member journey.

Name	Type	Required
organization_id	string	yes
project_id	string	yes
journey_group_id	string	yes

One journey failing to start does not abort the rest.

Returns: a summary line sorting the member journeys into three groups:

Group	Meaning
Started N audits (run ids: …)	New runs, one per journey.
N already had a run in flight: <name> (<run id>)	An audit of that journey was already running; nothing new started, and the id is the run already going.
Skipped N (over quota or refused): <name>	Did not start and is not running.

Only the groups that apply are printed. An empty group returns Group has no journeys to run; an unknown group id returns an error block.

Unlike start_agentic_audit, this returns run ids directly, not cloud run request ids. Run ids are what get_agentic_audit_report and cancel_audit take. get_audit_progress takes a cloud run request id, so it cannot poll a run started this way.