Orchetta

Attach an existing resource to a step on a journey map.

attach_resource_to_step

Create an atlas: named stages that journeys are then plotted across. Check list_atlases first rather than duplicating one; place_journey_on_atlas fills it.

create_atlas

Create a journey with its stages and steps in one call. Prefer this over adding stages one at a time. For a conversational experience (a chatbot, a voice assistant, a support script) pass layout "conversation": stages are then the phases of the exchange and each step is one turn, with a speaker.

create_journey_map

Save a view of a journey: a named way of reading the map that everyone in the workspace can pick, and that share links read through. A view changes what the map shows, never what's on it. Call list_journey_views first for the lane keys and for views that already exist.

create_journey_view

Create a list: a named, curated collection of existing resources — a shortlist of opportunities, the profiles to interview. Check list_lists first rather than duplicating one, then add_records_to_list fills it.

create_list

Create one profile: a persona this organization's experience serves. Call list_profiles first — a name already taken is refused rather than duplicated. A profile is a persona — one sort of person the experience serves, which the team then tags onto the journeys, steps, needs and opportunities that belong to them. A profile is a role with its own reasons, not a demographic slice and not a job title borrowed from an org chart. "First-time buyer" is a profile because they arrive knowing nothing and need proof before they'll commit; "25-34 year olds" is not, because nothing follows from it. The test for two profiles rather than one: would they take different paths through the same journey, or want different things at the same step? If they'd behave the same way, they are one profile with a broader description — merge them. Use 'customer' for someone who buys or uses what the organization offers, 'employee' for someone inside it who serves the experience, 'organization' when the persona really is a company or team rather than an individual, 'agent' for an AI agent acting on someone's behalf, and 'system' for software that takes part in the experience with nobody driving it.

create_profile

Create a record of any object this organization tracks — a need, a metric, a brand, anything list_resource_kinds names — optionally attaching it to steps. Journeys have their own tool, and labeling kinds (brand, product) go on the map with apply_label, never step_ids.

create_resource

Delete an atlas: its stages and placements go with it, the journeys placed on it are untouched. Not undoable — check get_atlas first.

delete_atlas

One atlas in full: its stages in order (each a 1-based column) and every placed journey with the columns its bar spans.

get_atlas

One report in full: title, subtitle, and its sections in order, each with the id the section tools take. A chart section also reports what its chart currently shows, so you can write about the numbers.

get_document

One help guide in full, as Markdown, by its slug from search_help_guides.

get_help_guide

The full stage-and-step tree for one journey, including which resources are attached to each step.

get_journey

The workspace's checklist run against a journey: whether the map is complete enough to act on — described, staged, steps carrying actions and needs, needs scored and evidenced, a goal and a metric. Each check passes, fails or skips (nothing to judge), with a one-line reason. Omit journey_id for every journey's tally and failing checks, weakest first.

get_journey_checks

A metric's readings, oldest first, between two days. list_resources shows only the latest 30; use this for the history behind them. Each reading says whether an integration synced it.

get_metric_readings

Add a section to a report, after a named section or at the end. A report holds at most 12 sections.

insert_document_section

Link two resources — a pain point to the solution that addresses it, a need to the opportunity it raises. Stored one way and read from both, so linking A to B is the same as linking B to A.

link_resources

List the organization's atlases — journey-of-journey charts that plot whole journeys as bars across shared stages, gantt-style.

list_atlases

Recent change sets, newest first: each is what one person's action, one MCP session, one assistant turn or one workflow run changed, which revert_change_set can undo together. Kept 90 days.

list_change_sets

What changed in the workspace between two days, newest first: resources created, edited and deleted (each edited field with what it was and what it became, statuses included), evidence attached, drafts approved or rejected, and journeys and atlases created or changed. Give journey_id to keep to one journey and the resources on its steps. Defaults to the last 7 days.

list_changes

The organization's reports — written documents edited in the app and exported to Word or PDF — newest first, with ids for get_document.

list_documents

The evidence behind one resource, or evidence across the workspace matching a search. Each piece says which resources it backs and where it came from.

list_evidence

The workspace's file library — documents and images members uploaded for reference. Each entry says whether it has readable text; read one with read_file.

list_files

A journey's saved views — named ways of reading its map: which lanes show, in what order, and which cards pass the filters — and the lane keys the map has for a view to name.

list_journey_views

List the organization's journeys with their stage and step counts.

list_journeys

The organization's lists — curated collections of records — each with the record ids it already holds, so an add can skip what's already there.

list_lists

The organization's members. Call this to find the user id that assigns work — an assignee is a user, not a membership.

list_members

List the organizations you belong to, with each organization's id (needed by every other tool), your role in it, and whether it admits MCP clients (mcp_enabled: false means every other tool will refuse it).

list_organizations

List the organization's profiles (personas and segments).

list_profiles

The objects this organization tracks, with every attribute each one carries — keys, types, and the options its selects offer. Objects are per-organization, so call this before creating or filtering resources.

list_resource_kinds

List the organization's resources of one kind, with their priority, status and scores.

list_resources

Move a section to sit after another, or to the top.

move_document_section

Counts of everything in the organization plus its journeys. Call this first to orient.

organization_overview

Place a journey on an atlas as a bar spanning stages, or move a bar already there. A journey appears on an atlas at most once, so placing a placed journey moves its bar.

place_journey_on_atlas

Read one file from the library. Text and PDFs return their text in windows — pass the next_offset that comes back to continue a long file. Images are returned as the image itself, so you can look at screenshots and journey maps.

read_file

One item from the research repository in full, by its ref from search_research: a highlight's exact words with who said them, in which interview and when; or the text of a note (a whole interview or transcript), doc or theme, in windows — pass the next_offset that comes back to read on.

read_research

Take a stage (column) off an atlas. Nothing placed is lost: a bar that started on it moves to the first column, one that ended on it shrinks to its start. To merge two stages, remove one, rename the other, and re-place any bar that shrank.

remove_atlas_stage

Take one section out of a report.

remove_document_section

Take a piece of evidence off one resource. It stays on any other resource it backs; evidence left backing nothing is deleted.

remove_evidence

Take a flow arrow off a journey map. The records at either end stay.

remove_flow_arrow

Take a journey's bar off an atlas. The journey itself is untouched — an atlas holds placements, never the journeys themselves.

remove_journey_from_atlas