L10_todos_issues
ChatGPTReads a team's whole Level 10, to-dos (open, done, parked) and issues. The Level 10 (L10) has four sections: To-Dos (next), Done, Issues (blocked) and Parked (the parking lot). An EOS team calls it the Level 10; every other team calls the same list its Weekly board. A done or parked to-do is still a to-do. all defaults to false, which keeps each section's 7-day window (to-dos due within the next 7 days, done to-dos and issues completed in the last 7 days); set it to true to read every to-do and issue in every section. The answer is raw JSON, so build the table yourself (name, assignee, due, ids). Long-term issues are never on the Level 10 — read them with issues. Headlines are not part of this answer — use list_headlines for the team's Headlines. To read one section with filters or paging, use list_L10_section.
add_1on1_issue
ChatGPTCreates a new issue on a 1-on-1, in its Issues section. A name containing @login assigns that person, exactly as typing it on the 1-on-1 does. To add a to-do use add_1on1_todo; to put a to-do or issue that already exists on the 1-on-1 instead, use place_on_1on1; to move one to another section afterwards use move_on_1on1, to mark it done use mark_done, and to edit it use update_item.
add_1on1_todo
ChatGPTCreates a new to-do on a 1-on-1, in its To-Dos section. A name containing @login assigns that person, exactly as typing it on the 1-on-1 does. To put a to-do or issue that already exists on the 1-on-1 instead, use place_on_1on1; to add an issue use add_1on1_issue; to move one to another section afterwards use move_on_1on1, to mark it done use mark_done, and to edit it use update_item.
add_L10_issue
ChatGPTCreates a new issue on a team's Level 10. It goes in the Issues section and gets no due date. Once it is solved, mark it done with mark_done; if it needs more work, add a fresh to-do with add_L10_todo instead. To add a new to-do, use add_L10_todo; for a new long-term issue, use add_long_term_issue; to put an issue that already exists on the Level 10, use place_on_L10.
add_L10_todo
ChatGPTCreates a new to-do on a team's Level 10. It goes in the To-Dos section, and a to-do given no due date gets one 7 days out. Its name is kept with a #next routing hashtag on the end; that is expected. To put a to-do or issue that already exists on the Level 10, use place_on_L10; to add a new issue, use add_L10_issue.
add_label
ChatGPTPuts one label on a to-do, an issue, a 1-Year Goal or a page, by the label's name, and leaves every other label on it as it was. A personal label needs only the right to open the target; a team or project label needs the right to edit it. A label already on the target changes nothing. Answers with the target and the labels it now carries. Use list_labels to see the labels you can use; take one off with remove_label.
add_long_term_issue
ChatGPTCreates a new issue on a team's long-term list. A long-term issue is never on the Level 10, so this is not the same as add_L10_issue, which creates an issue on the Level 10. It gets no due date. To read the long-term list, use issues with list long-term; to switch an existing issue between short-term and long-term, use change_issue_type; to take an issue off the long-term list and make it a team's issue on the Level 10, use place_on_L10 with section issues.
add_result_update_attachment
ChatGPTAttaches a file to your own result update by its link. Registers an already-hosted file against the result update, so place_on_result_update can show it on a section by id. Takes a URL, not a file upload — the file must already live at a reachable URL, and nothing is uploaded by this tool. Answers with the document id to pass in place_on_result_update's attachment_ids. Defaults to today's result update. Backed by the documented REST route POST /api/v2/result-feed/{date}/attachments (see https://api.resultkit.ai/api-docs/v2).
add_result_update_issue
ChatGPTCreates a new issue under Blocked in your own result update. To create a to-do use add_result_update_todo, and to put a to-do or issue that ALREADY exists into a section use place_on_result_update. Defaults to today's result update.
add_result_update_todo
ChatGPTCreates a new to-do in a section of your own result update. The section sets the new to-do's status: done completes it, next marks it next. A to-do goes in Done or Next only — to log an issue under Blocked use add_result_update_issue, and to put a to-do or issue that ALREADY exists into a section use place_on_result_update. Defaults to today's result update.
add_seat_link
ChatGPTAdd a reference link to a seat — the playbook, process doc, or dashboard the person in the seat works from. The url must start with http:// or https://. The title defaults to the url when none is given.
add_to_work_plan
ChatGPTCreates a new to-do on the plan. Defaults to today's plan when date is omitted, creating today's plan if you do not have one yet; a plan for another date must already exist. On today's plan, hashtags in the name are kept and acted on — #must marks the to-do a MUST, #daily makes it recur every day, and #next or #1-#4 set its Eisenhower quadrant; on another date none of that happens and #next is stripped from the stored name. The answer carries the new to-do's id. To put an existing to-do on the plan, use attach_to_work_plan instead.
align_milestone
ChatGPTConnects a Milestone to its Rock. Pass parent_id as null to remove the connection. The parent must be a Rock in the same team.
align_rock
ChatGPTConnects a Rock to the 1-Year Goal it advances. Pass parent_id as null to remove the connection. The parent must be a 1-Year Goal in the same team.
align_seat_goal
ChatGPTMakes a seat accountable for a 1-Year Goal or a Rock — one tool covers both. A goal sits on at most one seat: aligning a goal that already sits somewhere else silently moves it off that seat. Answers the seat's 1-Year Goals and Rocks after the change as raw rows — id, name, description, achieve_by, current_state.
align_seat_measurable
ChatGPTMakes a seat accountable for a Measurable. A Measurable sits on at most one seat: aligning a Measurable that already sits somewhere else silently moves it off that seat. Answers the seat's Measurables after the change as raw rows — id, name, description, chart_type (numeric), target_value, current_value.
archive_goal
ChatGPTArchive (soft-delete) a 1-Year Goal. Sets the 1-Year Goal's state to archived. Requires creator, assignee, or team admin access.
archive_headline
ChatGPTArchive a headline so it drops off the team's active list right away. The headline is expired rather than removed, so it still appears in the team's headline history. Only the headline's creator or a team admin may archive it. A Headline's text carries no id, so this works only on a Headline that create_headline returned in this chat.
archive_measurable
ChatGPTArchives a Measurable; its history is kept. It comes off the team's default Scorecard view, and list_measurables with include_archived=true still returns it. Archiving an already-archived Measurable is safe. List first with list_measurables and match by name to get the id.
archive_milestone
ChatGPTArchive (soft-delete) a Milestone. Sets the Milestone's status to archived. Requires creator, assignee, or team admin access.
archive_rock
ChatGPTArchive (soft-delete) a Rock. Sets the Rock's state to archived. A team Rock requires creator, assignee, or team admin access. A personal Rock has no team, so its owner alone may archive it.
archive_seat
ChatGPTArchives a seat and every seat beneath it — the whole branch goes, descendants included; they are not moved up to the seat's parent. A team's root seat cannot be archived. Archived seats drop out of the chart unless list_seats is called with include_archived; restore_seat brings a single one back.
attach_to_work_plan
ChatGPTPuts an existing to-do on the plan. It creates nothing new. Defaults to today's plan when date is omitted, creating today's plan if you do not have one yet; a plan for another date must already exist. On today's plan you may attach a to-do you own, a to-do assigned to you, or a to-do belonging to a team you are a member of; on another date, only a to-do you own or are assigned to. Answers an error if the to-do is already on that plan. To create a new to-do and place it in one step, use add_to_work_plan.
change_issue_type
ChatGPTSwitches an issue between short-term and long-term. type is long-term or short-term. Long-term takes the issue off the Level 10 and puts it on the team's long-term list; short-term takes it off the long-term list and puts it in Issues on the team's Level 10 — the same as place_on_L10 with section issues. It acts on the issue's own team, so it takes no team. This is for an issue: given a to-do's id it would turn the to-do into an issue. To create an issue, use add_L10_issue or add_long_term_issue; to read the lists, use issues.
change_member_role
ChatGPTSets a member's role: admin or member. Promotes a team member to admin, or demotes an admin back to member. Only a team admin (or the team's owner) can change roles. Pass the member's user_id — get_team lists every member with their user_id. The team's creator cannot be demoted, and the last remaining admin cannot be demoted: a team always keeps at least one admin.
create_goal
ChatGPTCreate a new 1-Year Goal for an EOS team. 1-Year Goals are annual strategic priorities that Rocks can align to. This creates a team's 1-Year Goal: a personal 1-Year Goal is not created here.
create_headline
ChatGPTCreate a headline (EOS Good News — the People and Customer Headlines shared at a Level 10 meeting) for a team. Headlines are short pieces of good news that stay on the team's active list until they expire; expires_at defaults to 7 days from today when it is not given. Only teams running the EOS framework have headlines; a team on any other framework is refused. It answers with the new Headline, including its id — keep the id: a Headline's text carries no id, so update_headline and archive_headline work only on a Headline created in this chat. To read a team's current headlines instead, use list_headlines.
create_item
ChatGPTCreates a to-do or issue, on a team or personal. Give team_id to put it on a team (you must be a member of that team, and it goes on the team's weekly board); leave it out for a personal one with no team. Give parent_id to create it under another to-do or issue, or in a Project column (project_columns lists the columns). Type is one of Task (a single action), TodoList (a project or checklist that holds other to-dos and issues), Outcome (a result to reach), or KeyResult (a measurable target); it defaults to Task when omitted. To create a Rock, use create_rock; for a 1-Year Goal, use create_goal.
create_label
ChatGPTCreates a label: personal (yours alone; anyone may create one), team (on team_id; created by an admin of that team) or project (on project_id; created by an admin of that project). color is one of Purple, Blue, Teal, Magenta, Amber or Green, or a hex; it defaults to Purple. An organization label is a team label on the organization's top team, shared with every team below it: set shared_with_descendant_teams. If the team already has a label of that name the answer warns and creates nothing; set create_anyway to create a second one.
create_measurable
ChatGPTAdds a Measurable to a team's Scorecard. Requires team-admin rights on that team. List first with list_measurables and match by name, so you do not add one that already exists. direction defaults to higher, meaning a bigger number is better; pass lower when a smaller number is better. An owner, if given, must already be a member of the team.
create_milestone
ChatGPTCreate a new Milestone beneath a Rock. Milestones are checkpoints or sub-deliverables that track progress toward completing a Rock. Give parent_id to place it under a Rock; get the Rock's id first with list_rocks.
create_page
ChatGPTAdds a page at the top level or under another page. The page goes into a team's wiki, nested under a parent page when you give parent_id and at the top level when you leave it out. Who may add one is the team's own pages_creatable_by setting: any team member under all_members, which is the default for a team that has never changed it, and team admins alone under admins_only. A page created under a parent starts with that parent's audience. Answers with the new page's identity — its id, title and where it sits — and NOT with the body you sent, so the answer is the same size whether the page is one line or a whole plan; call get_page to confirm what was saved and to read its content. Backed by the documented REST route POST /api/v2/teams/{id}/pages (see https://api.resultkit.ai/api-docs/v2).
create_project
ChatGPTCreates a project on a team. A Project is a team's board of action items organized in columns; it takes a name and an optional description, on a team the caller can edit. A new Project starts with no columns. Use projects to see the team's existing Projects before adding one, and project_columns to read the new Project's columns and the action items in them.
create_rock
ChatGPTCreate a new Rock (a 90-day priority) for an EOS team. Optionally align it to a parent 1-Year Goal with parent_id; get the 1-Year Goal's id first with list_goals.
create_seat
ChatGPTCreates a seat on the Accountability Chart, either as a report under an existing seat or as a team's first (root) seat. Give parent_id to add a report, or team_id to create the root seat — exactly one is required. If both are given, parent_id wins and the new seat lands on the PARENT seat's team, not on team_id. Creating a root seat requires team admin rights on that team; creating a report requires edit rights on the parent seat. A team can hold only one root seat, and a new team already has one, so add further seats with parent_id. To hand an existing seat to a new owner, use update_seat. A new owner takes over the seat's Goals, Rocks and Measurables.
custom_columns
ChatGPTReads your custom columns and what sits in each. These are the columns of the Custom view in My Work — your own planner buckets — and the to-dos sitting in each one on today's plan. Today's plan is materialized first, so on a fresh day this answers your real board instead of an empty one. Columns come back in board order, each with its to-dos in lane order and a completed flag on every to-do. Alongside them, uncategorized carries the still-open to-dos on today's plan that sit in no column — the leftmost lane of the Custom view. Read-only, and personal: it answers your own board and nobody else's. For a question about your columns, use this, not sequence; for the whole plan as one flat list use sequence; for what you have already finished use list_work_done.
delete_label
ChatGPTDeletes a label, and takes it off every to-do, issue, 1-Year Goal and page it is on. Without confirm it deletes nothing and answers how many items, goals and pages carry the label, so you can ask the person first; call it again with confirm set to delete. The rights are update_label's, and a locked label cannot be deleted.
delete_page
ChatGPTDeletes a page and every page beneath it. To undo it, restore_page brings them back. It removes one page of a team's wiki AND every page nested beneath it — the whole subtree goes, not just the named page. Confirm with the person before deleting a page. Requires the page's author role or team admin; an editor or contributor grant does not carry delete.
get_1on1
ChatGPTOpens one 1-on-1 in full: its two people, its shared notes, the Rocks and Measurables aligned to it, and its to-dos and issues in the three sections: To-Dos (what is coming up), Issues (marked blocked) and Done (completed in the last 10 days). Completed work older than that window is read with list_1on1_section, section done, not here.
get_3_year_vision
ChatGPTReads the 3-year vision: the picture, its date, revenue, profit and Measurables. That is the 3-Year Picture on the V/TO: threeYearPicture holds description (the picture itself), futureDate (the date it describes), revenue, profit and measurables. team_id says whose: the organization's top-level team gives the whole organization's, and any other team gives that team's own. A team set to inherit shows the vision of the team above it, and the answer says so (isInheritingParentVision, parentTeamId, visionTeamId). When no 3-Year Picture has been written, threeYearPicture is null: say so. Show what is set and leave out what is not. Text can carry simple HTML formatting. The answers behind the picture are read with get_vision_canvas, the Core Values, Core Focus, 10-Year Target and Marketing Strategy with get_vision_components, and the 1-Year Plan and the quarterly plans with get_business_plan. Read-only: the vision is not written through these tools; it is written in the vision builder, which open_vision_builder links to.
get_business_plan
ChatGPTReads the plan for 3 years, one year, or one quarter. period says which: '3_years' is the plan for 3 years, the 3-Year Picture that get_3_year_vision also reads (description, futureDate, revenue, profit, measurables); '1_year' is the 1-Year Plan of one year; 'quarter' is the plan for one quarter of a year, the V/TO's Quarterly Rocks. A 1-Year Plan and a quarter's plan each carry text, date, revenue and profit targets, measurables, and revenue_actual and profit_actual, the figures the team is tracking against those targets. year (four digits, like 2026) and quarter (1 to 4) pick which one; they default to the current year and the current quarter. year is used by '1_year' and 'quarter' only and quarter by 'quarter' only, and a year or quarter that the period does not use is refused. team_id says whose: the organization's top-level team gives the whole organization's, and any other team gives that team's own. A team set to inherit shows the vision of the team above it, and the answer says so (isInheritingParentVision, parentTeamId, visionTeamId). When no plan is on file for the period, plan is null: say so. Show what is set and leave out what is not. Text can carry simple HTML formatting. The Core Values, Core Focus, 10-Year Target and Marketing Strategy are read with get_vision_components. Read-only: the vision is not written through these tools; it is written in the vision builder, which open_vision_builder links to.
get_item
ChatGPTReads one to-do or issue, wherever it lives: its name, description, type, status, completion date, due date and its parent when it sits under another, plus its assignees (the people it is on) and its children (the to-dos and issues directly under it), each with its own status, exactly as ResultKit's detail read reports them, and the labels it carries that you may see. Put a label on or take one off with add_label and remove_label. It works on any to-do or issue you can open, including one the other person in your 1-on-1 shared onto it.
get_page
ChatGPTReads one page, as HTML or markdown. It is one page of a team's wiki: its title, body, parent page, position among its siblings, and whether the caller may edit it, delete it, or manage its permissions. The body comes back as HTML by default; set markdown to true for markdown instead. Use list_pages to discover page ids.
get_result_update
ChatGPTReads one person's result update for a day; yours by default. A result update is a person's daily update in four sections — Done, Next, Blocked and Review — each with its to-dos and issues, notes and attachments, plus whether it has been submitted. Reading yours starts the day's result update: it creates an empty result update for that date when you have none. Defaults to today in your own timezone, and takes YYYY-MM-DD or "today". To read a teammate's, pass user_id and team_id — the team it was shared with — and a literal YYYY-MM-DD date: "today" is not accepted for a teammate's, because the endpoint behind it has no "today" to resolve. A teammate's answer holds only the to-dos and issues its author shared with that team, and also says which team it was shared with (shared_team_id). A result update not shared with that team, or from a person who is not on it, reads as not found — the same answer as a day nothing was filed. Use list_result_updates for a team's whole shared feed.
get_seat
ChatGPTReads one seat. It carries the seat's owner, its accountabilities, its notes, the Measurables, 1-Year Goals and Rocks aligned to it, its links and documents, its parent seat, and its direct reports. Any member or admin of the seat's team can read it. Use list_seats for the whole chart at once.
get_team
ChatGPTReads one team and its members. It returns the team's description, its framework setting, its member list — each member's name, role (admin or member) and user_id, with a pending invitation marked — and its sub-teams. This is the only place to find a teammate's user_id, which change_member_role and list_seats (scope 'individual') need. The framework (EOS, OKR, 4DX, etc.) controls what terminology is used for goals, meetings, and scorecards within that team.
get_vision_canvas
ChatGPTReads the 3-Year Vision Canvas: five rows of prompts with the team's answers. The rows come back in this order: Financials, Employees, Customers, Products + Services and Press. Each row holds four prompts, and each prompt carries its label, its hint and the team's answer, null when unanswered. exists is false until the team has saved a canvas, and then every answer is null: say so. team_id says whose: the organization's top-level team gives the whole organization's, and any other team gives that team's own. A team set to inherit shows the vision of the team above it, and the answer says so (isInheritingParentVision, parentTeamId, visionTeamId). Show the rows in order with the answers that are set, and leave out what is not. Text can carry simple HTML formatting. The 3-Year Picture is read with get_3_year_vision, and the rest of the V/TO with get_vision_components and get_business_plan. Read-only: the vision is not written through these tools; it is written in the vision builder, which open_vision_builder links to.
get_vision_components
ChatGPTReads Core Values, Core Focus, 10-Year Target and Marketing Strategy, for the whole organization or one team. team_id says whose: the organization's top-level team gives the whole organization's, and any other team gives that team's own. A team set to inherit shows the vision of the team above it, and the answer says so (isInheritingParentVision, parentTeamId, visionTeamId). The answer carries coreValues (each with a name and a description), coreFocus (purpose and niche), tenYearTarget (its text) and marketingStrategy (target market, uniques, proven process and guarantee). A part nobody has filled in comes back empty or null, which is an answer, not an error: show what is set and leave out what is not. Text can carry simple HTML formatting. The 3-Year Picture is read with get_3_year_vision, the 3-Year Vision Canvas with get_vision_canvas, and the 1-Year Plan and the quarterly plans with get_business_plan. Read-only: the vision is not written through these tools; it is written in the vision builder, which open_vision_builder links to.
guide
ChatGPTHow to work in any one area of ResultKit: which tools to call, in what order, and which ids each needs. ALWAYS call it with what the person wants, in their words, before the first action in an area, because that action usually needs an id another tool returns. It answers with the matching area's guide, or with the list of areas when no single area matches.
inbox
ChatGPTReads what others handed to you. This is the Assigned to Me tab of My Work: every open to-do and issue another person put on you, each with who handed it to you and when, its due date, whether you have accepted it and whether you flagged it blocked. Work you made for yourself is never in it, and neither are finished work and parked work. It reads the whole list in one answer and takes no arguments. Read-only, and personal: it answers your own inbox and nobody else's.
issues
ChatGPTLists a team's issues, short-term by default, each with the to-do that resolves it and that to-do's status. list is short-term (the issues on the team's Level 10, the default), long-term (the team's long-term list) or both. It lists open issues; a solved issue is done and leaves the list. Each issue carries resolving_todos: none, one or several to-dos, each with its id, name, status, due date and owner — the status is the to-do's own, as it stands now. Long-term issues are never on the Level 10, so do not read them through L10_todos_issues. Add an issue with add_L10_issue (on the Level 10) or add_long_term_issue, and switch one between short-term and long-term with change_issue_type. To take an issue off the long-term list and make it a team's issue on the Level 10, use place_on_L10 with section issues. Mark an issue done with mark_done, like any other to-do or issue.
list_1on1_section
ChatGPTReads one section, filtered: the To-Dos, Issues or Done of a 1-on-1, chosen with section (todos, issues or done). To-Dos and Issues take q to keep only those whose name contains the text. Done answers the completed to-dos and issues, newest first, for the last 10 days by default; pass start_date and end_date together for a specific window of completion dates, or show_all to drop the window and answer every one the 1-on-1 has ever had. q is refused with done, and the dates and show_all with todos and issues, rather than ignored. To read all three sections at once use list_1on1_todos_issues.
list_1on1_todos_issues
ChatGPTReads all three sections: To-Dos, Issues, Done. Answers every to-do and issue on a 1-on-1 in one list, including archived ones and completed ones of any date: this read has no archived filter of its own and no date window (get_1on1 shows only the last 10 days of Done). Each row's status says its section: active is a To-Do, blocked is an Issue, realized is Done. q keeps only those whose name contains the text. To read one section, or Done for a window of dates, use list_1on1_section. Reads only: to move a to-do or issue to another section use move_on_1on1, to mark one done use mark_done, and to edit one use update_item.
list_1on1s
ChatGPTReads your 1-on-1s, optionally filtered by a team or organization. A 1-on-1 is one shared page for two people, usually a manager and a report: their to-dos and issues, their shared notes, and the Rocks and Measurables aligned to it. Answers the 1-on-1s the caller is one of the two people in, plus any they were added to as an assistant; no other role puts a 1-on-1 in this list. team_id only narrows which show: it keeps the 1-on-1s where both people are members of that team. organization_id keeps the 1-on-1s where both people belong to that organization: the company, meaning its top-level team and every team beneath it. If both are given, team_id wins. A 1-on-1 the caller only assists is listed whichever is given. Omit both to answer every 1-on-1 the caller is part of (the default). No tool creates a 1-on-1; it must already exist. Use get_1on1 to open one.
list_L10_section
ChatGPTReads one section of the Level 10, with search, owner filter and paging. A team that does not run EOS calls the Level 10 its Weekly board. section takes todos (or next), done, issues (or blocked) or parked (the parking lot); any other value is an error rather than an empty answer. Use L10_todos_issues to read all four sections at once. Long-term issues are never on the Level 10 — read them with issues.
list_activity
ChatGPTReads a team's history — who was added, removed, or had their role changed, by whom, and when — newest first. Any member of the team can read it. Returns page 1 with 100 entries unless page and per_page say otherwise; 100 is also the largest page available. This is membership history only; it does not cover 1-Year Goals, Rocks, Level 10s, to-dos, or issues.
list_goals
ChatGPTReads 1-Year Goals, personal or a team's. Give team_id to read that team's 1-Year Goals; leave it out to read your own: the personal 1-Year Goals you set for yourself plus the company 1-Year Goals assigned to you, across every team. 1-Year Goals only: a Rock is never in this answer, so read Rocks with list_rocks. Each 1-Year Goal comes back with its id, name, description, status, type, due date (achieve_by), progress color, whether the whole team can see it, its assignees and its creator. Defaults to the current year; pass year (e.g. 2027) to read another. A personal 1-Year Goal is read here only: it cannot be created or changed through the connector. A team 1-Year Goal's id is what update_goal and archive_goal take as goal_id, and what create_rock and align_rock take as parent_id.
list_headlines
ChatGPTList active headlines for a team using the EOS framework. Headlines are notable updates or kudos shared in the weekly meeting's Good News/Segue section — good news, accomplishments, and team highlights. A headline stays active until its expiration date, or for 7 days after creation when it has none. Only available for EOS teams. The answer is already formatted prose — relay it as it is. It shows each Headline's text without an id, so update_headline and archive_headline work only on a Headline that create_headline returned in this chat.
list_labels
ChatGPTReads the labels you can use, by kind: your personal labels (yours alone; nobody else sees them), the team's own labels, the organization labels a team above shares down to it (named with the team they come from), and a project's labels when you name a project. Locked and shared labels are marked. Give team_id, or project_id for a project (its team's labels come with it). Create, rename, recolor, share or delete one with create_label, update_label and delete_label; put one on or take it off with add_label and remove_label.
list_measurables
ChatGPTReads a team's or a person's Measurables with their weekly values for the year. Give team_id to read a team's Scorecard, or user_id to read one person's own Measurables — never both. A team's Measurable comes back with its weekly history slots (one slot per Monday of the year), its target, its owner, and what the caller may do to it; for this week's number against target, read the current week's slot beside the target. Monthly values are stored separately and do not appear in the weekly slots. A person's Measurables are the ones that belong to that person, not the ones they own on a team's Scorecard (read those with team_id and owner_id). Each comes back with its goal and its values for the year, as their profile lists them; numbers recorded with record_measurable_value are weekly history, which that read does not include. The person must share an organization with you (your own id always works). Defaults to the current year and to non-archived Measurables only; include_archived=true also returns the archived ones. owner_id narrows a team's Scorecard to one owner and cannot be combined with user_id. Its ids are what update_measurable, archive_measurable, record_measurable_value and record_measurable_note take.
list_pages
ChatGPTReads the pages of the organization or of one team, as a flat list. team_id says whose pages: the organization's top-level team gives the organization's pages, and any other team gives that team's own wiki. Each page carries its title, body, parent_id and position, so build the page tree yourself from this one call; each also says whether the caller may edit or delete it. Pages the caller has no right to see are left out of the answer rather than redacted. To read a single page by id, use get_page.
list_result_updates
ChatGPTReads the result updates shared with a team, newest date first. Only result updates that have been submitted AND shared with the team appear — a teammate's unsubmitted or unshared result update is not in this feed. Use get_result_update, with user_id, team_id and a date, for one person's result update on one day.
list_rocks
ChatGPTReads Rocks, personal or a team's, each with its Milestones. Give team_id to read that team's Rocks; leave it out to read your own: the personal Rocks you set for yourself plus the Rocks assigned to you, across every team. Each Rock comes back with its Milestones inside it (the name, status and due date of each), and there is no separate read for Milestones. A Rock is a 90-day priority: what EOS calls a Rock, and what other frameworks call an Objective, WIG, Method, or Must Win Battle. Defaults to the current quarter only: if a Rock you expect is missing, say so and pass year and quarter to read another quarter; there is no all-quarters option. For a team, a Rock that persists from an earlier quarter is included while it is still active. parent_id narrows a team's Rocks to the ones aligned to one 1-Year Goal (get its id with list_goals), and cannot be used without team_id. A Rock's id is what update_rock, archive_rock and align_rock take as rock_id and what create_milestone takes as parent_id; a Milestone's id is what update_milestone, archive_milestone and align_milestone take as milestone_id.
list_seats
ChatGPTReads the Accountability Chart for the whole organization, one team, or one individual. The organization and team reads answer a recursive tree of seats; the individual read answers a flat list of the seats that person holds. Every seat carries its owner, its accountabilities, its aligned Measurables, 1-Year Goals and Rocks, its links and documents, and whether you may edit it. Archived seats are left out by default. If the chart is empty and the team is the top-level team of its organization and EOS or OKR, the framework's starting hierarchy is created first (EOS: Visionary, then Integrator, then Sales/Marketing, Operations and Finance; OKR: CEO, then COO and President). A sub-team never gets one: reading a sub-team that owns no seats answers an empty list and creates nothing. The chart is the EOS Accountability Chart, and the org chart of roles in OKR, 4DX, V2MOM and SRT teams.
list_teams
ChatGPTReads the teams (Groups) visible to the user, exactly as the documented GET /teams read reports them: teams they are a member of, plus teams they founded or administer without being a member (those rows are marked as such). Takes no arguments. Archived teams are excluded, and muted teams are filtered out (the user's default team always stays). Teams form a hierarchy: the company is the top-level team, and its internal teams nest beneath it; together they are the organization. Each team has its own 1-Year Goals, Rocks, Scorecard, and Level 10.
list_work_done
ChatGPTReads what you finished, today by default: your own plan check-offs plus the to-dos on you whose own status is done, wherever they were marked done, most recent first. With no start or end, it answers for today, in your own timezone — no hidden lookback. Pass start and end (YYYY-MM-DD, both inclusive) for a period. Each entry names the to-do, the date it was finished in your own timezone, and the custom column it currently sits in on the Custom view (null when it sits in none). The same to-do finished on two different days counts twice, because a completion is per day. Optional filters follow the My Work controls and only ever narrow your own completions. Read-only, and personal: it answers your own work and nobody else's. For a question about what you finished, use this, not sequence.
mark_done
ChatGPTMarks a to-do or issue done and logs a result update. It never reopens: to reopen a to-do or issue, move it back with move_on_L10 or move_on_1on1. The entry goes in the Done section of your result update for today, once. Done is done everywhere, so marking it done also checks it off the day plan it is on (unless it recurs), and there is no separate check-off. It works on any to-do or issue you can change, wherever it lives, including one the other person in your 1-on-1 shared onto it. It marks a Milestone done the same way: give the Milestone's id, which list_rocks returns, and you must be able to edit that Milestone.
move_on_1on1
ChatGPTMoves a to-do or issue already on the 1-on-1 to a different section: To-Dos, Issues or Done, chosen with section (todos, issues or done). A section is the to-do's or issue's own status, so moving it changes it everywhere it appears, not only on this 1-on-1: moving to Done marks it done and logs it in the caller's result update, and moving a completed one back to todos reopens it. It has to be on the 1-on-1 already — one that is not answers as not found — and the caller needs the right to edit it, the same as with update_item. To put one that is not on the 1-on-1 yet use place_on_1on1, to take one off use remove_from_1on1, and to edit one use update_item.
move_on_L10
ChatGPTMoves a to-do or issue already on the Level 10 to a different section. section is todos (or next), done, issues (or blocked) or parked (the parking lot). Moving to done records the completion in your daily result update; moving into To-Dos or Parked tags the name with #next or #parkinglot, which is expected. To put a to-do or issue on the Level 10 in the first place, use place_on_L10 — this tool refuses one that is not there. To mark one done, use mark_done; to reopen a done one, move it back with this tool. To change a to-do or issue's status without moving it, use update_item.
move_seat
ChatGPTMoves a seat under a new parent, changing who it reports to on the Accountability Chart. Moving does not change who holds the seat: to hand it to a new owner, use update_seat. A new owner takes over the seat's Goals, Rocks and Measurables. The move is validated before it lands: a seat cannot be moved under itself or under one of its own descendants, the root seat cannot be moved, the new parent must be in the same organization, and framework rules hold (an EOS Visionary or an OKR CEO stays at the root). Only the parent changes: no other field of the seat is touched.
move_to_custom_column
ChatGPTMoves a to-do into one of your custom columns. These are the columns of the Custom view in My Work. Say which to-do (todo) and which column, by its name (column, not case-sensitive; if two of your columns share a name, the leftmost). The to-do must already be on today's plan: one that is not is refused in words and not added, so put it there first with attach_to_work_plan. It lands at the bottom of the column and leaves the column it sat in, since a to-do sits in one column at a time; nothing else about it changes, so its name, due date, labels and whether it is done stay as they were. A column you do not have, one that belongs to somebody else included, is refused in words naming the columns you do have, and no column is created. Moving a to-do into the column it already sits in changes nothing and says so. A to-do that does not exist and one you may not see get the same answer. The column it sat in before is not kept. To-do ids come from custom_columns, from reads that list to-dos (team, inbox, outbox, L10_todos_issues, list_L10_section, project_columns, list_1on1_todos_issues), get_item, or from the answer add_to_work_plan gave; sequence shows order but not ids. Backed by the documented REST route that moves a to-do into one of your custom columns (see https://api.resultkit.ai/api-docs/v2).
open_vision_builder
ChatGPTOpens the ResultKit vision builder page. It returns the link to that page in the app, for the person to open; it opens nothing itself, reads no vision and writes nothing, and the vision is built in that page, never through these tools. The builder asks a few questions about the future the team sees, then drafts the vision for the person to edit or approve. It opens on the team the person has selected in ResultKit, and this link does not name a team, so tell the person to select the right team there first.
outbox
ChatGPTReads what you handed off. This is the Assigned by Me tab of My Work: the to-dos you assigned to other people, each with who holds it, its status, its due date, the parent it sits under and its last three updates. A to-do you handed off shows for 30 days after it is finished. It returns one page at a time: the first 50 unless limit says otherwise; pass offset to read the next page, and keep going while has_more is true. total counts hand-offs, not to-dos: a to-do you handed to two people counts twice, so never work out whether more remain from total; use has_more. Read-only, and personal: it answers your own hand-offs and nobody else's.
place_on_1on1
ChatGPTPuts an existing to-do or issue on the 1-on-1, so both people can open, comment on, and edit it. It lands in the section its status puts it in: an issue in Issues, a completed one in Done, any other in To-Dos; use move_on_1on1 to change that. The caller must already be able to edit the to-do or issue — sharing it is what hands the other person that right — and one they cannot edit answers the same as one that does not exist. Use add_1on1_todo or add_1on1_issue for a brand-new one, and remove_from_1on1 to take one back off. Calling it twice changes nothing the second time. To mark it done use mark_done, and to edit it use update_item.
place_on_L10
ChatGPTPuts an existing to-do or issue onto a team's Level 10, in a section. section is todos (or next) or issues (or blocked): a to-do or issue placed in To-Dos becomes an open to-do and one placed in Issues becomes an open short-term issue, so a done one is reopened and a long-term issue placed in Issues leaves the long-term list. team_id is the team whose Level 10 it goes on; leave it out to use the team the to-do or issue already belongs to — one that belongs to no team needs team_id. You must be able to edit the to-do or issue and see the team. Placing it does not take it out of anywhere else it lives. To move one that is already on the Level 10 to Done or Parked, use move_on_L10. To create a new to-do or issue instead, use add_L10_todo or add_L10_issue; to take one off the Level 10, use remove_from_L10.
place_on_result_update
ChatGPTPuts an existing to-do or issue in a section of your own result update, and optionally sets that section's notes and attachments. Placing it in a section also sets its status: done completes it, next and blocked mark it accordingly. This is the only tool that sets a section's notes or attachments. attachment_ids REPLACES the section's whole attachment list rather than adding to it, and notes are stored as plain text — any markup is stripped. To create a new to-do or issue instead, use add_result_update_todo or add_result_update_issue. Defaults to today's result update.
project_columns
ChatGPTReads one project's columns and the work in each. A whole board reads in one call — the columns come back as the top-level rows, and each column's items ride along inside it. A flat-checklist project has no columns, so what comes back at the top level is its items. Use projects to find a project's id. To add an item to a column, use create_item with parent_id set to the column id.
projects
ChatGPTReads a team's projects, each with its progress. Progress is how much is done, blocked or overdue: each project carries its percent complete, how much work it holds, and how much of that is done, blocked, overdue, or still active. Answers the team's active projects by default; done, archived, draft, blocked, and parked projects are left out until you ask for them by status. Use project_columns to read one project's columns and the work in each.
record_measurable_note
ChatGPTSets or clears the note beside a week's number on a Measurable of a team's Scorecard. Use it to record the reason behind a miss. Pass null to clear that week's note. A note is at most 255 characters. The date defaults to the current week, and any date given is moved back to the Monday that starts its week. Access here is narrower than for the number itself: being a member of the team is enough to record a value with record_measurable_value, but the note needs edit rights on the Measurable, not just membership.
record_measurable_value
ChatGPTRecords a Measurable's value for a week or a month on a team's Scorecard. value is a string that reads as a number ("42", not the number 42). period defaults to week, and the date defaults to the current week (or the current month when period is month). Any member of the Measurable's team may record a value. Three guards run before anything is written: a value that does not read as a number is refused; a roll-up Measurable is refused, because its number is computed from its source Measurables rather than typed in; and a weekly date is moved back to the Monday that starts its week, so a mid-week date lands in the week you meant — say which Monday it landed on. For the note beside the number, use record_measurable_note, which is not open to every team member.
remove_from_1on1
ChatGPTTakes a to-do or issue off the 1-on-1; it is not deleted. It leaves the 1-on-1 only — the to-do or issue goes on living wherever else it belongs, with the status it has. Removing one that is already off the 1-on-1 succeeds and changes nothing. To put one back use place_on_1on1.
remove_from_L10
ChatGPTTakes a to-do or issue off the Level 10 without deleting it. It keeps its name, status, due date, owner and history — it simply stops appearing on that team's Level 10, and stays visible everywhere else it lives. To put it back, use place_on_L10.
remove_from_result_update
ChatGPTTakes a to-do or issue out of a section of your own result update; it is not deleted. It keeps whatever status it has — only its place in the result update goes away. Defaults to today's result update.
remove_from_work_plan
ChatGPTTakes a to-do off the plan; it is not deleted. The to-do itself is not deleted and not archived — it stays among your to-dos and can be put back with attach_to_work_plan. Defaults to today's plan when date is omitted. To mark the to-do done instead of taking it off the plan, use mark_done.
remove_label
ChatGPTTakes one label off a to-do, an issue, a 1-Year Goal or a page, by the label's name, and leaves every other label on it as it was. The rights are add_label's. A label the target does not carry changes nothing. Answers with the target and the labels it still carries.
remove_seat_link
ChatGPTRemove a reference link from a seat. The link is deleted outright, not archived, so it cannot be restored afterwards.
resequence_my_work
ChatGPTChanges the order of your plan for today. It moves one to-do on today's plan to the top, to the bottom, or to the place right after another to-do on the plan; every other to-do keeps its order, and none is added, dropped or marked done. Say where with to ('top' or 'bottom') or with after (the id of the to-do it should sit right after) — one of the two. The to-do must already be on today's plan: one that is not is refused in words and is not added, so put it there first with attach_to_work_plan. Only your own plan for today can be reordered; the tool takes no person and no date. Moving a to-do to where it already sits changes nothing and says so. A to-do that does not exist and one you may not see get the same answer. The plan's previous order is not kept. To-do ids come from the reads that list to-dos (team, inbox, outbox, L10_todos_issues, list_L10_section, project_columns, list_1on1_todos_issues), from get_item, or from a create result such as the answer add_to_work_plan gave; sequence shows the order but not the ids. Backed by the documented REST route that sets the order of today's plan (see https://api.resultkit.ai/api-docs/v2).
resequence_on_1on1
ChatGPTChanges the order of one list on a 1-on-1: its To-Dos or its Issues. It moves one to-do or issue to the top, to the bottom, or to the place right after another one in the same list; every other one keeps its order, and none is added, removed, marked done or moved to another section. Say where with to ('top' or 'bottom') or with after (the id of the to-do or issue it should sit right after) — one of the two. You do not name the list: it is the one the to-do or issue is in (an issue is in Issues, any other open one in To-Dos), and after has to be in that same list; one in the other list, or not on the 1-on-1, is refused in words. A completed one is refused too: Done is read newest first by completion date and has no order to set. The to-do or issue has to be on the 1-on-1 already: one that is not, one that does not exist and one you may not see get the same answer. You need the right to edit the 1-on-1. Moving one to where it already sits changes nothing and says so. The list's previous order is not kept. Ids come from list_1on1_todos_issues, list_1on1_section or get_1on1. To move one to another section use move_on_1on1; to put one on the 1-on-1 use place_on_1on1. Backed by the documented REST route POST /api/v2/1-on-1/{id}/set-positions (see https://api.resultkit.ai/api-docs/v2).
restore_page
ChatGPTRestores a deleted page and every page beneath it. It brings back what delete_page removed from a team's wiki: the page and all of its sub-pages. Requires the page's author role or team admin, the same as delete_page. A deleted page no longer shows in list_pages or get_page, so restore it by the id it had when it was deleted.
restore_seat
ChatGPTRestores one seat. It brings one archived seat back to the Accountability Chart. Only a team admin can restore a seat — seat owners cannot, unlike every other edit here. The restore covers that seat alone: its archived descendants stay archived and each has to be restored on its own.
save_1on1_notes
ChatGPTReplaces the notes in full. This overwrites the whole shared note of the 1-on-1 with the text given — anything previously there is gone, and it never appends. To add to the notes rather than start over, read the current ones with get_1on1 first and send them back with the addition included. HTML is sanitized before it is stored.
sequence
ChatGPTReads your plan for today or another day, in order. The plan is the prioritized list of to-dos you intend to work on for a given day, exactly as the Sequencer view of My Work reports it. Each entry shows the to-do's name and whether it is done. Defaults to today (creating today's plan if it doesn't exist yet); pass a date for a past or future day's plan, which is only read, never created. It does not show to-do ids, so to act on a to-do you read here, get its id from the reads that list to-dos (team, inbox, outbox, L10_todos_issues, list_L10_section, project_columns, list_1on1_todos_issues), from get_item, or from a create result such as the answer add_to_work_plan gave. For your custom columns use custom_columns, and for what you have finished use list_work_done.
submit_result_update
ChatGPTSubmits your own result update for a date, and shares it with a team if you name one. Pass team_id to name the team; without team_id it is submitted and shared with no one. Done and Next must each hold at least one to-do or issue or the submit is refused. A share covers the whole result update, not one section: this tool cannot pick which to-dos and issues the team sees, and any you already hid from that team in the app stay hidden. Submitting an already-submitted result update changes nothing about the submit itself; naming a team still shares it with that team. Defaults to today.
team
ChatGPTReads everything open on a team, whoever holds it. Give team_id. This is the Team tab of My Work: every open to-do and issue that belongs to the team, sits in one of its Projects, or is on a 1-on-1 between two of its people, each row with who it is on, its due date and where it sits. Finished and parked work is not in it. It also lists the team's people with how many open to-dos and issues each holds (roster) and the team's open total (total). It reads the whole list in one answer and takes no filters. Read-only. A team you cannot see and a team that does not exist answer with the same sentence.
unalign_seat_goal
ChatGPTEnds a seat's accountability for a 1-Year Goal or a Rock — one tool covers both. The goal itself is untouched — only the seat's accountability for it goes away, leaving it aligned to no seat. Errors if the goal is not currently aligned to this seat.
unalign_seat_measurable
ChatGPTEnds a seat's accountability for a Measurable. The Measurable itself is untouched — only the seat's accountability for it goes away, leaving it aligned to no seat. Errors if the Measurable is not currently aligned to this seat.
update_goal
ChatGPTUpdate an existing 1-Year Goal. Supports partial updates to name, description, target date, state, assignees, visibility, and progress color. To mark a 1-Year Goal done, set current_state to "realized"; setting it back to "active" reopens it.
update_headline
ChatGPTUpdate an existing headline's text and/or its expiration date. At least one of text or expires_at must be given; anything left out is unchanged. Only the headline's creator or a team admin may update it. A Headline's text carries no id, so this works only on a Headline that create_headline returned in this chat.
update_item
ChatGPTChanges a to-do or issue's name, description, due date or status. Setting status to done marks it done and logs a result update, and setting it to not_started reopens it; completing or reopening also syncs its check-off on your day plan, exactly as the documented update does. status is one of not_started, next, parked, blocked, done or archived ('draft' is read-only and rejected). To mark one done on its own, mark_done does the same. It works on any to-do or issue you can change, wherever it lives, including one the other person in your 1-on-1 shared onto it.
update_label
ChatGPTRenames or recolors a label, or shares a team label with the teams below its team or stops sharing it. A personal label is changed by its owner, a team label by an admin of the team that owns it, a project label by an admin of the project. An organization label inherited from a team above is changed only on the team that owns it. A locked label cannot be renamed or recolored; it is unlocked on the team page's Labels, Tags & Stages tab. Name the label by its name; give team_id or project_id for where it is.
update_measurable
ChatGPTChanges a Measurable on a team's Scorecard: name, description, unit, direction, target value, target period, aggregation type, chart type, owner or notes. Only the fields you pass change. A change to the name, unit, direction, target value, target period, aggregation type or owner is recorded in the Measurable's history, old value to new, with who made it and when. Pass null for chart_type, owner_id or notes to clear them. Reassigning the owner to somebody else requires team-admin rights or being the Measurable's current owner, and the new owner must be a member of the team. List first with list_measurables and match by name to get the id. Use archive_measurable to take a Measurable off the Scorecard.
update_milestone
ChatGPTUpdate an existing Milestone. Supports partial updates to name, description, due date, status, assignees, and parent Rock alignment. To reopen a done Milestone, set status to "active".
update_page
ChatGPTChanges a page's title, body, parent or position. It updates one page of a team's wiki: rename it (title), rewrite its body, move it under a different parent (parent_id), or reorder it among its siblings (position). A partial update — omit any field you are not changing and it is left exactly as it was; body null clears the body, and parent_id null moves the page to the top level. A locked page refuses changes to its title and body. Requires edit rights on the page: its author, editor or contributor role, or team admin. Answers with the saved page's identity and NOT with its body, so the answer is the same size whatever the page holds; call get_page to confirm what was saved and to read its content. Locking and unlocking a page and its permissions are set in the app; no tool here does them. Put a label on the page or take one off with add_label and remove_label. Backed by the documented REST route PATCH /api/v2/teams/{id}/pages/{pageId} (see https://api.resultkit.ai/api-docs/v2).
update_rock
ChatGPTUpdate an existing Rock. Supports partial updates to name, description, target date, state, assignees, visibility, progress color, and parent alignment. To mark a team Rock done, set current_state to "realized"; setting it back to "active" reopens it. A personal (no-team) Rock takes only "on_track" or "off_track", so it cannot be marked done here.
update_seat
ChatGPTUpdates a seat on the Accountability Chart: its name, owner, notes, accountabilities, or the team it represents. A new owner takes over the seat's Goals, Rocks and Measurables. Changing seat_owner_id CASCADES: every Measurable, 1-Year Goal and Rock aligned to this seat is reassigned to the new owner along with the seat. Who a seat reports to is changed with move_seat.
update_seat_link
ChatGPTUpdate a seat link's url or title. Passing a null or empty title resets the title to the link's url. The link must already belong to this seat. Backed by the documented REST route PATCH /api/v2/seats/{id}/links/{link_id} (see https://api.resultkit.ai/api-docs/v2).
L10_todos_issues
Claudeadd_1on1_issue
Claudeadd_1on1_todo
Claudeadd_L10_issue
Claudeadd_L10_todo
Claudeadd_long_term_issue
Claudeadd_result_update_attachment
Claudeadd_result_update_issue
Claudeadd_result_update_todo
Claudeadd_seat_link
Claudeadd_to_work_plan
Claudealign_milestone
Claudealign_rock
Claudealign_seat_goal
Claudealign_seat_measurable
Claudearchive_goal
Claudearchive_headline
Claudearchive_measurable
Claudearchive_milestone
Claudearchive_rock
Claudearchive_seat
Claudeattach_to_work_plan
Claudechange_issue_type
Claudechange_member_role
Claudecreate_goal
Claudecreate_headline
Claudecreate_item
Claudecreate_measurable
Claudecreate_milestone
Claudecreate_page
Claudecreate_project
Claudecreate_rock
Claudecreate_seat
Claudecustom_columns
Claudedelete_page
Claudeget_1on1
Claudeget_3_year_vision
Claudeget_business_plan
Claudeget_item
Claudeget_page
Claudeget_result_update
Claudeget_seat
Claudeget_team
Claudeget_vision_canvas
Claudeget_vision_components
Claudeguide
Claudeinbox
Claudeissues
Claudelist_1on1_section
Claudelist_1on1_todos_issues
Claudelist_1on1s
Claudelist_L10_section
Claudelist_activity
Claudelist_goals
Claudelist_headlines
Claudelist_measurables
Claudelist_pages
Claudelist_result_updates
Claudelist_rocks
Claudelist_seats
Claudelist_teams
Claudelist_work_done
Claudemark_done
Claudemove_on_1on1
Claudemove_on_L10
Claudemove_seat
Claudeopen_vision_builder
Claudeoutbox
Claudeplace_on_1on1
Claudeplace_on_L10
Claudeplace_on_result_update
Claudeproject_columns
Claudeprojects
Clauderecord_measurable_note
Clauderecord_measurable_value
Clauderemove_from_1on1
Clauderemove_from_L10
Clauderemove_from_result_update
Clauderemove_from_work_plan
Clauderemove_seat_link
Clauderestore_page
Clauderestore_seat
Claudesave_1on1_notes
Claudesequence
Claudesubmit_result_update
Claudeteam
Claudeunalign_seat_goal
Claudeunalign_seat_measurable
Claudeupdate_goal
Claudeupdate_headline
Claudeupdate_item
Claudeupdate_measurable
Claudeupdate_milestone
Claudeupdate_page
Claudeupdate_rock
Claudeupdate_seat
Claudeupdate_seat_link
Claude