此 MCP 可以做什么
Combines customer records, support conversations, feedback, product analytics, roadmaps, tasks, experiments, releases, and retention reporting.
功能
工具
71
工具
add_note
Add Internal Note
Add an INTERNAL note to a support conversation — visible only to your team, never sent to the end-user — and return the result. A write. Use it to record context or hand off; resolve conversation_id via list_conversations. conversation_id and body are required. For a public reply use reply_to_conversation instead.
输入模式
{'type': 'object', 'examples': [{'body': "Repro'd — linking to feat_sso.", 'conversation_id': 'conv_42'}], 'required': ['conversation_id', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Internal note text, teammates-only (required).'}, 'conversation_id': {'type': 'string', 'description': 'Conversation id to note on, from list_conversations (required).'}}}
analyze_funnel
Conversion Funnel
Build a conversion funnel from the product's own events: distinct users per step, step-to-step conversion %, and drop-off, evaluated in the exact order you pass. Needs product-analytics events flowing; returns empty counts when none match. Pass `steps` as an ordered list of 2+ event names — call it with NO steps first to get the menu of available event names rather than guessing them. Optional product_id and window_days (default 30, valid 1–365). Pairs with analyze_paths to see where the drop-offs go.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'steps': ['signup', 'activated', 'subscribed']}], 'properties': {'steps': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Ordered list of 2+ event names forming the funnel; omit to get the menu of available event names first.'}, 'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}, 'window_days': {'type': 'number', 'default': 30, 'minimum': 1, 'description': 'Lookback window in days (optional; default 30).'}}}
输出模式
{'type': 'object', 'required': ['steps'], 'properties': {'steps': {'type': 'array', 'items': {'type': 'object', 'properties': {'name': {'type': 'string'}, 'users': {'type': 'number'}, 'dropoff': {'type': 'number'}, 'mrrCents': {'type': 'number'}, 'convFromPrev': {'type': 'number'}, 'convFromStart': {'type': 'number'}}, 'additionalProperties': True}}, 'currency': {'type': 'string'}, 'completed': {'type': 'number'}, 'mrrTracked': {'type': 'boolean'}, 'windowDays': {'type': 'number'}, 'overallConv': {'type': 'number'}, 'productName': {'type': 'string'}, 'completedMrr': {'type': 'number'}, 'totalEntered': {'type': 'number'}, 'totalEnteredMrr': {'type': 'number'}}, 'additionalProperties': True}
analyze_nps
NPS (revenue-weighted)
NPS for the product: the standard −100…100 score AND revenue-weighted NPS (each respondent weighted by their account MRR), plus detractor accounts ranked by MRR-at-risk (highest first). Surfaces when your biggest customers are the unhappy ones even if the headline looks fine. Computed deterministically off survey responses inside `window_days` (default 90, valid 1–365); returns an empty result when none fall in the window. product_id optional (primary product when omitted). Quantify sentiment after get_product_brain, then dig into a detractor with get_customer_360.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'window_days': 90}], 'properties': {'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}, 'window_days': {'type': 'number', 'default': 90, 'minimum': 1, 'description': 'Lookback window in days (optional; default 90, i.e. the last quarter).'}}}
analyze_nrr
Net Revenue Retention
Net Revenue Retention (revenue-weighted) next to logo retention (count-weighted), the expansion/contraction/churn split, and the accounts that lost the most MRR (ranked, highest loss first). The divergence is the point: '92% of logos but 78% of revenue' means a big account churned. Computed deterministically off subscription movements inside `window_days` (default 90, valid 1–365); empty when none fall in the window. Quantify revenue health, then follow the top-losing accounts into get_customer_360.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'window_days': 90}], 'properties': {'window_days': {'type': 'number', 'default': 90, 'minimum': 1, 'description': 'Lookback window in days (optional; default 90, i.e. the last quarter).'}}}
analyze_paths
User Path Flow
Trace what users do AFTER a start event — the journey flow (Sankey) from the product's own events. Returns the next-step transitions ranked by user count (most common first), empty when no events match. Pass `start` to anchor on an event, or omit for the most common start (call analyze_funnel with no steps to list the event names). Optional product_id and window_days (default 30, valid 1–365).
只读
幂等
输入模式
{'type': 'object', 'examples': [{'start': 'signup'}], 'properties': {'start': {'type': 'string', 'description': 'Event name to anchor the flow on (optional; the most common start event when omitted — analyze_funnel with no steps lists the event names).'}, 'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}, 'window_days': {'type': 'number', 'description': 'Lookback window in days (optional; default 30).'}}}
cancel_booking
Cancel Booking
Cancel a scheduled booking (call/meeting) and return the result — the invitee is notified per the scheduling settings. A write. Resolve booking_id via list_bookings first; never guess it. To move it instead of cancelling, use reschedule_booking.
可访问外部资源
输入模式
{'type': 'object', 'examples': [{'booking_id': 'book_7'}], 'required': ['booking_id'], 'properties': {'booking_id': {'type': 'string', 'description': 'Booking id to cancel, from list_bookings (required).'}}}
capture_insight
Capture Insight
Write a piece of customer feedback to the spine (the agent's own hand, not just reading) and return the created insight. Fires the same insight.created webhook a manual capture does — a real side-effect, so only capture genuine signal. Resolve account_id via get_customer_360 and feature_id via list_features and tie them when known; kind='opportunity' marks a prioritisable ask. Only body is required.
输入模式
{'type': 'object', 'examples': [{'body': 'Two enterprise accounts asked for SAML this week.', 'kind': 'opportunity', 'account_id': 'acct_acme', 'feature_id': 'feat_sso'}], 'required': ['body'], 'properties': {'body': {'type': 'string', 'description': 'The verbatim feedback / insight text (the only required field).'}, 'kind': {'enum': ['insight', 'opportunity'], 'type': 'string', 'description': "'insight' = raw signal; 'opportunity' = a prioritisable ask (optional)."}, 'title': {'type': 'string', 'description': 'Short display title (optional).'}, 'account_id': {'type': 'string', 'description': "Account id it's about, from get_customer_360 (optional)."}, 'feature_id': {'type': 'string', 'description': 'Feature id to link on the spine, from list_features or pm_meta (optional).'}, 'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}}}
comment_on_task
Comment on Task
Add a comment to a task, authored as the connected member, and return the created comment. Use to record progress, a decision, or a handoff — the comment is visible to the whole org, so keep it work-relevant. Resolve the task id first with get_task or list_tasks; both id and body are required.
输入模式
{'type': 'object', 'examples': [{'id': 'task_8f3a', 'body': 'Shipped behind a flag — verifying in production.'}], 'required': ['id', 'body'], 'properties': {'id': {'type': 'string', 'description': 'Task id, from list_tasks or get_task.'}, 'body': {'type': 'string', 'description': 'Comment text; posted as the connected member and visible to the whole org.'}}}
create_decision
Log Decision
Log a decision and return it. status is 'decided' (default) | 'proposed' | 'revisit'; a 'decided' one stamps the decision time. Optionally weld it to a feature / release / objective via link_type + link_id (verified in-org). Only title is required.
输入模式
{'type': 'object', 'examples': [{'title': 'Ship SSO before mobile', 'link_id': 'feat_123', 'link_type': 'feature', 'rationale': 'Enterprise deals need it'}], 'required': ['title'], 'properties': {'title': {'type': 'string', 'description': 'The decision in a line (required).'}, 'status': {'enum': ['decided', 'proposed', 'revisit'], 'type': 'string', 'description': "Decision status (optional; default 'decided')."}, 'link_id': {'type': 'string', 'description': 'Id of the linked feature/release/objective, from list_features / list_releases / list_objectives (optional).'}, 'link_type': {'enum': ['feature', 'release', 'objective'], 'type': 'string', 'description': "What it's linked to (optional; pair with link_id)."}, 'rationale': {'type': 'string', 'description': 'Why — the reasoning (optional).'}}}
create_experiment
Create Experiment
Create a PM experiment (a Build-Measure-Learn hypothesis) and return it. state is 'hypothesis' (default) | 'build' | 'measure' | 'learn'. Only title is required. This is the PM tracker list_experiments reads, not the analytics A/B engine.
输入模式
{'type': 'object', 'examples': [{'title': 'Shorter onboarding lifts activation', 'metric': 'activation rate', 'target': '+5pp'}], 'required': ['title'], 'properties': {'state': {'enum': ['hypothesis', 'build', 'measure', 'learn'], 'type': 'string', 'description': "Build-Measure-Learn stage (optional; default 'hypothesis')."}, 'title': {'type': 'string', 'description': 'Experiment title / the hypothesis in a line (required).'}, 'metric': {'type': 'string', 'description': "The metric it moves, e.g. 'activation rate' (optional)."}, 'target': {'type': 'string', 'description': "Target change, e.g. '+5pp' (optional)."}, 'hypothesis': {'type': 'string', 'description': 'The full hypothesis (optional).'}, 'product_id': {'type': 'string', 'description': 'Product, from whoami (optional).'}}}
create_feature
Create Feature
Create a feature on the product spine and return it (id, key, name, status). The key is generated from the name; status starts 'active'. product_id defaults to the org's primary product when omitted (pass one from whoami for a multi-product org). Only name is required — create a feature here before linking tasks to it with create_task.
输入模式
{'type': 'object', 'examples': [{'name': 'SAML SSO'}], 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': "Feature name (the only required field), e.g. 'SAML SSO'."}, 'product_id': {'type': 'string', 'description': "Product to create it under, from whoami (optional; the org's primary product when omitted)."}, 'description': {'type': 'string', 'description': 'What the feature is / why it matters (optional).'}, 'objective_id': {'type': 'string', 'description': "Objective (goal) to align this feature under directly when there's no intermediate initiative, from list_objectives (optional)."}, 'initiative_id': {'type': 'string', 'description': 'Initiative to align this feature under for line-of-sight, from list_initiatives (optional).'}}}
create_idea
Create Idea
Create an idea in the backlog and return it (starts with 0 votes, status 'new'). Link the evidence it came from with insight_id (from list_insights). product_id defaults to the primary product. Only title is required. Grow it with vote_idea, then promote_idea turns the winner into a roadmap feature.
输入模式
{'type': 'object', 'examples': [{'body': 'Several accounts asked to change status on many tasks at once.', 'title': 'Bulk-edit tasks'}], 'required': ['title'], 'properties': {'body': {'type': 'string', 'description': 'The idea in more detail (optional).'}, 'title': {'type': 'string', 'description': "Idea title (the only required field), e.g. 'Bulk-edit tasks'."}, 'insight_id': {'type': 'string', 'description': 'Customer insight this idea came from, from list_insights (optional; welds evidence to the idea).'}, 'product_id': {'type': 'string', 'description': 'Product to scope it to, from whoami (optional; the primary product when omitted).'}}}
create_initiative
Create Initiative
Create an initiative — a strategic effort that groups features and rolls up to a goal — and return it. Link it to a goal with objective_id (from list_objectives) to build line-of-sight. status ∈ planned|active|paused|done|abandoned (default planned); timeframe is free text ('H2 2026'). product_id defaults to the primary product. Only name is required. Then align features to it via create_feature / update_feature (initiative_id).
输入模式
{'type': 'object', 'examples': [{'name': 'Win enterprise', 'timeframe': 'H2 2026', 'objective_id': 'obj_123'}], 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': "Initiative name (the only required field), e.g. 'Win enterprise'."}, 'status': {'enum': ['planned', 'active', 'paused', 'done', 'abandoned'], 'type': 'string', 'description': "Lifecycle status (optional; default 'planned')."}, 'timeframe': {'type': 'string', 'description': "Free-text timeframe, e.g. 'Q3 2026' or 'H2 2026' (optional)."}, 'product_id': {'type': 'string', 'description': 'Product to scope it to, from whoami (optional; the primary product when omitted).'}, 'description': {'type': 'string', 'description': 'What the initiative is / why it matters (optional).'}, 'objective_id': {'type': 'string', 'description': 'Goal this rolls up to, from list_objectives (optional; builds line-of-sight).'}}}
create_objective
Create Objective (OKR)
Create an objective, optionally with key results, and return it. period is free text (e.g. 'Q3 2026'); product_id and parent_id (a parent objective) are optional and verified in-org. Each key result takes name + optional unit / start_value / target_value. Only name is required.
输入模式
{'type': 'object', 'examples': [{'name': 'Reach $50k MRR', 'period': 'Q3 2026', 'key_results': [{'name': 'MRR', 'unit': 'USD', 'target_value': 50000}]}], 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': "Objective name (the only required field), e.g. 'Reach $50k MRR'."}, 'period': {'type': 'string', 'description': "Free-text period, e.g. 'Q3 2026' (optional)."}, 'parent_id': {'type': 'string', 'description': 'Parent objective id to nest under, from list_objectives (optional).'}, 'product_id': {'type': 'string', 'description': 'Product to scope it to, from whoami (optional).'}, 'description': {'type': 'string', 'description': 'Context for the objective (optional).'}, 'key_results': {'type': 'array', 'items': {'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': "Key result name, e.g. 'MRR'."}, 'unit': {'type': 'string', 'description': "Unit, e.g. 'USD' or '%' (optional)."}, 'start_value': {'type': 'number', 'description': 'Starting value (optional; default 0).'}, 'target_value': {'type': 'number', 'description': 'Target value (optional).'}}}, 'description': 'Key results to attach (optional; up to 10).'}}}
create_page
Create Page
Create a Page (in-product doc / PRD on the spine) and return it (id, title). `body` is plain text — blank-line-separated blocks become paragraphs; omit it for a blank page. title defaults to 'Untitled'. product_id / parent_id (a parent page) are optional and verified in-org.
输入模式
{'type': 'object', 'examples': [{'body': "Problem\n\nUsers can't self-serve SAML today.", 'title': 'PRD: SSO'}], 'properties': {'body': {'type': 'string', 'description': 'Page content as plain text; blank lines separate paragraphs (optional).'}, 'icon': {'type': 'string', 'description': 'An emoji icon for the page (optional).'}, 'title': {'type': 'string', 'description': "Page title (optional; 'Untitled' when omitted)."}, 'parent_id': {'type': 'string', 'description': 'Parent page id to nest under, from list_pages (optional).'}, 'product_id': {'type': 'string', 'description': 'Product to scope it to, from whoami (optional).'}}}
create_release
Create Release
Create a release and return it (id, version, changelog, released_at). Omit released_at for an unreleased/draft entry. product_id defaults to the org's primary product. Only version is required.
输入模式
{'type': 'object', 'examples': [{'version': 'v2.4.0', 'changelog': 'SSO + faster board', 'released_at': '2026-07-15T00:00:00Z'}], 'required': ['version'], 'properties': {'version': {'type': 'string', 'description': "Version string (required), e.g. 'v2.4.0'."}, 'changelog': {'type': 'string', 'description': 'What shipped (optional).'}, 'product_id': {'type': 'string', 'description': 'Product, from whoami (optional; the primary product when omitted).'}, 'released_at': {'type': 'string', 'description': 'Ship time, ISO 8601 (optional; omit for a draft).'}}}
create_sprint
Create Sprint
Create a sprint and return it (id, name, goal, state, dates). state is 'future' (default) or 'active'; start_date / end_date are optional ISO 8601. Only name is required. Schedule tasks into it by passing the returned sprint id as sprint_id on create_task / update_task.
输入模式
{'type': 'object', 'examples': [{'goal': 'Ship SSO', 'name': 'Sprint 12', 'state': 'active'}], 'required': ['name'], 'properties': {'goal': {'type': 'string', 'description': 'The sprint goal (optional).'}, 'name': {'type': 'string', 'description': "Sprint name (the only required field), e.g. 'Sprint 12'."}, 'state': {'enum': ['future', 'active'], 'type': 'string', 'description': "Lifecycle state (optional; default 'future')."}, 'end_date': {'type': 'string', 'description': 'End, ISO 8601 (optional).'}, 'start_date': {'type': 'string', 'description': "Start, ISO 8601 e.g. '2026-07-15T00:00:00Z' (optional)."}}}
create_task
Create Task
Create a task and return the created task. list_id defaults to the org's first list when omitted; feature_id / insight_id link it to the spine and sprint_id schedules it into a sprint. Resolve list/status/feature/insight/member ids via pm_meta and sprint_id via list_sprints — never guess them. Only title is required.
输入模式
{'type': 'object', 'examples': [{'title': 'Fix SSO redirect loop', 'priority': 'high', 'feature_id': 'feat_sso'}], 'required': ['title'], 'properties': {'title': {'type': 'string', 'description': 'Task title (the only required field).'}, 'list_id': {'type': 'string', 'description': "List to create the task on; resolve the id via pm_meta (optional; the org's first list when omitted)."}, 'priority': {'enum': ['urgent', 'high', 'normal', 'low'], 'type': 'string', 'description': 'Priority level, urgent highest (optional).'}, 'sprint_id': {'type': 'string', 'description': 'Schedule into a sprint (optional; resolve the id via list_sprints).'}, 'status_id': {'type': 'string', 'description': 'Initial status; resolve the id via pm_meta (optional).'}, 'feature_id': {'type': 'string', 'description': 'Feature id to link on the spine, from pm_meta or list_features (optional).'}, 'insight_id': {'type': 'string', 'description': 'Insight id to link on the spine, from list_insights (optional).'}, 'description': {'type': 'string', 'description': 'Task body / details (optional).'}, 'assignee_member_ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Member ids to assign, from pm_meta (optional).'}}}
delete_task
Delete Task
PERMANENTLY delete a task and return the deleted id. Irreversible — there is no undo. Cascades: the task's comments, assignees, tags, attachments, time entries, outcomes, events, relations, and its SUBTASKS are deleted with it; experiment/insight/meeting links to it are cleared. Resolve the id via list_tasks and confirm intent first — prefer update_task (e.g. move it to a done/archived status) when you only want it off the active board.
可能执行破坏性操作
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'task_123'}], 'required': ['id', 'confirm'], 'properties': {'id': {'type': 'string', 'description': 'Task id to permanently delete, from list_tasks (required).'}, 'confirm': {'enum': ['DELETE'], 'type': 'string', 'description': 'Safety gate — must be exactly "DELETE". Required so a bare task id can never trigger a permanent, cascading delete. Confirm with the human FIRST, in plain language naming the task, then pass it.'}}}
get_codebase_map
Codebase Map
The auto-generated codebase brain map for one product: a plain-language summary, the module/node/edge counts, when the map was last generated, and the labels of the modules it found. Read-only; returns the latest generated map, empty when none has been generated for the product yet. Use it to ground 'where in the code does X live?' questions and to see how the codebase splits into modules before discussing architecture or scoping engineering work. Optional product_id, from whoami; omit for the org's primary product.
只读
幂等
输入模式
{'type': 'object', 'properties': {'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}}}
get_conversation
Read Support Conversation
Read one support conversation: the visitor plus the full message thread, oldest first. Read-only. Resolve the conversation_id first with list_conversations — never guess it.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'conversation_id': 'conv_42'}], 'required': ['conversation_id'], 'properties': {'conversation_id': {'type': 'string', 'description': 'Conversation id, from list_conversations.'}}}
get_customer_360
Customer 360
Everything about ONE customer, resolved by id, email, domain, or company name: profile, subscription + MRR, how many users sit under the account, and their verbatim feedback. Read-only; returns the matched account, or an empty result when nothing matches the query. The money + people + voice join on one record — call it before answering anything about a specific account.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'query': 'acme.com'}], 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': "The account to resolve: an account id, a user's email, a company domain (e.g. 'acme.com'), or a company name."}}}
get_device_candidates
Device-Graph Identity Candidates
Clusters of ≥2 end_users seen on the same device: 'anon_bridge' (high confidence — an anonymous visitor later identified) or 'device_shared' (low confidence — review only). Read-only; returns the candidate clusters, empty when none are found. Use it to find merge targets, then act with merge_end_users.
只读
幂等
输入模式
{'type': 'object', 'properties': {}}
get_page
Read Page
Read one Page (doc / PRD) by id and return its full content. Read-only. Resolve the id first with list_pages — never guess it.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'page_12'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Page id, from list_pages.'}}}
get_pm_playbook
PM Playbook
How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
只读
幂等
输入模式
{'type': 'object', 'properties': {}}
get_product_brain
Product Brain Snapshot
A grounded snapshot of the org's product so YOU can reason about it. Returns one JSON object with: revenue + top paying accounts (ranked by MRR), web + product analytics headline metrics, the feature list, recent verbatim customer signals (newest first), and open-work counts — each block empty when that source isn't flowing yet. The time-windowed sections (revenue, cost, web + product analytics, feature usage) honour `window` (7 | 30 | 90 days, default 30). Single call, no pagination. Start here to ground, then go deeper with the dedicated list_* reads and the analytics tools. Optional product_id (the org's primary product when omitted).
只读
幂等
输入模式
{'type': 'object', 'properties': {'window': {'enum': [7, 30, 90], 'type': 'number', 'default': 30, 'description': 'Time window in days for the revenue, cost, and analytics sections (optional; 7, 30, or 90; default 30).'}, 'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}}}
get_retention
Cohort Retention
Weekly cohort retention for the product: users grouped by first-seen week (one row per cohort, newest last), with the share still active each subsequent week — a lower-triangular grid. Needs product-analytics events flowing; returns empty cohorts when the product has none. window_days default 56 = 8 weekly cohorts (min 7; roughly one extra cohort per added 7 days). product_id optional (primary product when omitted).
只读
幂等
输入模式
{'type': 'object', 'examples': [{'window_days': 56}], 'properties': {'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; the org's primary product when omitted)."}, 'window_days': {'type': 'number', 'default': 56, 'minimum': 7, 'description': 'Lookback window in days (optional; default 56 = 8 weekly cohorts).'}}}
get_roadmap_drift
Roadmap Drift
Planned vs shipped features over a window: a drift score (0-100, 100 = perfect alignment), counts (planned / shipped / on-time / slipped / unplanned / orphaned), median slip days, and the top slipped + unplanned ships. Deterministic, no LLM cost. window = week | month | quarter (default quarter); optional product_id. Read-only; returns the drift report, zeroed when nothing was planned or shipped in the window. Use it in planning reviews to check delivery against the roadmap, then open the slipped features with list_features.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'window': 'quarter'}], 'properties': {'window': {'enum': ['week', 'month', 'quarter'], 'type': 'string', 'default': 'quarter', 'description': 'Lookback window to compare planned vs shipped over (optional; default quarter).'}, 'product_id': {'type': 'string', 'description': "Product id, from whoami (optional; spans all the org's products when omitted)."}}}
get_task
Get Task
Get one task by id and return it with its full comments and assignees. Read-only. Resolve the id first with list_tasks — never guess it; pair with update_task or comment_on_task to act on what you read.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'task_8f3a'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Task id, from list_tasks.'}}}
get_weekly_signal_memo
Weekly Signal Memo
The Weekly Product Signal Memo — the last 7 days of customer signal clustered into themes (insights grouped by feature, ranked by the revenue behind them) with verbatim quotes, week-over-week deltas (new / repeated / stronger / weaker), concluded experiments, and shipped releases. Deterministic — every count is off real rows, no fabricated quotes. Optional `week` (ISO 'YYYY-Www') for a past week; `generate=1` rebuilds + persists the current week now. Read-only apart from that rebuild; returns the persisted memo, empty when the requested week has none. Open a weekly review with it, then drill into a theme with list_insights.
只读
幂等
输入模式
{'type': 'object', 'properties': {'week': {'type': 'string', 'description': "ISO week to fetch, format 'YYYY-Www' e.g. '2026-W27' (optional; the latest persisted week when omitted)."}, 'generate': {'type': 'string', 'description': "Pass '1' to rebuild and persist the current week's memo now instead of reading the stored one (optional)."}}}
输出模式
{'type': 'object', 'required': ['week', 'counts', 'themes'], 'properties': {'week': {'type': 'string', 'description': 'ISO week the memo covers.'}, 'counts': {'type': 'object', 'properties': {'accounts': {'type': 'number'}, 'insights': {'type': 'number'}, 'releases': {'type': 'number'}, 'experiments': {'type': 'number'}}, 'additionalProperties': True}, 'themes': {'type': 'array', 'items': {'type': 'object', 'properties': {'label': {'type': 'string'}, 'featureId': {'type': ['string', 'null']}, 'evidenceCount': {'type': 'number'}}, 'additionalProperties': True}}}, 'additionalProperties': True}
list_artifact_versions
Artifact Versions
Version history of an artifact's AI reviews (F5): every review run is a version with its score, model, cost, who/what generated it, and whether it's the current one. Read-only; returns the version list, empty when the artifact has never been reviewed. Use it to see how a feature/experiment/page's review changed over time and to pick the version_id to pass to revert_to_version. Takes the same target_id/target_type you'd pass to review_artifact.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'target_id': 'feat_8f3a', 'target_type': 'feature'}], 'required': ['target_id', 'target_type'], 'properties': {'target_id': {'type': 'string', 'description': 'Id of the reviewed feature/experiment/page — the same id passed to review_artifact.'}, 'target_type': {'enum': ['feature', 'experiment', 'page'], 'type': 'string', 'description': 'What kind of artifact target_id is: a feature (spec), an experiment (plan), or a page (doc/PRD).'}}}
list_bookings
List Bookings
Upcoming confirmed bookings on the org's scheduling. Read-only; returns the bookings, empty when none are scheduled. Pass include='all' for full history.
只读
幂等
输入模式
{'type': 'object', 'properties': {'include': {'enum': ['all'], 'type': 'string', 'description': "Pass 'all' for history (optional)."}}}
list_channels
List Comms Channels
List the team Comms channels the connected member belongs to (membership-scoped). Read-only; returns the member's channels, empty when they belong to none. Call read_channel with a channel_id to read one.
只读
幂等
输入模式
{'type': 'object', 'properties': {}}
list_conversations
List Support Conversations
List support-chat conversations in the inbox (open + snoozed by default; pass status='all' to include closed). Read-only; returns the matching conversations, empty when the inbox is clear. Optional product_id to scope to one product; open a full thread with get_conversation.
只读
幂等
输入模式
{'type': 'object', 'properties': {'status': {'enum': ['all'], 'type': 'string', 'description': "Pass 'all' to include closed (optional)."}, 'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_decisions
List Decisions
List the org's logged decisions — title, rationale, status, and any linked feature/release/objective — newest first. Returns an empty list when none. Optional status filter (decided | proposed | revisit). Resolve a decision id here before update_decision.
只读
幂等
输入模式
{'type': 'object', 'properties': {'status': {'enum': ['decided', 'proposed', 'revisit'], 'type': 'string', 'description': 'Filter by status (optional).'}}}
list_experiments
List Experiments
List product experiments. Returns an array where each experiment carries its hypothesis, the metric it moves, the target, its current state, and — once concluded — the verdict and the decision that came out. Read-only; empty when none match. Use it to see what's being tested before proposing new work, and cite a concluded verdict as evidence when you create_task or review_artifact. Optional product_id (from whoami) and state filter.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'state': 'running'}], 'properties': {'state': {'type': 'string', 'description': "Only experiments in this state, e.g. 'running' (optional)."}, 'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_features
List Features
The product's feature catalogue with description, status, and when each was last touched — richer than pm_meta (which is just id+name for resolution). Read-only; returns the matching features, empty when none. Optional product_id and free-text q over name+key; use a feature id from here to link a task or insight on the spine.
只读
幂等
输入模式
{'type': 'object', 'properties': {'q': {'type': 'string', 'description': 'Free-text search over feature name + key (optional).'}, 'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_ideas
List Ideas
List the org's ideas — the native, votable idea backlog — ranked by vote count (highest first). Each returns its title, status, vote count, author, and the feature it was promoted to (if any). status ∈ new|under_review|planned|promoted|declined (optional filter). Read-only; empty when none. Ideas are distinct from insights: an idea is a proposal a team votes on; an insight is a piece of customer evidence. Resolve an idea id here before update_idea / vote_idea / promote_idea.
只读
幂等
输入模式
{'type': 'object', 'properties': {'status': {'enum': ['new', 'under_review', 'planned', 'promoted', 'declined'], 'type': 'string', 'description': 'Filter by status (optional).'}, 'product_id': {'type': 'string', 'description': 'Only ideas for this product, from whoami (optional).'}}}
list_identity_merges
Identity Merge History
List the org's end-user merge history. Returns an array of merge events, newest first, where each carries its event id, kind (merge or unmerge), the target and source end-user ids, the reason, who ran it, when, and — for merges — whether it has already been reverted. Read-only; empty when no merges have ever run. Use it to audit identity changes and to find the event id to pass to unmerge_end_users (only un-reverted merges can be undone).
只读
幂等
输入模式
{'type': 'object', 'properties': {'limit': {'type': 'number', 'default': 50, 'maximum': 200, 'minimum': 1, 'description': 'Max events to return (optional; default 50, max 200).'}}}
list_initiatives
List Initiatives
List the org's initiatives — the strategic layer between goals and features (goal → initiative → feature → epic → release). Each returns its name, status, timeframe, the objective it rolls up to (if any), and its linked-feature count. Read-only; empty when none. Resolve an initiative id here before create_feature / update_feature (initiative_id) or update_initiative.
只读
幂等
输入模式
{'type': 'object', 'properties': {'product_id': {'type': 'string', 'description': 'Only initiatives for this product, from whoami (optional; all products when omitted).'}}}
list_insights
Search Insights
Search the captured insight backlog (voice of customer) — the read twin of capture_insight. Read-only; returns the matching insights newest first, empty when nothing matches. Filters: status, kind (insight|opportunity), feature_id, account_id, product_id, and free-text q over title+body; limit default 50, max 200. Use it to survey the evidence behind a feature or account before prioritising — resolve feature_id via list_features and account_id via get_customer_360.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'q': 'SSO', 'kind': 'opportunity'}], 'properties': {'q': {'type': 'string', 'description': 'Free-text search over title + body (optional).'}, 'kind': {'enum': ['insight', 'opportunity'], 'type': 'string', 'description': "'insight' = raw signal; 'opportunity' = a prioritisable ask (optional)."}, 'limit': {'type': 'number', 'default': 50, 'maximum': 200, 'minimum': 1, 'description': 'Max rows to return (optional; default 50, max 200).'}, 'status': {'type': 'string', 'description': 'Only insights in this workflow status (optional).'}, 'account_id': {'type': 'string', 'description': 'Only insights about this account; resolve the id via get_customer_360 (optional).'}, 'feature_id': {'type': 'string', 'description': 'Only insights linked to this feature; resolve the id via list_features or pm_meta (optional).'}, 'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_objectives
List OKRs
List the org's OKRs. Returns an array of objectives, each with its key results and live progress (0..1 between start and target), so you can prioritise toward what the team is actually trying to move. Read-only; empty when none are set. Read it before prioritising — tie proposed tasks to the objective they move, and cite the live progress when arguing priority. Optional product_id, from whoami.
只读
幂等
输入模式
{'type': 'object', 'properties': {'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_pages
List Pages
List the in-product docs / PRDs (Pages) on the spine. Returns an array of pages with title + id only — no content, so it stays cheap to scan. Read-only; empty when none exist. Use it to find the page id, then read the full content with get_page; pair with review_artifact (target_type 'page') to critique a draft PRD. Optional product_id, from whoami.
只读
幂等
输入模式
{'type': 'object', 'properties': {'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_releases
List Releases
List shipped releases. Returns an array, newest first, where each release carries its version, changelog, and ship date. Read-only; empty when nothing has shipped. Use it to answer 'what did we ship recently?', to ground a changelog or launch summary in real ship dates, and to see what went out before reading get_roadmap_drift. Optional product_id, from whoami.
只读
幂等
输入模式
{'type': 'object', 'properties': {'product_id': {'type': 'string', 'description': 'Product id to scope to, from whoami (optional; spans all products when omitted).'}}}
list_sprints
List Sprints
Sprints — name, goal, state, and window, newest first. Read-only; returns the matching sprints, empty when none exist. See the delivery cadence (active + recent), and resolve a sprint_id here before scheduling a task via create_task / update_task. Optional state filter (e.g. 'active').
只读
幂等
输入模式
{'type': 'object', 'examples': [{'state': 'active'}], 'properties': {'state': {'type': 'string', 'description': "Filter by state, e.g. 'active' (optional)."}}}
list_tasks
List Tasks
List the org's board tasks and return the matches with their status, priority, assignees, and any linked feature/insight/sprint. Optionally narrow by status_id or list_id — resolve either via pm_meta. Read-only; returns an empty list when nothing matches. Use it to find a task id before get_task, update_task, or comment_on_task.
只读
幂等
输入模式
{'type': 'object', 'properties': {'list_id': {'type': 'string', 'description': 'Only tasks on this list; resolve the id via pm_meta (optional).'}, 'status_id': {'type': 'string', 'description': 'Only tasks in this status; resolve the id via pm_meta (optional).'}}}
输出模式
{'type': 'object', 'required': ['tasks'], 'properties': {'tasks': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'title'], 'properties': {'id': {'type': 'string'}, 'title': {'type': 'string'}, 'priority': {'type': ['string', 'null']}, 'status_id': {'type': ['string', 'null']}, 'feature_id': {'type': ['string', 'null']}, 'updated_at': {'type': ['string', 'null']}}, 'additionalProperties': True}}}, 'additionalProperties': True}
merge_end_users
Merge End-Users
Merge source end-users into a target and return the merge result, including the merge event id (also recoverable later via list_identity_merges): all FK rows (events, insights, tasks, …) are re-pointed onto the target and the sources are tombstoned. A write; reversible for 30 days via unmerge_end_users. Get the candidate ids from get_device_candidates first — never guess which users to fold together. target_end_user_id and source_end_user_ids are required.
输入模式
{'type': 'object', 'examples': [{'reason': 'device:anon_bridge', 'target_end_user_id': 'eu_keep', 'source_end_user_ids': ['eu_discard']}], 'required': ['target_end_user_id', 'source_end_user_ids'], 'properties': {'reason': {'type': 'string', 'description': 'Why the merge (optional, recorded).'}, 'target_end_user_id': {'type': 'string', 'description': 'UUID of the end-user to keep, from get_device_candidates.'}, 'source_end_user_ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'UUIDs of end-users to fold into the target, from get_device_candidates.'}}}
pm_meta
PM Metadata
List the org's PM lists, statuses, members, and features as id+name pairs. Read-only; returns arrays for resolution only (list_features carries the richer catalogue). Call it to turn a name into an id before create_task / update_task — never guess an id.
只读
幂等
输入模式
{'type': 'object', 'properties': {}}
post_to_channel
Post to Channel
Post a message to a team Comms channel you belong to, as the connected member, and return the posted message. It appears live for teammates and is org-visible — keep it work-relevant. Resolve channel_id via list_channels; you can only post to channels you're a member of. Both channel_id and body are required.
输入模式
{'type': 'object', 'examples': [{'body': 'Shipped SSO — closing the epic.', 'channel_id': 'chan_123'}], 'required': ['channel_id', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Message text, visible to all channel members (required).'}, 'channel_id': {'type': 'string', 'description': 'Channel id to post into, from list_channels (required).'}}}
promote_idea
Promote Idea to Feature
Promote an idea into a roadmap feature: creates a feature from the idea (name + description), stamps the idea 'promoted' and links it to the new feature, and returns the feature id. Idempotent — an already-promoted idea returns its existing feature. Resolve the id via list_ideas; only id is required. Align the new feature to an initiative/goal afterwards with update_feature.
输入模式
{'type': 'object', 'examples': [{'id': 'idea_123'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Idea id to promote, from list_ideas (required).'}, 'product_id': {'type': 'string', 'description': "Product to create the feature under, from whoami (optional; the idea's product or the primary when omitted)."}}}
read_channel
Read Comms Channel
Read a Comms channel's recent messages, newest included (the connected member must be a channel member). Read-only; returns the messages, empty when the channel is silent. Resolve channel_id first with list_channels — never guess it. Optional limit.
只读
幂等
输入模式
{'type': 'object', 'examples': [{'limit': 50, 'channel_id': 'chan_eng'}], 'required': ['channel_id'], 'properties': {'limit': {'type': 'number', 'description': 'Max messages to return (optional).'}, 'channel_id': {'type': 'string', 'description': 'Channel id, from list_channels.'}}}
reply_in_channel
Reply in Channel Thread
Reply in a thread under a specific message in a Comms channel you belong to, as the connected member, and return the posted reply — org-visible to the channel. Resolve channel_id via list_channels and the parent message's id via read_channel. channel_id, parent_id, and body are all required.
输入模式
{'type': 'object', 'examples': [{'body': 'On it — PR up in an hour.', 'parent_id': 'msg_9', 'channel_id': 'chan_123'}], 'required': ['channel_id', 'parent_id', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Reply text, visible to all channel members (required).'}, 'parent_id': {'type': 'string', 'description': 'Parent message id to thread under, from read_channel (required).'}, 'channel_id': {'type': 'string', 'description': 'Channel id, from list_channels (required).'}}}
reply_to_conversation
Reply to Support Conversation
Send a public reply to a support-inbox conversation, as the connected member, and return the result — it goes to the end-user on the conversation's channel. A write. Resolve conversation_id via list_conversations; read the thread with get_conversation before replying. conversation_id and body are required. For an internal-only note use add_note; to close it use resolve_conversation.
可访问外部资源
输入模式
{'type': 'object', 'examples': [{'body': 'Thanks for flagging — the export bug is fixed and live.', 'conversation_id': 'conv_42'}], 'required': ['conversation_id', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Public reply text sent to the end-user (required).'}, 'conversation_id': {'type': 'string', 'description': 'Conversation id to reply to, from list_conversations (required).'}}}
reschedule_booking
Reschedule Booking
Reschedule a booking to a new start time (ISO 8601) and return the result — the invitee is notified. A write. Resolve booking_id via list_bookings first. booking_id and start are required.
可访问外部资源
输入模式
{'type': 'object', 'examples': [{'start': '2026-07-20T15:00:00Z', 'booking_id': 'book_7'}], 'required': ['booking_id', 'start'], 'properties': {'start': {'type': 'string', 'description': 'New start time, ISO 8601 (e.g. 2026-07-20T15:00:00Z) (required).'}, 'booking_id': {'type': 'string', 'description': 'Booking id to move, from list_bookings (required).'}}}
resolve_conversation
Resolve Conversation
Mark a support-inbox conversation resolved (closed) and return the result. A write; idempotent — resolving an already-resolved conversation is a no-op. Resolve conversation_id via list_conversations first. Do it after you've replied and the ask is handled.
幂等
输入模式
{'type': 'object', 'examples': [{'conversation_id': 'conv_42'}], 'required': ['conversation_id'], 'properties': {'conversation_id': {'type': 'string', 'description': 'Conversation id to resolve, from list_conversations (required).'}}}
revert_to_version
Revert Artifact Version
Restore an earlier artifact version (F5) to current and return the now-current version: the existing current version is flipped to 'reverted' (kept for the learning signal) and the chosen version becomes current again. A write — not idempotent, since re-running reverts again. version_id is the version you want to RESTORE; get it from list_artifact_versions and never guess it. Optional reason is recorded.
输入模式
{'type': 'object', 'examples': [{'reason': 'new review missed the metric finding', 'version_id': 'ver_8f3a'}], 'required': ['version_id'], 'properties': {'reason': {'type': 'string', 'description': "Why you're reverting (optional, recorded)."}, 'version_id': {'type': 'string', 'description': 'Id of the version to restore (make current), from list_artifact_versions.'}}}
review_artifact
PRD Review
Agent-as-critic over a DRAFT artifact (a feature spec, experiment plan, or page): checks it against a baseline PM bar — clear problem/hypothesis, a measurable success metric, evidence cited, risks named, a rollout/experiment plan — and returns structured findings (section, severity, a CONCRETE suggested fix, and a verbatim evidence quote) plus a 0-100 score. A write: each call re-runs the review and persists it as a new version (see list_artifact_versions). Resolve target_id first — via pm_meta or list_features for a feature, list_experiments for an experiment, list_pages for a page. One small LLM call; use it before sending a draft for sign-off.
输入模式
{'type': 'object', 'examples': [{'target_id': 'feat_8f3a', 'target_type': 'feature'}], 'required': ['target_id', 'target_type'], 'properties': {'rubric_id': {'type': 'string', 'description': "Score against a specific rubric; omit to use the org's default rubric (or the built-in baseline)."}, 'target_id': {'type': 'string', 'description': 'Id of the feature/experiment/page to review — from pm_meta, list_features, list_experiments, or list_pages.'}, 'target_type': {'enum': ['feature', 'experiment', 'page'], 'type': 'string', 'description': 'What kind of artifact target_id is: a feature (spec), an experiment (plan), or a page (doc/PRD).'}}}
unmerge_end_users
Undo End-User Merge
Undo a previous end-user merge: reads the merge ledger and re-points every FK row (events, insights, tasks, …) back to its original end-user, un-tombstoning the folded-in sources. Safe to retry — a second undo of the same merge changes nothing (it fails with already_reverted). Use to correct a wrong identity merge (merges stay reversible for 30 days). Find the event_id with list_identity_merges (pick an un-reverted merge); event_id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'event_id': 'uuid'}], 'required': ['event_id'], 'properties': {'event_id': {'type': 'string', 'description': 'Id of the merge event to undo, from list_identity_merges.'}}}
update_decision
Update Decision
Update a decision and return it; omitted fields unchanged. Moving status to 'decided' re-stamps the decision time. Re-link via link_type + link_id (verified in-org), or clear with nulls. Resolve the id via list_decisions; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'dec_123', 'status': 'revisit'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Decision id, from list_decisions (required).'}, 'title': {'type': 'string', 'description': 'New title (optional).'}, 'status': {'enum': ['decided', 'proposed', 'revisit'], 'type': 'string', 'description': 'New status (optional).'}, 'link_id': {'type': 'string', 'description': 'New linked id, or null to unlink (optional).'}, 'link_type': {'enum': ['feature', 'release', 'objective'], 'type': 'string', 'description': 'New link target (optional).'}, 'rationale': {'type': 'string', 'description': 'New rationale; null clears it (optional).'}}}
update_experiment
Update Experiment
Update a PM experiment — advance its state and record the outcome — and return it. state ∈ hypothesis|build|measure|learn; verdict ∈ validated|invalidated; decision ∈ pivot|persevere. Resolve the id via list_experiments; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'exp_123', 'state': 'learn', 'verdict': 'validated', 'decision': 'persevere'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Experiment id, from list_experiments (required).'}, 'state': {'enum': ['hypothesis', 'build', 'measure', 'learn'], 'type': 'string', 'description': 'Build-Measure-Learn stage (optional).'}, 'title': {'type': 'string', 'description': 'New title (optional).'}, 'metric': {'type': 'string', 'description': 'New metric; null clears it (optional).'}, 'result': {'type': 'string', 'description': 'Free-text result / what you learned; null clears it (optional).'}, 'target': {'type': 'string', 'description': 'New target; null clears it (optional).'}, 'verdict': {'enum': ['validated', 'invalidated'], 'type': 'string', 'description': 'Outcome (optional).'}, 'decision': {'enum': ['pivot', 'persevere'], 'type': 'string', 'description': "What you'll do next (optional)."}, 'hypothesis': {'type': 'string', 'description': 'New hypothesis; null clears it (optional).'}}}
update_feature
Update Feature
Update a feature and return it; omitted fields are unchanged. status is 'active' | 'discovered' | 'archived' (there is NO 'shipped' status — set mark_shipped:true to stamp its ship date instead). target_date is 'YYYY-MM-DD' (or null to clear). Resolve the id via list_features; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'feat_123', 'mark_shipped': True}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Feature id to update, from list_features (required).'}, 'name': {'type': 'string', 'description': 'New name (optional).'}, 'status': {'enum': ['active', 'discovered', 'archived'], 'type': 'string', 'description': 'Lifecycle status (optional).'}, 'description': {'type': 'string', 'description': 'New description; null clears it (optional).'}, 'target_date': {'type': 'string', 'description': "Target ship date 'YYYY-MM-DD', or null to clear (optional)."}, 'mark_shipped': {'type': 'boolean', 'description': 'true stamps the ship date now; false clears it (optional).'}, 'objective_id': {'type': 'string', 'description': 'Align directly under this objective, from list_objectives; null unlinks (optional).'}, 'initiative_id': {'type': 'string', 'description': 'Align under this initiative (line-of-sight), from list_initiatives; null unlinks (optional).'}}}
update_idea
Update Idea
Update an idea's title / body / status and return it; omitted fields unchanged. status ∈ new|under_review|planned|promoted|declined (set 'promoted' via promote_idea instead, so a feature is actually created). Resolve the id via list_ideas; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'idea_123', 'status': 'under_review'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Idea id, from list_ideas (required).'}, 'body': {'type': 'string', 'description': 'New body; null clears it (optional).'}, 'title': {'type': 'string', 'description': 'New title (optional).'}, 'status': {'enum': ['new', 'under_review', 'planned', 'promoted', 'declined'], 'type': 'string', 'description': "New status (optional; prefer promote_idea over setting 'promoted' by hand)."}}}
update_initiative
Update Initiative
Update an initiative and return it; omitted fields are unchanged. Re-point it to a different goal with objective_id (null unlinks). status ∈ planned|active|paused|done|abandoned. Resolve the id via list_initiatives; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'init_123', 'status': 'active'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Initiative id, from list_initiatives (required).'}, 'name': {'type': 'string', 'description': 'New name (optional).'}, 'status': {'enum': ['planned', 'active', 'paused', 'done', 'abandoned'], 'type': 'string', 'description': 'Lifecycle status (optional).'}, 'timeframe': {'type': 'string', 'description': 'New timeframe; null clears it (optional).'}, 'description': {'type': 'string', 'description': 'New description; null clears it (optional).'}, 'objective_id': {'type': 'string', 'description': 'New parent goal, from list_objectives; null unlinks (optional).'}}}
update_key_result
Update Key Result
Update a key result — most often to move current_value as progress lands — and return it; omitted fields are unchanged. Resolve the id via list_objectives (each objective carries its key_results with ids). Only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'kr_123', 'current_value': 42000}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Key result id, from list_objectives (required).'}, 'name': {'type': 'string', 'description': 'New name (optional).'}, 'unit': {'type': 'string', 'description': "New unit, e.g. 'USD'; null clears it (optional)."}, 'start_value': {'type': 'number', 'description': 'New starting baseline (optional).'}, 'target_value': {'type': 'number', 'description': 'New target value; null clears it (optional).'}, 'current_value': {'type': 'number', 'description': 'New current value (optional).'}}}
update_objective
Update Objective
Update an objective's name / description / period and return it; omitted fields are unchanged (null clears description or period). Resolve the id via list_objectives; only id is required. To move a key result's value use update_key_result.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'obj_123', 'name': 'Reach $75k MRR'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Objective id, from list_objectives (required).'}, 'name': {'type': 'string', 'description': 'New name (optional).'}, 'period': {'type': 'string', 'description': "New period, e.g. 'Q4 2026'; null clears it (optional)."}, 'description': {'type': 'string', 'description': 'New description; null clears it (optional).'}}}
update_page
Update Page
Update a Page — rename, set icon, replace the body, or archive/unarchive (archived:true hides it, false restores it). `body` is plain text (blank lines → paragraphs) and REPLACES the page content. Omitted fields are unchanged. Resolve the id via list_pages; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'page_123', 'archived': True}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Page id, from list_pages (required).'}, 'body': {'type': 'string', 'description': 'New content as plain text; blank lines separate paragraphs. REPLACES existing content (optional).'}, 'icon': {'type': 'string', 'description': 'New emoji icon; null clears it (optional).'}, 'title': {'type': 'string', 'description': 'New title (optional).'}, 'archived': {'type': 'boolean', 'description': 'true archives (hides) the page; false restores it (optional).'}}}
update_release
Update Release
Update a release and return it; omitted fields unchanged. Set released_at to ship it (or null to move it back to draft). Resolve the id via list_releases; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'rel_123', 'released_at': '2026-07-15T12:00:00Z'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Release id, from list_releases (required).'}, 'version': {'type': 'string', 'description': 'New version (optional).'}, 'changelog': {'type': 'string', 'description': 'New changelog; null clears it (optional).'}, 'released_at': {'type': 'string', 'description': 'Ship time ISO 8601, or null for draft (optional).'}}}
update_sprint
Update Sprint
Update a sprint and return it. state is 'future' | 'active' | 'closed' — moving to 'closed' stamps the completion time, reopening clears it. start_date / end_date are ISO 8601 (or null to clear). Resolve the id via list_sprints; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'spr_123', 'state': 'closed'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Sprint id, from list_sprints (required).'}, 'goal': {'type': 'string', 'description': 'New goal; null clears it (optional).'}, 'name': {'type': 'string', 'description': 'New name (optional).'}, 'state': {'enum': ['future', 'active', 'closed'], 'type': 'string', 'description': "Lifecycle state; 'closed' completes it (optional)."}, 'end_date': {'type': 'string', 'description': 'End, ISO 8601, or null (optional).'}, 'start_date': {'type': 'string', 'description': 'Start, ISO 8601, or null (optional).'}}}
update_task
Update Task
Update one or more of a task's fields and return the updated task; fields you omit are left unchanged (idempotent — re-sending the same values is a no-op). Pass sprint_id: null to remove the task from its sprint. Resolve ids first — the task via get_task/list_tasks, and status/feature/insight/sprint/member ids via pm_meta and the list_* reads — never guess them. Only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'task_8f3a', 'status_id': 'status_in_progress'}, {'id': 'task_8f3a', 'sprint_id': 'sprint_2026_w27'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Task id, from list_tasks or get_task.'}, 'title': {'type': 'string', 'description': 'New title (optional; omitted fields stay unchanged).'}, 'priority': {'enum': ['urgent', 'high', 'normal', 'low'], 'type': 'string', 'description': 'New priority level, urgent highest (optional).'}, 'sprint_id': {'type': 'string', 'description': 'Move into a sprint, or null to remove (optional; resolve via list_sprints).'}, 'status_id': {'type': 'string', 'description': 'New status; resolve the id via pm_meta (optional).'}, 'feature_id': {'type': 'string', 'description': 'Feature id to link on the spine, from pm_meta or list_features (optional).'}, 'insight_id': {'type': 'string', 'description': 'Insight id to link on the spine, from list_insights (optional).'}, 'description': {'type': 'string', 'description': 'New body / details (optional).'}, 'assignee_member_ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Member ids to assign, from pm_meta (optional).'}}}
vote_idea
Vote on Idea
Cast (or remove) the connected member's vote on an idea and return the new vote state. Adds your vote by default; pass remove:true to take it back. One vote per member — voting twice is a no-op. Resolve the id via list_ideas; only id is required.
幂等
输入模式
{'type': 'object', 'examples': [{'id': 'idea_123'}], 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Idea id, from list_ideas (required).'}, 'remove': {'type': 'boolean', 'description': 'true removes your vote instead of adding it (optional; default false).'}}}
whoami
Connected Identity
Show the connected AIOProductOS identity (org, member) AND the org's products (id, name, is_primary). Read-only; returns the identity plus the product list. For a multi-product org, call this first to get the product ids, then pass one as `product_id` to any product-scoped tool; omit product_id to use the primary.
只读
幂等
输入模式
{'type': 'object', 'properties': {}}
历史
近期工具变更
已添加
unmerge_end_users
2026年9月17日 12:33
已添加
merge_end_users
2026年9月17日 12:33
已添加
list_identity_merges
2026年9月17日 12:33
已添加
get_device_candidates
2026年9月17日 12:33
已添加
list_bookings
2026年9月17日 12:33
已添加
read_channel
2026年9月17日 12:33
已添加
list_channels
2026年9月17日 12:33
已添加
list_sprints
2026年9月17日 12:33
已添加
get_codebase_map
2026年9月17日 12:33
已添加
get_page
2026年9月17日 12:33
已添加
list_pages
2026年9月17日 12:33
已添加
list_releases
2026年9月17日 12:33
已添加
list_experiments
2026年9月17日 12:33
已添加
list_objectives
2026年9月17日 12:33
已添加
list_features
2026年9月17日 12:33
已添加
list_insights
2026年9月17日 12:33
已添加
get_conversation
2026年9月17日 12:33
已添加
list_conversations
2026年9月17日 12:33
已添加
capture_insight
2026年9月17日 12:33
已添加
comment_on_task
2026年9月17日 12:33
已添加
update_task
2026年9月17日 12:33
已添加
revert_to_version
2026年9月17日 12:33
已添加
list_artifact_versions
2026年9月17日 12:33
已添加
review_artifact
2026年9月17日 12:33
已添加
reschedule_booking
2026年9月17日 12:33
已添加
cancel_booking
2026年9月17日 12:33
已添加
resolve_conversation
2026年9月17日 12:33
已添加
add_note
2026年9月17日 12:33
已添加
reply_to_conversation
2026年9月17日 12:33
已添加
reply_in_channel
2026年9月17日 12:33
发现
类似的 MCP 服务器
roadflow
io.roadflow/roadflow
Creates and shares roadmap graphs, and manages structured model registers containing parameters, observations, formulas, dictiona…
DeskMonitor
com.thedeskmonitor/mcp
Supports workforce attendance, timesheets, employee management, team hours, productivity reporting, workload alerts, approvals, a…
Atisbo
io.github.brian8a1/atisbo
Manages workspace signals, opportunities, decisions, backlogs, documents, integrations, evidence, analytics, and operational maps.
Elasticflow
app.elasticflow/mcp
Provides a team workspace with tables, documents, workflow automation, dashboards, and analytics.
freedom-mcp
com.getfreedomos/freedom-mcp
Supports company operations through commitments, teams, agents, customer evidence, leads, content workflows, spreadsheets, commer…
synter-ads
io.github.Synter-Media-AI/synter-ads
Manages cross-platform advertising campaigns, audiences, tracking, creative, landing pages, campaign audits, technology intellige…
synter-ads
io.github.jshorwitz/synter-ads
Manages cross-platform advertising campaigns, audiences, tracking, creative, landing pages, campaign audits, technology intellige…
Stratalize Finance
com.stratalize/finance
Provides financial, macroeconomic, banking, credit, commodities, M&A, ESG, labor, and regulatory benchmarks for analysis and plan…