add_agenda_item
ChatGPTAdd a section to a meeting's agenda. Pass title for a custom discussion section, or tool to surface one of the space's tools (metrics scorecard, rocks, todos, issues, ...) as a section. New sections land just above the conclusion and carry over to future occurrences of a recurring meeting, so this is how a custom meeting format is built. Use get_meeting to see the current agenda with section IDs, update_agenda_item to rename or re-time sections, and remove_agenda_item to take sections out.
add_checklist_item
ChatGPTAdd a checklist item to a todo. Creates the checklist if the todo doesn't have one yet. Use get_todo to see existing checklist items, and list_todos to find todo IDs.
add_seat_role
ChatGPTAdd a role to a seat on an Accountability Chart, after its existing roles. A role is one of the seat's key responsibilities, such as 'Lead, Manage, Accountability'. Seat IDs come from get_accountability_chart. Returns the seat with all of its roles.
archive_resource
ChatGPTArchive a record — a todo, rock, issue, and other archivable items (see resource_type). Archiving keeps the record but hides it from the active lists; it stays available under the space's archived filter and can be unarchived from the app. Use trash_resource to delete a record instead. Use the matching list/get tool to find the resource_id first.
archive_space
ChatGPTArchive a team or project. Archiving hides the space and its rocks, todos, issues, metrics, and meetings from lists and dashboards, but deletes nothing — use unarchive_space to reverse it. Two effects are not reversed by unarchiving: archiving a team clears it as anyone's primary team, and archiving a project removes people's pins for it. The leadership team cannot be archived. Use archive_resource to archive records inside a space instead.
checkin_metric
ChatGPTCheck in a metric value for a given period. Defaults to the current visible period on the scorecard (the previous period when the scorecard hides the current one, otherwise the current period). Pass a date to check in for the period containing that date (e.g. "2026-04-06" checks in for the week of Apr 6–12, or for that exact day on a daily metric). If a check-in already exists for that period it will be updated. Use list_metrics to find metric IDs.
checkin_project
ChatGPTRecord a check-in on a project: set its current status, optionally update progress (0-100%), and add context. Any rocks linked to this project have their check-ins derived from this one automatically. Returns the new check-in and updated project status. Use list_projects to discover project IDs.
checkin_rock
ChatGPTRecord a check-in on a rock (90-day priority): set its current status, and for targeted rocks, the latest progress value. Returns the new check-in and updated rock status. Use list_rocks to discover rock IDs.
complete_checklist_item
ChatGPTMark a checklist item as complete or incomplete. Use get_todo to see checklist items and their IDs.
complete_milestone
ChatGPTMark a rock's milestone done or reopen it. Use get_rock to see milestones and their IDs; use update_milestone to change its title, date, or owner.
complete_todo
ChatGPTMark a todo as complete or incomplete. Use list_todos to find todo IDs. Optionally add a comment when completing (e.g. to explain the outcome or provide context).
create_check_in
ChatGPTCreate a new check-in: a question asked to a team, person, or project space (or company-wide) on a recurring schedule. Provide team_id, person_id, or project_id to specify where it belongs, or omit all three for a company-wide check-in. Use list_teams, list_people, or list_projects to find valid space IDs. Defaults to asking every non-viewer member of the space, weekly on weekdays at 9am in the caller's time zone. Use update_check_in to change the schedule or participants later.
create_check_in_answer
ChatGPTAnswer a check-in question. Use list_check_ins to discover check_in IDs.
create_core_process
ChatGPTCreate a core process in a team's space: one of the few documented, repeatable ways the business runs, such as hiring or sales. Pass the team_id of the team to create it in. Title is required. It is owned by you unless owner_id is passed (a person ID from list_people); the owner must be a member of the space, and if you are not, it has no owner. The owner is subscribed to it. Pass subprocesses, each with optional steps, to create the whole outline in one call; if anything is invalid nothing is created. Use create_subprocess and create_step to add to a core process that already exists. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created core process with its sub-processes and steps.
create_doc
ChatGPTCreate a doc in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id (use list_teams / list_people / list_projects for IDs). Provide a title (and optional content) to create a doc from scratch, or a template_id from list_templates(type: "doc") to seed it from a template, not both. Pass a folder_id from list_docs to create the doc inside that folder; omit it to create the doc at the top level of the space's docs. From-scratch docs are saved as drafts unless publish: true is passed; docs created from a template are always published. When creating a draft, give the user the returned url so they can review it — publish it later with update_doc (publish: true) when they ask, or they can publish from the web app.
create_doc_folder
ChatGPTCreate a folder for docs in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id. Pass a parent_id from list_docs to nest the folder inside another folder; omit it to create the folder at the top level. Returns the new folder's id: pass it as folder_id to create_doc or update_doc to put docs in it.
create_headline
ChatGPTCreate a new headline in a team, person, or project space. A headline is a short piece of customer or employee news, good or bad, shared in the meeting without discussion. Anything that needs discussion is an issue. Provide exactly one of team_id, person_id, or project_id to specify where the headline belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required.
create_issue
ChatGPTCreate a new issue in a team, person, or project space. An issue is anything unresolved: a problem, obstacle, opportunity, or idea the team needs to identify, discuss, and solve. It states what is wrong or open, not the fix. If the action is already agreed, that is a todo. Provide exactly one of team_id, person_id, or project_id to specify where the issue belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required.
create_message
ChatGPTCreate a new message in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id to specify where the message belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required. Defaults to publishing immediately, which notifies subscribers; pass publish: false to leave it as a draft. When creating a draft, give the user the returned url so they can review it — publish it later with update_message (publish: true) when they ask, or they can post it from the web app.
create_metric
ChatGPTCreate a new metric (measurable) on a team, person, or project scorecard. A measurable is one weekly, activity-based number with one owner and a goal, on a scorecard of 5-15. Leading indicators (what the team does) over lagging results (what happened). Provide exactly one of team_id, person_id, or project_id to specify which scorecard the metric belongs to. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required; the metric defaults to a weekly, plain-number measurable owned by the current user with a "greater than or equal to" goal, so target_value is required. For a range goal, pass target_type 'between' along with target_min_value and target_max_value. Use checkin_metric to record values after creation.
create_milestone
ChatGPTAdd a milestone to a rock. Milestones break a quarterly rock into the checkpoints that show it is on track before the due date arrives, so each one names a deliverable with a date the owner can tick off. Give the rock and a title; the milestone is unassigned and undated unless you say otherwise. Use list_rocks to find rock IDs and get_rock to see a rock's existing milestones. Use complete_milestone to mark one done, and get_milestone for one milestone's full context.
create_project
ChatGPTCreate a new project in the current organization. Title is required. Optionally pass a template_id to seed the project from a project template (use list_templates type: "project" to discover IDs; template content is materialized asynchronously). When template_id is provided, the template controls privacy and description — explicit values for those fields are ignored. You are always added as a member; pass person_ids to add others at the same time, using list_people to find person IDs. Use update_project to rename a project or change who is on it.
create_rock
ChatGPTCreate a new rock in a team, person, or project space. A rock is one of a team's 3-7 most important priorities for the quarter, judged Done or Not Done at quarter end, so it is specific and measurable with one owner. Work that fits in a week is a todo; something unresolved is an issue. Provide exactly one of team_id, person_id, or project_id to specify where the rock belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required; the rock defaults to a binary (on/off-track) rock owned by the current user, due at the end of the quarter. For a measurable rock, pass check_in_type 'with_target' along with start_value, target_value, and value_format. Pass backlogged: true to create a planned rock in the backlog. Pass milestones to break the rock into checkpoints as it is created; the response returns them with their IDs on the rock, so update_milestone can date or assign one afterwards. Use checkin_rock to record progress after creation.
create_seat
ChatGPTAdd a seat to an Accountability Chart, reporting to an existing seat on that chart. Seat IDs come from get_accountability_chart, and assignee IDs from list_people. A seat can't report to the Owner's Box, or to the Visionary when the Visionary and Integrator sit side by side. Use add_seat_role to give the new seat its roles.
create_shoutout
ChatGPTCreate a new shoutout (peer recognition) in a team, person, or project space, or company-wide. Provide team_id, person_id, or project_id to specify where the shoutout belongs, or omit all three for company-wide recognition. Use list_teams, list_people, or list_projects to find valid space IDs. Shoutouts require at least one recipient and at least one recognized core value. Pass company_shoutout: true to surface a team/person/project shoutout to the whole company.
create_step
ChatGPTAdd a step to a sub-process: one concrete action in how the work gets done. Title is required. The step is added after the existing steps. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created step. Sub-process IDs come from get_core_process.
create_subprocess
ChatGPTAdd a sub-process to an existing core process: one stage of how the core process runs, such as interviewing within hiring. Title is required. It is added after the existing sub-processes, in the core process's space, in the 'identify' phase unless phase is passed, and owned by the core process's owner unless owner_id is passed (a person ID from list_people; the owner must be a member of the space). Pass steps to create its steps in the same call, or add them later with create_step; if anything is invalid nothing is created. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created sub-process with its steps.
create_team
ChatGPTCreate a new team in the current organization. The name must be unique across the organization's teams. New teams start with the organization's standard tools enabled and their default meetings scheduled. You are always added as a member; pass person_ids to add others at the same time, using list_people to find person IDs. Use list_teams to see existing teams, or get_team for a team's full context. Use update_team to rename a team or change who is on it.
create_todo
ChatGPTCreate a new todo in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id to specify where the todo belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Either title or template_id is required. When template_id is given, the template's title, description, priority, and checklist seed the todo; any of those fields you also pass override the template defaults. Use list_templates(type: "todo") to discover template IDs. Custom fields can be set by name and option label via custom_fields — use get_team, get_person, or get_project to discover available fields and options for the space.
create_todo_list
ChatGPTCreate a new todo list in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id, plus a title. The list is added after the space's other undocked lists and starts empty. Returns the list with its id; pass that id as todo_list_id to create_todo or move_todo to put todos in it.
delete_check_in_answer
ChatGPTPermanently delete a check-in answer. Unlike other resources, check-in answers have no trash and cannot be restored. Only the creator can delete their own answer. Use list_check_in_answers to discover check_in_answer IDs.
get_accountability_chart
ChatGPTGet the public company-wide Accountability Chart. Returns the chart's reporting structure and every seat's assignees, purpose, roles, and role descriptions. This does not return private team Accountability Charts. Use create_seat and update_seat to change seats, and add_seat_role, update_seat_role, or remove_seat_role to change their roles.
get_check_in
ChatGPTGet a check-in's full context: its schedule, participants, and the most recent answers. Use list_check_in_answers for older answers beyond what's shown here. Use list_check_ins to discover check-in IDs.
get_company
ChatGPTGet a top-down view of the company: basics, current quarter dates, leadership team id, current quarter company rocks, company scorecard, and teams list. Provides full organizational context in one call. rocks and metrics are capped; rocks_count and metrics_count give the totals. For the V/TO use get_vto. For the public company-wide Accountability Chart use get_accountability_chart.
get_core_process
ChatGPTGet a core process's full context: title, owner, description, whether it is published and its latest published version, its sub-processes in order (each with phase, owner, description, and steps; a sub-process can live in another team's space, named in its space), the rocks and metrics it tracks, and comments, everything in one call. Returns the live record only, never a published version's contents, and omits sub-processes, rocks, and metrics you cannot access. Use list_core_processes to discover core process IDs. Use get_published_process for the published version's contents.
get_doc
ChatGPTRead a doc's content and comments. Returns the document body for document-type docs, the URL for link-type, or the filename for uploads, along with the comment count and any comment threads (useful for ranking VoC requests by customer demand). Use list_docs to discover doc IDs.
get_headline
ChatGPTGet a headline's full context: title, status, owner, description, related resources, subscribers, and comments — everything in one call. Use list_headlines to discover headline IDs.
get_issue
ChatGPTGet an issue's full context: title, status, owner, description, resolution, related resources, subscribers, and comments — everything in one call. Use list_issues to discover issue IDs.
get_me
ChatGPTGet the authenticated user's identity and authorized organization memberships, including each organization's leadership team id. Use get_my_profile for their teams, projects, and working context within an organization.
get_meeting
ChatGPTGet a meeting's full context. For completed meetings, returns a recap: attendees, todos created, issues solved/opened, headlines, ratings, and notes. For upcoming meetings, returns a one-call prep brief: enriched agenda, open IDS issues (team meetings), and outstanding todos. Use list_meetings to discover meeting IDs. Agenda section IDs in the output can be passed to update_agenda_item and remove_agenda_item. When transcript_available is true, get_meeting_transcript returns the verbatim wording.
get_meeting_transcript
ChatGPTGet the verbatim transcript of a recorded meeting, as plain text. Often 10k+ tokens — call this only when the user asks for the exact wording or a direct quote. For attendees, todos, issues, decisions, or a recap, use get_meeting instead. Use list_meetings to discover meeting IDs.
get_message
ChatGPTGet a message's full context: content, subscribers, comments, related resources, and metadata. Use list_messages to discover message IDs.
get_metric
ChatGPTGet a metric's full context: title, assignee, description, target, frequency, formula (for calculated metrics), recent check-in history, subscribers, and comment count. Values match the scorecard, including formula-computed values for calculated metrics. Use list_metrics to discover metric IDs.
get_milestone
ChatGPTGet a milestone's full context: title, completion, due date, assignee, description, the rock it belongs to, and the issues, todos and shoutouts created from it. A milestone URL ends in its ID, so a link pasted by the user resolves here. Use get_rock to see all of a rock's milestones and their IDs.
get_my_profile
ChatGPTGet the authenticated person's profile: name, role, title, teams, projects, accountability chart seats, direct reports, manager, members, and enabled tools. Start here to understand who the current user is.
get_person
ChatGPTGet a person's profile: name, role, title, manager, teams, projects, accountability chart seats, direct reports, members, and enabled tools. Use list_people to discover person IDs.
get_project
ChatGPTGet a project's overview: title, status, progress, dates, description, members, and enabled tools. Provides full context about a project space. Use list_projects to discover project IDs.
get_published_process
ChatGPTGet one of the organization's published core processes ("The {Org} Way", the documented way the company runs): its latest published version with the sub-processes in order, each with its owner, description, and steps, plus the title, owner, space, and description as they are now. Visible to everyone in the organization except external users. Returns the latest published version only. Use list_published_processes to discover core process IDs. Use get_core_process for the live working copy, which may differ from what was published.
get_recent_notifications
ChatGPTSee what needs the current user's attention. Returns the 10 most recent unread notification groups as a markdown summary — each group represents a distinct record with a count of unread notifications, who triggered the latest one, and a link. For record types that have detail tools (Todo, Message, Metric, Project), the summary includes which tool to call for full context. Typically called after get_my_profile to see what needs the user's attention. Use list_notifications for paginated structured data or to browse read notifications.
get_rock
ChatGPTGet a rock's full context: title, status, backlog state, assignee, due date, description, milestones, recent check-ins, related resources, subscribers, and comments — everything in one call. Use list_rocks to discover rock IDs, and get_milestone for one milestone's full context.
get_shoutout
ChatGPTGet a shoutout's full context: creator, recipients, recognized core values, content, and comments — everything in one call. Use list_shoutouts to discover shoutout IDs.
get_team
ChatGPTGet a team's overview: name, description, members, and enabled tools. Provides full context about a team space. Use list_teams to discover team IDs.
get_todo
ChatGPTGet a todo's full context: title, status, assignee, description, custom field values, checklist, related resources, subscribers, and comments — everything in one call. Use list_todos to discover todo IDs.
get_vto
ChatGPTGet the company's Vision/Traction Organizer: core values, core focus, 10-year target, 3-year picture, 1-year plan, quarterly rocks, strategy, and SWOT analysis. Provides strategic context for all EOS work. For a broader org snapshot (teams, scorecard) use get_company.
list_check_in_answers
ChatGPTList check-in answers: what people have said in response to check-in questions. Provide check_in_id to see every answer to one check-in, or team_id, person_id, or project_id to see answers to every check-in in that space. Omit all of them for every answer across the company. Provide check_in_id, or a space id, not both. Returns each answer's full text. Use list_check_ins to discover check-in IDs.
list_check_ins
ChatGPTList check-ins (recurring questions asked on a schedule) in a team, person, or project space, or company-wide. Returns summary info for each check-in including its schedule, next ask date, and participant count. Provide team_id, person_id, or project_id to scope to a space, or omit all three for company-wide check-ins. Use get_check_in for full context including recent answers, and list_check_in_answers to see what people have said. Pass cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_core_processes
ChatGPTList a team's core processes: the documented, repeatable ways the business runs. Pass the team_id of the team whose core processes to list, in the team's own manual order. Archived core processes are not listed. Returns summary info for each, including its owner and whether it is published. Use get_core_process for sub-processes, steps, tracked rocks and metrics, and comments. Published versions are read with list_published_processes. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_docs
ChatGPTList docs. Omit team_id, person_id, and project_id to list docs at the company level; pass one to list a team, person, or project space's docs. Returns the catalog for the selected scope: folder structure and every doc with its folder path and comment count. Published docs only by default — pass status_in to include your own drafts. Use get_doc to read full content.
list_headlines
ChatGPTList headlines in a team, person, or project. Returns summary info for each headline. Provide exactly one of team_id, person_id, or project_id. Use get_headline for full context including description and comments. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_issues
ChatGPTList issues in a team, person, or project. Returns summary info for each issue. Provide exactly one of team_id, person_id, or project_id. Use get_issue for full context. Use create_issue to add new issues, comment_on_resource to comment, or resolve_issue to mark resolved. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_meetings
ChatGPTList meetings (L10s, quarterlies, 1:1s, custom, etc.) in a team, person, or project. Returns summary info for each meeting. Provide exactly one of team_id, person_id, or project_id. Use get_meeting for full context including attendees, agenda, notes, and recap. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_messages
ChatGPTList messages. Omit team_id, person_id, and project_id to list messages posted at the company level; pass one to list a team, person, or project space's messages. Returns summary info for each message. Use get_message for full message content, comments, and activity. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_metrics
ChatGPTList metrics (measurables) in a team, person, or project scorecard. Returns each metric's title, assignee, target, frequency, current status (on track, off track, or not checked in), and scorecard category, plus the scorecard's available categories — use a category id with create_metric or update_metric to categorize a metric. Provide exactly one of team_id, person_id, or project_id. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_notifications
ChatGPTList notifications for the current user, grouped by the record they relate to. Defaults to unread. Use get_recent_notifications for a rich markdown summary of what needs attention. This tool returns structured data for pagination and filtering by read status. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_people
ChatGPTList people. Omit team_id and project_id to list everyone in the company; pass one to list only that space's members. External people and observers can only list the members of a team or project they belong to. Pass the returned id as person_id to list_todos and other space-scoped tools. Pass next_cursor from the previous response to fetch the next page.
list_projects
ChatGPTList projects the current person can access. Returns each project's id and name. Pass the id as project_id to list_todos and other space-scoped tools.
list_published_processes
ChatGPTList the organization's published core processes: "The {Org} Way", the documented way the company runs. Returns the latest published version of each, with its owner, space, version, and when and by whom it was published; system_name is what the organization calls the collection. Visible to everyone in the organization except external users. Use get_published_process for the published sub-processes and steps. Use list_core_processes and get_core_process for the live working copy, which may differ from what was published. Ordered by title. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_rocks
ChatGPTList rocks (90-day priorities). Omit team_id, person_id, and project_id to list rocks owned at the company level; pass one to list a team, person, or project space's rocks. To find rocks anywhere in the org that are flagged as visible-at-the-company-level (a per-rock setting), pass company_wide_eq: true instead — see that filter for details. Returns summary info for each rock, including whether it is backlogged. Use get_rock for full context including description, milestones, check-ins, and comments. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_shoutouts
ChatGPTList shoutouts (peer recognition) in a team, person, or project space, or company-wide. Returns summary info for each shoutout including creator, recipients, and recognized core values. Provide team_id, person_id, or project_id to scope to a space, or omit all three for company-wide shoutouts. Use get_shoutout for full context including content and comments. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_teams
ChatGPTList teams the current person can access. Returns each team's id and name, and flags the company's leadership team. Pass the id as team_id to list_todos and other space-scoped tools.
list_templates
ChatGPTList templates of a given type that your organization owns. Each result is an {id, type, title} summary — enough to choose a template and pass its id as template_id to the create tool of the same name (create_project, create_doc, create_todo), which applies the template's pre-configured defaults without restating every field. Project templates also carry contents: the tools the new project starts with and the todo lists, todos, custom fields, metrics, docs, and check-in questions each tool is seeded with. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
list_todos
ChatGPTList todos (to-do items) in a team, person, or project. Returns summary info for each todo, including any custom field values. Provide exactly one of team_id, person_id, or project_id. Use get_todo for full context including description, checklist, and comments. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
move_todo
ChatGPTMove a todo to a different todo list or to another team, person, or project space. Pass todo_list_id to target a specific list (from get_team, get_person, or get_project), or pass exactly one of team_id, person_id, or project_id to move the todo to that space's default list. If the space has no default list, the todo is placed in the space without a list and the response's todo_list is null. Optionally assign the todo to yourself. Use list_todos to find todo IDs.
relate_resources
ChatGPTLink two resources together ("Related to") — for example an issue to a rock, a todo to a meeting, or a doc to a metric. Use the matching list/get tools to find the source_id and target_id first.
remove_agenda_item
ChatGPTRemove a section from a meeting's agenda. Custom sections are deleted; tool sections are only taken off the agenda — the tool and its data stay in the space. The segue and conclusion can't be removed. Use get_meeting to see the agenda with section IDs.
remove_seat_role
ChatGPTDelete a role from an Accountability Chart seat. This can't be undone. Role IDs come from get_accountability_chart. Returns the seat with its remaining roles.
resolve_issue
ChatGPTMark an issue as resolved or unresolved. Use list_issues to find issue IDs. When resolving, provide a resolution explaining how the issue was solved.
search
ChatGPTFull-text search across the user's accessible content: issues, headlines, rocks, rock check-ins, metrics, metric check-ins, meetings, messages, to-dos, decisions, agenda items, comments, docs, core processes, subprocesses, and spaces. Keyword search, not question answering: pass the distinctive terms (australian pricing), not a whole question (what did we decide about australian pricing), which can match nothing. Results cover only records the user can access. Scope to one space with team_id, person_id, or project_id whenever the target space is known — org-wide results are much noisier — and pass a result's space.id straight back as the matching filter. Each hit reports the model value this tool's model filter takes. Snippets are truncated, so fetch the record with the matching get_ tool before relying on its content; not every type has one. Pass next_cursor from the previous response to fetch the next page. Iteration is complete when next_cursor is absent.
trash_resource
ChatGPTMove a record — a todo, rock, issue, and other trashable items (see resource_type) — to the trash. This is the same as deleting it in the app: the record leaves its lists but can be restored from the space's trash within the 30-day restore window. Use the matching list/get tool to find the resource_id first.
unarchive_space
ChatGPTUnarchive a team or project, returning it and its contents to lists and dashboards. This does not restore what archiving cleared: a team is not restored as anyone's primary team, and a project's pins are not recreated. Use archive_space to archive a space.
unrelate_resources
ChatGPTRemove a relationship between two resources that was created with relate_resources — for example unlink an issue from a rock, a todo from a meeting, or a rock from its parent rock. Pass the two resources in either order. Succeeds as a no-op if they are not currently linked.
update_agenda_item
ChatGPTUpdate a section of a meeting's agenda. Only provided fields are changed. Title and description can only change on custom sections and the segue/conclusion — tool sections take their name from the tool they surface. Use get_meeting to see the agenda with section IDs, and add_agenda_item / remove_agenda_item to change which sections exist.
update_check_in
ChatGPTUpdate a check-in's question, participants, or schedule. Only provided fields are changed; omitted fields, including individual schedule fields, keep their current values. Use list_check_ins to discover check-in IDs.
update_check_in_answer
ChatGPTUpdate a check-in answer's text. Only the creator can update their own answer. Use list_check_in_answers to discover check_in_answer IDs.
update_core_process
ChatGPTUpdate a core process's title, description, or owner. Only provided fields are changed. Pass null for owner_id to clear the owner; a new owner must be a member of the core process's space (person IDs come from list_people). Sub-processes and steps are updated with update_subprocess and update_step. Use list_core_processes to discover core process IDs. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety.
update_doc
ChatGPTUpdate a doc's title or body, move it to another folder or the top level, or publish a draft by passing publish: true. Only provided fields change. Content applies only to document-type docs (not link or upload docs). Use list_docs to find doc IDs and get_doc for current content.
update_doc_folder
ChatGPTRename a doc folder, change its description, or move it under another folder or to the top level. Only provided fields change. Use list_docs to find folder IDs. To move a doc between folders, use update_doc.
update_issue
ChatGPTUpdate an issue's editable fields (title, description, type, priority, owner, subscribers). Only provided fields are changed. Use list_issues to find issue IDs, and get_issue for current content. Use resolve_issue to mark an issue resolved or unresolved.
update_message
ChatGPTUpdate a message's title, content, or subscribers, or publish a draft by passing publish: true. Only provided fields are changed. Publishing notifies subscribers; editing a published message notifies anyone newly mentioned in the content. Use list_messages to find message IDs, and get_message for current content.
update_metric
ChatGPTUpdate a manual metric's (measurable's) editable fields: title, description, assignee, check-in frequency, number format, target, and scorecard category. Only provided fields are changed. Pass null for assignee_id or category_id to clear them. When changing the target, past check-ins keep their original targets unless apply_target_to_past_checkins is true. Use checkin_metric to record values, list_metrics to discover metric and category IDs, and get_metric for current context.
update_milestone
ChatGPTUpdate a milestone's title, due date, assignee, or description. Only provided fields are changed. Use get_rock to see a rock's milestones and their IDs, get_milestone for one milestone's full context, and complete_milestone to mark it done or reopen it.
update_project
ChatGPTUpdate a project's title, description, dates, privacy, or membership. Only the fields you pass are changed. Changing start_date or end_date also moves the start and due dates of every rock linked to the project. Removing a member also removes their votes, their invitations to the project's upcoming meetings, and their pins for the space, and a project must always keep at least one member. Use list_projects to discover IDs, get_project for current context and membership, and list_people to find person IDs. Use checkin_project to report status and progress, and archive_space to archive a project.
update_rock
ChatGPTUpdate a rock's editable fields, company-wide visibility, or backlog state. Only provided fields are changed. Pass null for assignee_id, start_date, or due_date to clear them. Use checkin_rock to update status or progress. Use list_rocks to discover rock IDs and get_rock for current context.
update_seat
ChatGPTUpdate a seat on an Accountability Chart: its name, purpose, the people who hold it, or the seat it reports to. Only provided fields are changed. Seat IDs come from get_accountability_chart, and assignee IDs from list_people. Use add_seat_role, update_seat_role, and remove_seat_role to change the seat's roles.
update_seat_role
ChatGPTUpdate a role on an Accountability Chart seat: its title or description. Only provided fields are changed. Role IDs come from get_accountability_chart. Returns the seat with all of its roles.
update_shoutout
ChatGPTUpdate a shoutout's content, recipients, recognized core values, or company-wide sharing. Only provided fields are changed; omitted fields are left unchanged. The space is fixed at creation and cannot be changed here. Only the creator or an account owner can update a shoutout. Use list_shoutouts to discover shoutout IDs.
update_step
ChatGPTUpdate a step's title or content. Only provided fields are changed. Step IDs come from get_core_process. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety.
update_subprocess
ChatGPTUpdate a sub-process's title, description, owner, or phase. Only provided fields are changed. Pass null for owner_id to clear the owner; a new owner must be a member of the sub-process's space (person IDs come from list_people). Changing the phase is recorded in the core process's activity. Steps are updated with update_step. Sub-process IDs come from get_core_process. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety.
update_team
ChatGPTUpdate a team's name, description, privacy, or membership. Only the fields you pass are changed. Removing a member also removes their votes, their invitations to the team's upcoming meetings, and their pins for the space, and a team must always keep at least one member. Use list_teams to discover IDs, get_team for current context and membership, and list_people to find person IDs.
update_todo
ChatGPTUpdate a todo's editable fields. Only provided fields are changed. Pass null for due_date or assignee_id to clear them. Custom fields can be set by name and option label via custom_fields; pass null for a field to clear its value. Use get_team, get_person, or get_project to discover available fields and options. Use move_todo to move between todo lists, and complete_todo to mark complete. Use list_todos to find todo IDs.
update_todo_list
ChatGPTRename a todo list, make it the space's default list, dock it to the left or right of the space's todo board, or reorder it. Only the fields you pass are changed. Returns the updated list. Use create_todo_list to add a new list.
add_checklist_item
Claudecheckin_metric
Claudecheckin_project
Claudecheckin_rock
Claudecomplete_checklist_item
Claudecomplete_todo
Claudecreate_doc
Claudecreate_headline
Claudecreate_issue
Claudecreate_message
Claudecreate_metric
Claudecreate_project
Claudecreate_rock
Claudecreate_shoutout
Claudecreate_todo
Claudedelete_shoutout
Claudeget_company
Claudeget_doc
Claudeget_headline
Claudeget_issue
Claudeget_mcp_resource
Claudeget_meeting
Claudeget_message
Claudeget_metric
Claudeget_my_profile
Claudeget_person
Claudeget_project
Claudeget_recent_notifications
Claudeget_rock
Claudeget_shoutout
Claudeget_team
Claudeget_todo
Claudeget_vto
Claudelist_docs
Claudelist_headlines
Claudelist_issues
Claudelist_meetings
Claudelist_messages
Claudelist_metrics
Claudelist_notifications
Claudelist_people
Claudelist_projects
Claudelist_rocks
Claudelist_shoutouts
Claudelist_teams
Claudelist_templates
Claudelist_todos
Claudemove_todo
Clauderesolve_issue
Claudesearch
Claudeupdate_message
Claudeupdate_shoutout
Claudeupdate_todo
Claude
