Skip to content
ReviewDesk

Developers

MCP tool reference

What a connected assistant can read and change, and why every mutation takes two steps

Once connected, your assistant gets the tools below. They fall into two groups: tools that read, which run directly, and tools that change something, which do not.

Reading

ToolWhat it does
get_session_contextWho you are, which organization, and what you can access.
list_appsYour connected apps and their sync status.
list_reviewsSearch and filter reviews, with the same filters as the inbox.
get_reviewOne review in full, including any existing reply.
list_alertsRecent alerts.
get_analyticsDashboard-style metrics.
get_account_overviewA roll-up across an account.
get_pipeline_statusWhether ingestion and classification are running and current.
list_team_membersMembers and their assignments.
get_reply_statusWhere a specific reply is in its lifecycle.

Drafting and translation

ToolWhat it does
draft_replyGenerate a draft for a review by ID.
draft_reply_from_screenshotMatch a pasted screenshot to a review and draft a reply. See Screenshot-to-reply.
translate_reviewTranslate a review into a target language.
adjust_support_emailAdd or remove the support-email line on an existing draft.

Changing things

StageConfirmCovers
stage_replyconfirm_reply_actionSending or editing a reply.
—confirm_post_replyPublishing a draft that is already prepared.
stage_app_changeconfirm_app_changeApp settings and credentials.
stage_team_changeconfirm_team_changeMembers, assignments, reply permission.

Two further tools change configuration and follow the same discipline: manage_app_connection for connecting and pausing apps, and manage_auto_reply for automation rules. triage_alerts marks alerts read.

What still applies

Working through MCP does not bypass anything. Drafts count against your daily generation limit, replies obey store character caps, automation rules still govern what sends automatically, and a team member’s assignments still scope what they can see.