Skip to main content
Ambiguous MCP logo
  • Category: model context protocol
  • Auth: API_KEY
  • Composio-managed OAuth available? N/A
  • Tools: 945
  • Triggers: 0
  • Slug: AMBIGUOUS_MCP
  • Version: 00000000_00

Tools

Slug: AMBIGUOUS_MCP_ACK_MENTIONS_ACTIVITYAcknowledge the Mentions & reactions inbox after it has been displayed. Marks the caller’s unread chat mention notifications read and stamps users.mentions_acked_at, so the projector recomputes both chat.mentions and chat.reactions to 0 durably (the sidebar “Mentions & reactions” item un-bolds and stays cleared across re-fetch). Per-channel read cursors are untouched, so channel message unread counts are unaffected; a reaction that arrives after the ack re-bolds the item.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ACK_THREAD_ACTIVITYAcknowledge readable Threads inbox activity on entry without advancing personal read cursors or clearing explicit manual unread intent.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_CONDITIONAL_FORMATAdd a conditional formatting rule to a spreadsheet. Provide one of booleanRule, gradientRule, iconSetRule, or dataBarRule. The server generates a unique ID for the rule.

Input Parameters

string
required
array
object
object
object
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_CONNECTED_ELEMENTExtend a flow: place a new node beside an existing element and connect them in one call — the server computes the position unless you pass drop_point. Use this instead of create_canvas_element + a manual connector when building a flowchart, product map, or swimlane step-by-step. Give source_element_id and a direction (n/s/e/w); the new node lands one standard gap on that side and is nudged clear of any overlap, and a connector is created pre-attached from the source to it. For a drag-to-empty gesture, supply optional drop_point: { x, y } to center the new node at that board-space point instead of automatic placement. Provide element for the new node’s type (connector/frame/swimlane not allowed here), or omit it to duplicate the source. Coordinates: board units, top-left origin, +x right / +y down. Example: add_connected_element({ id: “<boardId>”, source_element_id: “<elId>”, direction: “e”, element: { type: “shape”, shape: “diamond” } }) → { element, connector }.

Input Parameters

string
required
Canvas board id.
string
The new node to place (geometry omitted — the server positions it). Omit to duplicate the source’s type, shape, size, and style.
object
Optional connector styling; defaults to an elbow line with an arrow at the new element.
string ("n" | "s" | "e" | "w")
required
Side of the source to place the new element on: n/s/e/w.
object
Optional board-space center for a dragged connected step. Omit for automatic placement beside the source.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
Existing element to connect the new one from.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_DEAL_LINE_ITEMAdd a line item to a deal. Either reference an existing product (via product_id) or create a custom line by providing name and unit_price. The deal amount is auto-recalculated.

Input Parameters

string
required
string
number
required
string
integer
number
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
number
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_FORWARDING_ADDRESSAdd a forwarding address (sends verification email).

Input Parameters

string
string ("all" | "matching")
all forwards every inbound message; matching only those matched by a forwarding rule.
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_PIPELINE_MEMBERAdd (or update the role of) a user or team on a CRM pipeline. Provide either user_id or team_id, plus role (admin | member). Admins/owners and pipeline admins can manage members.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_SHARED_DRIVE_MEMBERAdd a member (manager-only).

Input Parameters

string ("manager" | "content_manager" | "contributor" | "commenter" | "viewer")
required
Membership role on a shared drive.
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_SHEET_COLUMNAdd a column to a sheet tab.

Input Parameters

string
required
string
string
string
number
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_SHEET_ROWSAppend rows to a sheet tab. Each row is an object keyed by column ID. Example: [{“A”: “Widget”, “B”: 9.99}].

Input Parameters

string
required
array
string
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_SHEET_TABAdd a new tab to a sheet. Auto-generates the name if not provided.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_SLIDEAdd a new slide to an existing presentation. Provide the slide as a JSON object with layout, background, and elements. Each element has a type (text, image, shape, table, video, group), position (x, y), size (w, h), and type-specific properties. IMPORTANT: Create SEPARATE text elements for each visual block (title, each bullet point, each paragraph). Do NOT put multiple lines or bullet points in a single text element — create one element per line with proper positioning. Use bullet character ’•’ instead of markdown ’*’ or ’-’. Set fontSize and fontWeight per element for visual hierarchy. If the user is currently viewing a presentation, use the presentation ID from the page context.

Input Parameters

string
required
string
object
Slide body (full or partial — service merges).
object
array
Element list. Convenience for callers that don’t wrap in slide.
string
Slide background color, for example “#0F1B33”.
integer
Insert position. Omit to append.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_TASK_ATTACHMENTAttach a Drive file to a task. Idempotent — re-attaching the same file returns the existing row. Attaching makes the file readable by everyone who can read the task, so a file you do not own needs the share right on it (403 file_attach_requires_share when you can only view it).

Input Parameters

string
required
string
required
Drive file ID to attach
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADD_TEAM_MEMBERAdd a user to a team with an optional role (admin or member). Only team admins or workspace admins can add members. Default role is ‘member’. Use this when the user asks to add someone to a team or distribution list.

Input Parameters

string ("admin" | "member")
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INTEGRATION_DELETEdisconnect an integration

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INTEGRATIONS_LISTlist all integrations for workspace

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INTEGRATIONS_SLACK_CHANNELSlist Slack channels via bot token

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INTEGRATION_UPDATEupdate integration config

Input Parameters

string
required
Resource ID.
object
string ("active" | "inactive" | "error")
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INVITE_DELETERevoke (cancel) a pending invite. Pending only — an accepted or expired invite is refused 409 invite_not_pending; its row is history, not a live grant.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INVITE_RESENDResend invite email + refresh expiry. The email carries a freshly minted link, so every link sent before for this invite stops working. Pending invites only — an accepted or expired invite is refused 409 invite_not_pending.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_INVITES_LISTList pending, accepted, and expired workspace invites, pending first and then newest. Paginated; pending_total counts invites awaiting acceptance. Each row also carries delivery — what the provider said about the latest send of that invite email, so a bounced invite is distinguishable from an ignored one.

Input Parameters

integer
Page size (default 50, max 200).
string
string
integer
Offset for pagination (must be >= 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSION_CREATEmanually add a suppression

Input Parameters

string ("bounce" | "complaint")
required
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSION_DELETEremove a suppression

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSIONS_LISTlist suppressed addresses

Input Parameters

string ("bounce" | "complaint")
Filter by suppression type.
integer
Page size (default 50, max 500).
string
string
integer
Offset for pagination (must be ≥ 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_NOTIFICATION_DEFAULTS_GETRead workspace-default email notification prefs. Returns sensible defaults (all enabled) when never configured.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_NOTIFICATION_DEFAULTS_UPDATEPartially update workspace-default email notification prefs. Emits settings.updated audit event.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
boolean
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
boolean
boolean
Slug: AMBIGUOUS_MCP_ADMIN_USAGE_EXPORTExport usage stats as CSV

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_USAGE_TIMESERIESDaily creation counts (last 14 days, split into “last 7” + “prior 7” windows) for the four hero metrics on the Overview tab. Returns {users, documents, messages, emails} each with {buckets[7], total, previous_total} so the UI can draw a sparkline + render a 7…

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_USER_GETGet one workspace user’s full admin record by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_USER_RESET_PASSWORDCreate and email a one-hour password-reset link. On delivery failure, returns sent: false with reset_url.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_USER_SUSPENDSuspend a user account. Suspended accounts return 403 on all API calls.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_USER_UNSUSPENDUnsuspend a user account. Restores access to all API calls.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ADMIN_WORKSPACE_LOGO_DELETERemove workspace logo (admin only)

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_ANNOTATIONS_LISTList a project’s annotations, oldest date first: each is a date, an optional end date, a short text and its author, drawn on every time-series chart in the project. from/to keep only annotations overlapping that range.

Input Parameters

string
required
string
Only annotations that start on or before this date.
string
Only annotations that end on or after this date.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_CATALOG_OVERRIDES_LISTList catalog metadata overrides for the workspace.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_CATALOG_STATSPer-event last_seen_at and 30-day volume for the workspace’s tracked events.

Input Parameters

string
string
string ("true" | "false")
Use the workspace-wide management catalog (workspace admin only), instead of a project view.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_COHORTS_GETRead a saved cohort’s name, stored criteria and member-count snapshot by ID, without recomputing its audience. Use analytics_cohorts_list to find cohort IDs. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_COHORTS_LISTList saved cohort reports in the active workspace, including their definitions and stored member counts. Lists one Analytics project (project_id) and requires a role on it.

Input Parameters

string
string
string
The Analytics project to list. Omitted, the workspace’s default project is used while clients migrate.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_DASHBOARDS_GETRead a saved analytics dashboard’s name, stored query and tile layout by ID. Requires a role on the dashboard’s project; unavailable dashboards return not found. Use analytics_dashboards_list to find accessible IDs. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_DASHBOARDS_LISTList the saved analytics dashboards of one Analytics project (project_id), including their tile layouts. Everyone who can view the project sees every dashboard in it. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
string
string
The Analytics project to list. Omitted, the workspace’s default project is used while clients migrate.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_EVENTS_GETRead one Analytics evidence event owned by the caller’s source workspace. Foreign and missing IDs return 404.

Input Parameters

integer
required
string
string
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_EVENTS_LISTList source-owned Analytics evidence with bounded filters and stable pagination. Measured group IDs never grant access.

Input Parameters

string ("track" | "identify" | "page" | "group" | "alias")
string
integer
string
string
string
ISO timestamp (an instant), ISO date or offset-less timestamp (wall clock in the workspace analytics timezone), now / now-N{h,d,w,m} (rolling from this instant), or today / today-N{d,w,m} (start of a calendar day in the workspace analytics timezone). dateFrom is inclusive, dateTo exclusive.
integer
string
ISO timestamp (an instant), ISO date or offset-less timestamp (wall clock in the workspace analytics timezone), now / now-N{h,d,w,m} (rolling from this instant), or today / today-N{d,w,m} (start of a calendar day in the workspace analytics timezone). dateFrom is inclusive, dateTo exclusive.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_FUNNELS_GETRead a saved funnel report’s name and stored conversion query definition by ID, without running the funnel. Use analytics_funnels_list to find report IDs. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_FUNNELS_LISTList saved funnel reports in the active workspace, including their names and conversion query definitions. Lists one Analytics project (project_id) and requires a role on it.

Input Parameters

string
string
string
The Analytics project to list. Omitted, the workspace’s default project is used while clients migrate.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_INSIGHTS_GETRead a saved insights report’s name and stored query definition by ID, without executing the query. Use analytics_insights_list to find report IDs. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_INSIGHTS_LISTList saved insights reports in the active workspace, including their names and query definitions. Lists one Analytics project (project_id) and requires a role on it.

Input Parameters

string
string
string
The Analytics project to list. Omitted, the workspace’s default project is used while clients migrate.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_METRIC_DEFINITIONS_LISTList metric definitions visible in the named Analytics project, or its workspace default when omitted. management=true instead reads the workspace-wide admin catalog. Each definition includes its newest stored period.

Input Parameters

string
string
string ("true" | "false")
Use the workspace-wide management catalog (workspace admin only), instead of a project view.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_METRICS_UPSERTUpsert external metric rows (ad spend, cloud spend, incident minutes) keyed by metric, grain, period and dimensions. A row replaces the live value only when its observed_at is newer; an older observation is kept in the restatement history and reported as stale. Requires workspace admin rank and the analytics.write scope; the public write key is refused.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_METRIC_VALUERead one number from a saved insight or funnel over a window: the value, the same metric over the window before it, a sparkline and a link to the report. Embedded metrics on canvas, in chips and in sheets read through this. Example: report=insights:<id>&from=today-28d&to=now.

Input Parameters

string
Window end (exclusive). Defaults to the report’s saved window.
string
Window start (inclusive). Defaults to the report’s saved window.
integer
Funnels only: report the count reaching this 1-based step instead of overall conversion.
string
string
string
required
The saved report to read, as insights:<id> or funnels:<id>.
string
JSON property filters composed with the saved report’s filters, for dashboard number tiles.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_MV_METADATAGet materialized view name and last refresh time.

Input Parameters

string
string
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_CREATEAsk the project’s owners for access at viewer or editor. Must ask higher than the role held (400 access_role_not_higher); 409 access_request_open while one is open; 404 for an unknown project.

Input Parameters

string
required
string ("viewer" | "editor")
required
The role being asked for.
string
An optional note to whoever decides the request.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_CURRENTReturn whether the caller has an open access request for the project.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_DECIDEApprove at viewer or editor, or decline, an open access request. Project owners only. Returns 409 once decided.

Input Parameters

string
required
string ("viewer" | "editor")
The role the owner grants — need not equal the role asked for. decision approve only.
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_GETRead one Analytics project, its view and the caller’s role. 404 when the caller holds no role on it.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_LISTList the Analytics projects the caller holds a role on, each with its view and the caller’s role. Workspace admins hold no implicit role: a private project an admin was not added to is not listed.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_PROJECTS_PERMISSIONS_LISTList the project’s members: users and teams with their roles. The Everyone team row is the workspace tier.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_QUERY_EXECUTEExecute an ad-hoc analytics query (events/insights/funnel/retention/cohort). Returns structured results over the project’s view (the workspace default project when project_id is omitted).

Input Parameters

string
required
string
type insights only.
integer
type events, drilldown only.
string ("all" | "any")
type cohort only.
string
type drilldown only.
array
type funnel only.
object
type events only.
string
ISO timestamp (an instant), ISO date or offset-less timestamp (wall clock in the workspace analytics timezone), now / now-N{h,d,w,m} (rolling from this instant), or today / today-N{d,w,m} (start of a calendar day in the workspace analytics timezone). dateFrom is inclusive, dateTo exclusive. type insights, funnel, retention, cohort only.
string
string
string ("event" | "metric")
type insights only.
string
type events, insights only.
integer
type retention only.
array
type insights, funnel, retention only.
array
type cohort only.
string
ISO timestamp (an instant), ISO date or offset-less timestamp (wall clock in the workspace analytics timezone), now / now-N{h,d,w,m} (rolling from this instant), or today / today-N{d,w,m} (start of a calendar day in the workspace analytics timezone). dateFrom is inclusive, dateTo exclusive. type insights, funnel, retention, cohort only.
string
type insights, funnel, retention only.
string
type insights, funnel only.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
type insights only.
string ("count" | "sum" | "unique" | "ratio")
type insights only.
string ("event" | "metric")
type insights only.
string
type retention only.
string
type retention only.
array
type insights only.
boolean
type funnel only.
array
type retention only.
array
type retention only.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
type funnel only.
string
type insights only.
string
Which step of an attempt supplies its breakdown value: a step number (1-based, default 1), the first step with a value, or the last. A person trait key ignores it. type funnel only.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_RESTRICTED_MARKS_LISTList the workspace’s restricted event names, trait keys and metric keys. Workspace admin only.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_RETENTIONS_GETRead a saved retention report’s name and stored query definition by ID, without computing retention. Use analytics_retentions_list to find report IDs. Requires a role on the report’s project; 404 otherwise.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_RETENTIONS_LISTList saved retention reports in the active workspace, including their names and query definitions. Lists one Analytics project (project_id) and requires a role on it.

Input Parameters

string
string
string
The Analytics project to list. Omitted, the workspace’s default project is used while clients migrate.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_SETTINGS_GETGet the workspace’s analytics settings — the timezone calendar windows such as today-7d and day/week/month buckets resolve in.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_USERS_AGGREGATESList analytics user profiles from the materialized view (faster at high volume, nightly refresh). Falls back to direct read when MV is unavailable.

Input Parameters

integer
Page size (1-200, default 50).
string
string
integer
Page offset (default 0).
Substring match on analytics_user_id.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_USERS_LISTList analytics user profiles (paginated, searchable). Returns traits, first_seen, last_identified.

Input Parameters

integer
Page size (1-200, default 50).
string
string
integer
Page offset (default 0).
string
Substring match on analytics_user_id.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_USER_TIMELINEGet a user’s event timeline with session grouping (30-min inactivity split). Walks the alias graph (depth 5) to include all prior identities.

Input Parameters

integer
Page size (1-200, default 50).
string
string
integer
Page offset (default 0).
string
required
string
Window end, exclusive (analytics window grammar).
string
Window start, inclusive (analytics window grammar).
string
Filter to a single event name.
string
The Analytics project the read runs in. Omitted, the workspace’s default project is used.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ANALYTICS_WRITE_KEY_LISTList all writeKeys for the workspace (plaintext never returned on list).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_APPEND_SHEET_VALUESAppend rows of values to a sheet at the first empty row in a range. The server finds the insertion point — no need to read the last row first. Uses OVERWRITE semantics (does not shift existing data).

Input Parameters

string
required
string
A1-style range — Sheet1!A1:D10 or A1:D10.
array
2-D array of row × column values. Capped at 1000 rows per call.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_APPLY_DEAL_TEMPLATECreate a new deal from a saved deal template. The template provides default pipeline, stage, amount, probability, and line items. Use this when starting a deal that matches a known pattern (e.g., ‘Standard Enterprise Plan’).

Input Parameters

string
required
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_APPLY_MASTER_TO_SLIDELink a master slide to a specific slide by 0-based index. The slide stores a by-reference link, retains its existing elements as child-owned content, and clears prior master-element override markers. Current master elements inherit at render time and future master edits flow through automatically.

Input Parameters

string
required
string
required
string
required
Master slide ID to apply.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_APPLY_TASK_TEMPLATECreate a new task by applying a template’s defaults. The template pre-fills status, priority, estimate, assignee, description, and labels. Override any field by passing it explicitly. Title is always required.

Input Parameters

string
required
string ("todo" | "in_progress" | "done" | "cancelled" | "blocked")
System task status category. Drives the built-in board columns.
string
integer
string ("urgent" | "high" | "medium" | "low")
Task priority. Determines SLA timer and sort weight.
string
string
string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_APPLY_TRANSITION_TO_ALLApply a slide transition to every slide in the deck. Set transition.type to ‘none’ to clear transitions on all slides. Prefer duration_s (float seconds, 0.1–10); legacy speed presets map to slow=1.0s, medium=0.5s, fast=0.3s.

Input Parameters

string
required
object
required
Transition applied to every slide. Provide duration_s (seconds, preferred), speed (legacy preset), or duration (legacy ms).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ARCHIVE_MAIL_THREADArchive every inbox-folder message in a thread

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ASSET_GET_CONTENTAn image inside a doc, sheet, slide deck, canvas board, wiki page or task description is an asset of that container, not a Drive file: it never appears in Drive, and it is readable exactly when its container is. Returns the image bytes when the caller can read the container — through the document’s role, the wiki page’s role or the task’s access check, collaborators in other workspaces included. Bytes are proxied, never redirected, with Cache-Control: no-store; an active type such as SVG is served as a download. Every miss is the same 404.

Input Parameters

string
required
The asset id from /api/assets/{id}/content.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ASSIGN_ROLEAssign a role to a user. Requires admin role.

Input Parameters

string
string
required
string
Alias for role.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_AUTH_WHOAMIReturn the current authenticated user’s profile (works with both JWT and API-key auth), including active workspace name + ID and agent kind + manager when applicable. needs_workspace_setup: true indicates the account has no workspace yet.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_AUTOMATIONS_ENQUEUEQueue an enabled automation for background execution. Send a JSON object with an optional payload object containing the trigger data. Returns 202 Accepted with run_id, status and status_url; the Location response header points to GET /api/automations/runs/{run_id}. Poll with the same credential until success, failed, filtered, cancelled or depth_exceeded. The durable scheduler resumes queued work. Dry runs use /api/automations/{id}/test instead; _test_mode is rejected on this endpoint.

Input Parameters

string
required
object
Trigger payload for a manual run. Forwarded verbatim to the manualTrigger node. Shape is workflow-author-defined; downstream nodes reference fields via {var: "<NodeName>.field"} JSONLogic expressions.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_ARCHIVE_EMAILSArchive multiple emails in one atomic call. Moves all specified messages to the archive folder. Use this when the user wants to bulk-archive many emails (e.g., inbox-zero cleanup, archiving all messages from a sender).

Input Parameters

array
required
string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_CLEAR_SHEET_VALUESClear all cell values in multiple ranges atomically. Sets cells to null without removing rows or columns. Useful for resetting template sheets or clearing data regions.

Input Parameters

string
required
array
required
Array of A1-style range specs. Capped at 100 per call.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_FILE_PERMISSIONSBatch-fetch permissions for up to 50 files by ID. Returns a map of file_id → permissions array.

Input Parameters

string
string
string
Comma-separated file IDs (max 50).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_GET_CONTACTSFetch multiple CRM contacts by their IDs in a single request (max 100). Missing or inaccessible IDs are silently omitted from the result.

Input Parameters

string
Comma-separated list of contact UUIDs (max 100).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_GET_DEALSFetch multiple CRM deals by their IDs in a single request (max 100). Missing or inaccessible IDs are silently omitted from the result.

Input Parameters

string
Comma-separated list of deal UUIDs (max 100).
string
Comma-separated embed fields. Supported: line_items.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_GET_FILESBatch-fetch up to 50 files by ID. Powers drive:// embed hydration in Chat/Docs/Wiki/CRM.

Input Parameters

string
Comma-separated file IDs (max 50).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_GET_SHEET_VALUESFetch multiple disjoint ranges from a spreadsheet in a single request. Avoids N sequential round-trips when reading KPIs from different regions.

Input Parameters

string
required
array
required
Array of A1-style range specs. Capped at 100 per call.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_MODIFY_EMAILSBatch modify multiple emails in one atomic call. Can star/unstar, mark read/unread, add/remove labels, and change folder — all at once for up to 500 messages. Use this when the user wants to bulk-update many emails (e.g., star all from a sender, mark a batch as read, apply labels to multiple messages).

Input Parameters

array
Explicit email IDs. Omit when using search_query.
boolean
Alias for mark_read.
boolean
boolean
true trashes; false restores trashed messages to their previous folder, falling back to inbox. With archive=false, a restored archive message also returns to inbox. Folder directives must agree.
string
string
Explicit folder destination. It must agree with archive/trash flags; conflicting directives are rejected before any update.
string
boolean
true archives; false returns archived messages to inbox when no other destination is supplied. Folder directives must agree; contradictions return 400 without writes.
boolean
array
Label IDs or label names.
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
Gmail-style search query — applies the action to every matching email (capped at 500), not just a visible page.
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BATCH_TRASH_EMAILSTrash multiple emails in one atomic call. Moves all specified messages to the trash folder. Use this when the user wants to bulk-trash many emails (e.g., spam cleanup, clearing a project mailbox).

Input Parameters

array
required
string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BLOCK_SENDERBlock a sender (address or domain).

Input Parameters

string ("address" | "domain")
address matches a single email; domain matches any sender at that domain.
string
string
required
boolean
Default true; retroactively trashes matching inbox/archive mail.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BOOK_EVENT_RESOURCESBook one or more resources (rooms, equipment) for an existing event. Returns a conflict error if a resource is already booked.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BROWSE_PUBLIC_CHANNELSBrowse the workspace’s public channels, including the ones the caller has not joined, each with a joined flag and member count. list_channels returns memberships only, so this is the only way to discover a public channel you are not in and get the id chat_channel_join needs. Private channels and DMs are never listed. Use this when the user asks what channels exist, or asks to join a channel by name.

Input Parameters

string
Filter by a substring of the channel name or description, case-insensitive.
string
Max channels to return (default 100, cap 200).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_ARCHIVE_TASKSArchive up to 100 tasks at once. Only archives tasks the caller created or is assigned to.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_COPY_FILESCopy multiple files to a folder (max 100). The destination needs editor access (contributor in a shared drive); a folder the caller cannot see answers 404 like one that does not exist, and a visible one they cannot write to answers 403. A copy into a shared-drive folder belongs to that drive.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_DELETE_CONTACTSDelete many CRM contacts in a single operation. Returns counts of deleted/skipped/failed items.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_DELETE_DEALSDelete many CRM deals at once by their ids.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_DELETE_MESSAGESSoft-delete up to 100 messages in a channel. Deletes only the IDs the caller may delete (own messages, or any message when the caller is a channel admin); every other ID returns in rejected. Emits one bulk message.deleted event, never one per message.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_DELETE_TASKSSoft-delete multiple tasks at once by ID. Only deletes tasks the current user created. Max 100 task IDs per call. Subtasks cascade. Use restore_task to recover individually.

Input Parameters

array
Alias for task_ids.
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_EXPORT_CONTACTSExport selected contacts as CSV or vCard. CSV includes core fields and custom properties; vCard preserves imported RFC 6350 properties and parameters.

Input Parameters

array
required
string
string ("csv" | "vcf")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_EXPORT_DEALSExport selected deals as CSV

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_MOVE_FILESMove multiple files to a folder (max 100). The destination needs editor access (contributor in a shared drive); a folder the caller cannot see answers 404 like one that does not exist, and a visible one they cannot write to answers 403. Per-file failures come back in errors: “File not found” for a file the caller cannot view, “Forbidden” for one they can view but not edit. An item whose sharing is restricted (editors can’t share, on it or a folder above it) moves only with its owner.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_UPDATE_CONTACTSUpdate many CRM contacts in a single operation. Useful for re-assigning ownership, updating lifecycle stage on a list of contacts, or reclassifying industry. Provide an array of contact IDs and the fields to apply to all of them.

Input Parameters

array
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_UPDATE_DEALSUpdate many CRM deals in a single operation. Useful for moving multiple deals to a new stage, reassigning ownership, or marking a batch of deals as won/lost. Provide an array of deal IDs and the fields to apply.

Input Parameters

array
required
string ("open" | "won" | "lost")
Lifecycle of a deal. won and lost close the deal; lost requires a lost_reason.
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_BULK_UPDATE_TASKSUpdate multiple tasks at once by ID. Only updates tasks the current user has access to (creator or assignee). Max 200 task IDs per call. Omit fields you do not want to change. Pass null to clear a nullable field (assignee_id, project_id, due_date, goal_id, task_status_id).

Input Parameters

array
Alias for task_ids.
string ("todo" | "in_progress" | "done" | "cancelled" | "blocked")
System task status category. Drives the built-in board columns.
string
string
string
string
string ("urgent" | "high" | "medium" | "low")
Task priority. Determines SLA timer and sort weight.
array
Tasks to update. Both task_ids and ids are accepted by the route.
string
string
string
array
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_CONFLICTSDetect attendee scheduling conflicts.

Input Parameters

string
string
string
string
string
Comma-separated user IDs.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_EXPORT_ICSExport single event as .ics.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_MEETING_NOTES_CREATECreate a meeting-notes doc for an event, or — when document_id is given — link that existing doc and grant attendees access.

Input Parameters

string
required
string
string
string
Link this EXISTING document to the event as its meeting notes (and grant attendees access) instead of creating a new doc. Used by the @-mention ‘Share & attach’ flow.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_CREATEAdd a reminder to a calendar event.

Input Parameters

string
required
string ("popup" | "email" | "notification")
required
How the reminder fires for the user.
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_LISTList event reminders.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_SETReplace reminder list.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EVENT_UNBOOK_RESOURCESRelease every resource booked for a calendar event.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXPORT_ICSExport entire calendar as .ics.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_AUTH_URLStart external provider OAuth.

Input Parameters

string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CALENDARS_ENABLE_SYNCEnable two-way sync.

Input Parameters

string
required
string
required
Display name for the mirrored calendar
string
Optional calendar color
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
The Google calendar ID to sync
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CALENDARS_LISTList calendars on connection.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CONNECTION_DELETEDisconnect external account.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CONNECTIONS_LISTList connected external accounts.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_FORCE_SYNCSchedule every mirror calendar on this connection for an immediate background pull. Poll the connection’s last_sync_at; completion is any value at or after requested_at.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_EXTERNAL_SYNCED_DISABLEDisable sync for one calendar.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_IMPORT_ICS_URLImport an .ics feed by URL. Fetches the URL server-side and imports its events into the calendar.

Input Parameters

string
required
string
required
Publicly reachable http(s) URL of an .ics feed to fetch and import.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("skip" | "replace_newer" | "create_copy")
How to handle an event whose UID already exists. Defaults to replace_newer.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_REMINDER_DELETEDelete one calendar event reminder by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_RESOURCE_DELETEDelete a bookable calendar resource by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_RESOURCE_GETGet one bookable calendar resource by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_RESOURCES_CREATECreate a bookable resource.

Input Parameters

string
required
string ("room" | "equipment" | "other")
Calendar resource type. Rooms count for capacity; equipment for inventory.
string
string
array
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_RESOURCE_UPDATEUpdate a bookable calendar resource’s details.

Input Parameters

string
required
string
string ("room" | "equipment" | "other")
Calendar resource type. Rooms count for capacity; equipment for inventory.
string
string
array
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDARS_CREATECreate a calendar in the current workspace.

Input Parameters

string
string
string
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDARS_DELETEDelete a calendar and every event on it.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDARS_PERMISSIONS_GETGet a single user’s permission entry on a calendar, including their role, display name, and email. Useful for checking if a specific user has access without listing all permissions.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDARS_UPDATEUpdate calendar fields.

Input Parameters

string
required
string
string
string
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CALENDAR_UPCOMING_REMINDERSReminders due to fire within the next window_hours (default 24, max 168), soonest first. Each row carries the event it is about — title, span, status, location and calendar — so the caller renders the row without a second fetch.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CANCEL_SCHEDULED_EMAILCancel a scheduled email

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CANCEL_SCHEDULED_MESSAGECancel a pending scheduled message so it’s never sent. Use this when the user says ‘never mind’ or changes their plan before the scheduled time.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CANCEL_SCHEDULER_BOOKINGCancel a booking as its host. The booked event is cancelled and the booker is always emailed the cancellation, with the optional message.

Input Parameters

string
required
string
Shown to the booker in their cancellation email.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHANGE_COWORKER_MANAGERReassign the accountable human (manager) for a coworker. Admin-only — the current manager cannot reassign themselves out. Changing manager revokes the coworker’s existing API keys and realtime sessions; the new manager must reconnect it. An unchanged manager keeps keys.

Input Parameters

string
required
string
required
New manager (workspace user id), or null to clear (admin-only after).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_CREATECreate a chat channel in the workspace.

Input Parameters

string
string ("public" | "private" | "dm")
required
public — workspace-wide. private — invite-only. dm — 1:1 or small-group direct message.
string ("conversation" | "notification")
Default notification behavior for new members, independent of channel visibility.
array
Legacy alias for member_ids.
array
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_DELETEDelete a chat channel and its messages.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_GETGet a specific channel by UUID, with members.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_GROUP_REMOVERemove a group from channel (clean up fan-out rows)

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_JOINSelf-join a public channel (no body required)

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_LAST_MESSAGESBatch-fetch the latest message preview for multiple channels in one request. Pass ids as a comma-separated list of channel IDs (max 100). Returns one entry per channel the caller can read, each carrying its channel_id. Replaces per-channel GET /messages?limit=1 calls so a DMs/channels list renders previews without an N+1 request fan-out.

Input Parameters

string
required
Comma-separated channel IDs (max 100) to fetch the latest message preview for.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_LEAVELeave a chat channel you belong to.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_MEMBER_REMOVERemove a member from a chat channel.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_MEMBERS_ADDAdd member(s) or a group

Input Parameters

string
required
string
string
Singular convenience alias — add one member (handler folds it into user_ids).
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_NOTIFICATION_PREFERENCEChoose your channel notification preference, not mute/unmute; use set_channel_muted for that. unread_only (default) surfaces unread activity; all_messages also notifies on unmuted messages. mentions_only shows mention badges; nothing hides channel unread/badge indicators and suppresses keyword and subscribed-thread alerts. Direct mention and broadcast notification delivery remains separate. This does not change the mute indicator or expiry. Per-user; other members are unchanged.

Input Parameters

string
required
string ("unread_only" | "all_messages" | "mentions_only" | "nothing")
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_NOTIFICATION_PREFSUpdate the caller’s per-channel notification preferences (unread_display: count | dot | since_visit).

Input Parameters

string
required
string ("count" | "dot" | "since_visit")
required
How a channel row renders its unread state for one viewer.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_CHANNEL_UPDATEUpdate a chat channel’s name, topic or settings.

Input Parameters

string
required
string
string ("conversation" | "notification")
Default notification behavior for new members, independent of channel visibility.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_DRAFT_CREATE_SAVEDCreate a saved (named) draft for the caller.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_DRAFT_DELETEDelete a draft owned by the caller.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_DRAFTS_LISTThe caller’s chat drafts (inflight + saved), newest first.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_DRAFT_UPDATEUpdate a saved draft owned by the caller.

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_EMOJI_IMAGEServe custom emoji image from GCS

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_MENTIONS_INBOXMessages from other users that @-mention the caller. Powers the Mentions tab.

Input Parameters

string
Max messages to return (default 50, cap 100).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_MESSAGE_DELETEDelete one message from a chat channel.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_MESSAGE_UPDATEEdit message or pin/unpin

Input Parameters

boolean
string
string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
Author correction of the block override after sending.
boolean
Author toggle of the thread-reply channel reshare after sending; true→false un-shares, false→true reshares late.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_PREFERENCESWorkspace-level chat preferences readable by any authenticated member (default_reactions).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_REACTIONS_INBOXMessages authored by the caller that carry reactions from other users. Powers the Mentions & Reactions inbox.

Input Parameters

string
Max messages to return (default 50, cap 100).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SAVED_IDS_LISTGet saved message IDs for a channel (for UI bookmarked state)

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SIDEBAR_CREATE_SECTIONCreate a custom chat-sidebar section for the caller.

Input Parameters

string
required
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SIDEBAR_DELETE_SECTIONDelete a chat-sidebar section owned by the caller.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SIDEBAR_LIST_SECTIONSThe caller’s custom chat-sidebar sections, ordered by position.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SIDEBAR_REORDER_SECTIONSReorder the caller’s chat-sidebar sections.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_SIDEBAR_UPDATE_SECTIONRename a chat-sidebar section or set its channels.

Input Parameters

string
required
string
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_THREAD_ACTIVITY_LISTList thread-activity inbox for the current user. Powers the sidebar “Threads” inbox entry. Returns readable threads the user participates in or explicitly marked unread, with peer-only unread counts and own-inclusive unread anchors.

Input Parameters

string
Max threads to return (default 30, cap 100).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHAT_THREAD_GETGet the replies in a chat message’s thread.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHECK_AVAILABILITYCheck free/busy availability for one or more users in a given time range. Returns busy time slots (not event details) for each user. Use this when the user asks to find a free time, check if someone is available, or schedule a meeting. Call this before create_event to avoid scheduling conflicts.

Input Parameters

string
required
string
required
string
string
string
required
Comma-separated user IDs.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHECK_RESOURCE_AVAILABILITYCheck if a specific resource (room, equipment) is free in a time range. Call before booking to avoid conflicts.

Input Parameters

string
string
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CHECK_WORKSPACE_SLUGCheck whether a workspace slug is available.

Input Parameters

string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CLAIM_DOCUMENTMake an unclaimed document yours. A document, spreadsheet, presentation or board created without an account returns a single-use claim_key; call this with it after signing in and the document moves into your active workspace with you as owner, keeping its id and URL. Its link drops to view-only, which you can raise again. A second claim of the same document, or a wrong key, is refused with 409 claim_rejected, which does not say which.

Input Parameters

string
required
string
required
The claim key returned when the document was created without an account.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CLEAR_CALENDARDelete ALL events from a calendar. Owner-only — use for resetting shared calendars at quarter boundaries or wiping test data. Returns the count of deleted events. This is irreversible.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CLEAR_REMINDERClear a pending reminder on a saved message. The message stays saved; only the reminder is removed.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CLEAR_SHEET_VALIDATIONRemove a data validation rule from a spreadsheet by range. The range is matched after normalization (sheet tab defaults to Sheet1 if not specified). Returns 404 if no rule exists for that range.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CLEAR_USER_STATUSClear the current user’s status (emoji + text + expiresAt). Does NOT change DND — use set_user_dnd with until=null to clear DND separately.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_COMMENT_UPDATEEdit or delete an owned comment; maintainers may delete published comments. Concurrent edits require the last observed body. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
boolean
object
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_CONNECTIONS_LISTList repositories offered by the workspace GitHub installation. Workspace administrators only.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_AUTO_MERGEEnable or cancel durable Code auto-merge using the PR review policy and GitHub checks. Requires merge authority and the last read version. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string ("squash" | "merge" | "rebase")
string
boolean
required
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_CHANGES_SINCE_REVIEWCompare the caller’s last reviewed head with the current head. Historical or truncated source is explicitly reported.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_COMMENTStart a discussion or reply to a thread. Inline comments retain their original revision and source excerpt. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
required
object
string
string
boolean
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_COMMITRead the diff for one commit in this pull request.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_CREATECreate or adopt a GitHub pull request with an accountable Ambiguous author. An omitted base uses the repository’s default target branch. Retries use the same idempotency key. autoMerge arms auto-merge on the new pull request in the same call, so it needs no version and cannot race the first check update; it requires merge authority on the repository and is ignored when the key or number returns an existing Code pull request. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
string
string
boolean
string
string
string
integer
object
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_EXPORTExport the complete review record with original anchors and attribution as versioned JSON or Markdown.

Input Parameters

string
required
string
string ("json" | "markdown")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_GETRead a native review, its revision, discussion, checks and merge blockers. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_MERGEMerge the confirmed pull request version into its existing target after fresh revision, authorization, review-policy and GitHub checks. No target branch is accepted. The provider confirms the outcome; uncertain requests remain pending. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string ("squash" | "merge" | "rebase")
string
string
required
string
required
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_REFRESHReconcile with current GitHub state. Never interprets an older webhook as current source truth. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_REVIEWSubmit a review for the specified comparison as an authenticated user or agent with repository review permission. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
string
required
string
required
string
required
string ("approved" | "changes_requested")
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULLS_LISTPermission-filtered pull request inbox.

Input Parameters

string ("all" | "needs_review" | "mine" | "following" | "assigned" | "involves")
string ("open" | "closed" | "merged" | "all")
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_PULL_UPDATEEdit metadata, assign reviewers, follow, close, reopen or mark ready. Requires the last read version. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
boolean
string ("open" | "closed")
string
string
array
boolean
string
integer
required
boolean
string
object
array
array
string ("approved" | "approved_or_resolved")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
object
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
Slug: AMBIGUOUS_MCP_CODE_REPOSITORIES_LISTList repositories the caller can read, with their Code role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_COMPARECompare two repository refs before opening a pull request.

Input Parameters

string
required
string
required
string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_CONNECTConnect a repository from this workspace’s existing GitHub installation. Workspace admin only; grants the connector repository ownership.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_GRANTGrant or revoke a workspace user or team. Null role revokes. Repository owner only.

Input Parameters

string
required
string
required
string
required
string ("user" | "team")
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_GRANTSRead repository access grants. Repository owner only.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_METADATARead the repository labels and milestones available for pull requests.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_PRINCIPALSList workspace users and teams available for an explicit repository grant. Repository owner only.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_REVIEWERSList currently eligible Ambiguous reviewers, including agents.

Input Parameters

string
required
string
string
string ("all")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REPOSITORY_UPDATEUpdate the default target branch, review policy or connection. A null target resets to GitHub’s default branch. Repository owner only.

Input Parameters

string
required
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
array
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REVIEW_DISMISSDismiss a blocking review with an auditable reason. Maintainer only. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CODE_REVIEW_RESOLVEResolve or reopen a review without changing its verdict. The PR author or maintainer may resolve another reviewer’s feedback. The response carries every file patch, thread and activity entry. Pass fields to return only what you need, for example id,version,blockers,data(autoMerge,mergeIntent,syncError,provider(state,headSha,baseSha,baseRef,mergeable,checks)).

Input Parameters

string
required
string
string
string
required
string
required
string
required
boolean
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COMPUTE_PIVOT_TABLECompute the result of a persisted pivot table — applies row/column grouping, value aggregation, sort orders, and any matching slicer filters, and returns the rendered cells. The pivot config itself (row/column/value fields, source range) is not modified.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COMPUTE_WIKI_ROLLUPSCompute and return rollup values for all rows in the database. Each rollup aggregates a property across related rows.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COPY_SHEET_TOCopy a sheet tab from one spreadsheet to another. Deep-copies columns, rows, formulas, formatting, and merges. Cross-document formulas will show as #REF!. Requires viewer access on source and editor access on destination.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
string
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_CONVERSATION_GETProxy (workspace-isolated): get a single conversation thread.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_CONVERSATIONS_LISTProxy (workspace-isolated): list conversations for the coworker in the active workspace.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_EXECUTION_CANCELKill switch: cancel an in-flight execution. Flips an active (PENDING/RUNNING/PAUSED) coworker_executions row to CANCELLED; the coworker’s execution loop aborts at its next action-call boundary. Idempotent no-op on an already-terminal execution.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_EXECUTION_GETGet one execution with full trace data — task row, parent/children lineage, conversation, reasoning cycles, and tool-call activities. Powers the Execution Trace debug view.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_EXECUTIONS_LISTProxy: list coworker execution history (paginated).

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_ADDProxy (workspace-isolated): start monitoring a channel.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_LISTProxy (workspace-isolated): list channels the coworker is monitoring.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_REMOVEProxy (workspace-isolated): stop monitoring a channel.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_ARCHIVEArchive a playbook. Archived playbooks are hidden from lists and cannot be selected during dispatch, but remain linked to historical executions for audit.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_CREATECreate a playbook and its initial version. instructions and subtasks seed version 1, which becomes the current version.

Input Parameters

string
required
string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_DELETEDelete a playbook and its versions. Returns 409 if any coworker_executions still reference the playbook — use the archive endpoint to retire it instead.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_GETGet one playbook with its current version’s instructions and subtasks.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_LISTList the coworker’s playbooks (metadata + current version pointer).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_UPDATEEdit playbook metadata in place (title, objective). Instructions and subtasks are immutable — create a new version instead.

Input Parameters

string
required
string
string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_CREATEAppend a new version. Auto-increments the version number and marks the new version current. Prior versions stay readable for audit.

Input Parameters

string
required
string
string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_GETGet one historical version’s instructions and subtasks.

Input Parameters

string
required
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_LISTList all versions of a playbook, newest first.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_COWORKERS_ROTATE_TOKENRotate the management token used to talk to the coworker service.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CANVASCreate a new (empty) canvas — a Miro-style infinite whiteboard. Use when starting a fresh flowchart, product map, or swimlane flow; returns the canvas envelope with an empty data.elements, then add objects with create_canvas_element. Coordinates: board units, top-left origin, +x right / +y down. Example: create_canvas({ title: “Q1 product map” }) → { id: “<boardId>”, data: { elements: [] } }.

Input Parameters

string
Board title. Defaults to ‘Untitled’.
string ("restricted" | "workspace" | "link" | "public")
Initial visibility. Defaults to ‘restricted’.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CANVAS_ELEMENTAdd one element to a board — a sticky, text, shape, image, codeBlock, frame, swimlane, connector, or metric. Use when placing a new object; to attach a connector so it re-routes when shapes move, set each endpoint to an existing element id with an anchor (n/s/e/w) — free-form points stay fixed and never follow a move, so use them only for unattached lines. Provide type and geometry; the server mints the element id and returns it, and every other element on the board is untouched. Fields are flat, never nested under element, and id is the board. Send only the fields of that type: sticky and text take content; shape takes shape and content; image takes src; codeBlock takes code and language; frame takes name and an optional metricWindow; metric takes report (insights:<id> or funnels:<id>, a saved analytics report), optional step, title and window ({ from, to } like today-28d / now) and renders that report’s live value; connector takes from and to as { element, anchor } or { point: { x, y } }, with x,y,w,h all 0. Coordinates: board units, top-left origin, +x right / +y down — pass x,y (the element’s top-left corner) with w,h. Example: create_canvas_element({ id: “<boardId>”, type: “sticky”, x: 100, y: 80, w: 160, h: 120, content: “Idea” }).

Input Parameters

number
required
Height in board units.
number
required
Width in board units.
number
required
Board x (top-left). +x right.
number
required
Board y (top-left). +y down.
number
Paint order (Arrange front/back): higher paints on top, undefined = 0.
string
required
Canvas board id.
object
type connector only.
string
The image’s container asset URL (/api/assets/<asset-id>/content); older boards may carry a Drive reference (drive://<file-id>). type image only.
string
Plain source text on the wire. type codeBlock only.
object
type connector only.
Navigational target (Link to…): same-board element ref or a URL.
string
type frame only.
integer
type metric only.
string
required
object
type connector only.
array
type swimlane only.
string ("straight" | "elbow" | "curved")
type connector only.
string ("rect" | "roundedRect" | "ellipse" | "diamond" | "parallelogram" | "cylinder")
type shape only.
object
string
type metric only.
boolean
A locked element rejects geometry/content mutation until unlocked.
string
The saved analytics report the tile reads, as insights:<id> or funnels:<id>. type metric only.
object
type metric only.
string
The element’s text: a plain string (“Ship the beta”), or ProseMirror document JSON for formatting. type shape, sticky, text only.
string
Owning frame id when the element lives inside a frame.
string
Group membership; elements sharing a groupId move/rotate/delete as a unit.
object
type image only.
string ("none" | "arrow")
type connector only.
string
type codeBlock only.
number
Degrees about the element’s center.
boolean
type metric only.
boolean
type metric only.
string ("none" | "arrow")
type connector only.
string ("horizontal" | "vertical")
type swimlane only.
object
type frame only.
number
type frame only.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CHARTEmbed a chart on a tab of the sheet. Charts visualize a rectangular data range — pick a chart type (bar / line / pie / scatter), the source range, and an overlay position. Returns the created chart with its server-assigned id.

Input Parameters

number
number
string
required
string
Tab name where the chart lives. Defaults to the first tab.
object
string ("bar" | "stackedBar" | "line" | "area" | "pie" | "donut" | "scatter" | "combo")
required
string
required
number
number
object
object
required
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CONTACTCreate a new CRM contact (person or company). Persons can be linked to a company via company_id. IMPORTANT: Before creating a contact, ALWAYS call list_contacts with a search query (q) to check if a contact with the same name or email already exists. If a matching contact is found, use update_contact instead of creating a duplicate. Only create a new contact if no match is found. Use this when the user asks to add a contact, log a lead, or create a company record.

Input Parameters

string
string ("person" | "company")
person is a human contact; company is the organisation entity.
string
string
string
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CONTACT_GROUPCreate a named contact group for organizing contacts. Groups allow overlapping membership — a contact can be in multiple groups.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CRM_PROPERTY_DEFINITIONDefine a typed custom property for contacts or deals. field_type ‘relation’ (with relation_target contact|company|deal) makes the property a link to another record: values written to custom_properties under this key must be the id of an existing record of the target type.

Input Parameters

string
required
string
required
array
boolean
string ("text" | "number" | "select" | "multi_select" | "date" | "checkbox" | "url" | "email" | "phone" | "relation")
required
number
string ("contact" | "company" | "deal")
required
string ("contact" | "company" | "deal")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_CRM_VIEWCreate a saved CRM view: a named filter+sort preset for contacts, companies, or deals. Useful when the user asks to ‘save this filter’ or ‘create a view for high-value deals’.

Input Parameters

string
required
object
boolean
boolean
string
string ("contacts" | "companies" | "deals")
required
Which list page the saved view applies to.
string ("asc" | "desc")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_DATA_CONNECTORCreate a new data connector that fetches data into specific cells of a sheet. After creating, call run_data_connector to execute it.

Input Parameters

string
required
string
string
object
string
string
number
number
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_DEALCreate a new CRM deal (revenue opportunity). Deals belong to a pipeline and sit in a specific stage. Link to a contact and/or company. Use this when the user asks to create a deal, log an opportunity, or start tracking a sale.

Input Parameters

string
required
string
string ("open" | "won" | "lost")
Lifecycle of a deal. won and lost close the deal; lost requires a lost_reason.
string
string
string
string
string
string
string
string
integer
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
Alias for contact_id. Either is accepted; sending both with different values returns 400.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_DEAL_TEMPLATECreate a deal template — a reusable preset for creating deals with standard pipeline/stage/amount and line items. Use when the user has a repeatable sale like ‘Standard Enterprise Plan’.

Input Parameters

string
required
string
string
string
boolean
array
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Slug: AMBIGUOUS_MCP_CREATE_DOCCreate a new doc. content is Markdown (recommended) or a ProseMirror JSON string. Returns the created document; read, update, share and trash it through the /api/documents/{id} operations. For a spreadsheet use create_sheet, for a deck create_presentation, for a whiteboard create_canvas.

Input Parameters

string
array
string
Doc body. Accepts Markdown (recommended) or a ProseMirror JSON string. HTML is tolerated best-effort: a tag the editor schema maps becomes its node or mark, so <b>x</b> stores x in bold. A tag it does not map is kept as literal text, attributes and closing tag verbatim, so <display-slug> survives a round trip. Styling and decorative wrappers are still dropped and are listed in import_warnings on the response. To insert a native smart chip (the live-status chip the editor inserts), write @{task:<task-uuid>} in Markdown; doc, sheet, slide, canvas and wiki_page ids work the same way, and the chip takes the entity’s title when you can read it. Wrap a token in backticks to keep it as text.
object
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Shared drive to create the doc in; omit for My Drive.
string
Drive folder to create the doc in.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_DRAFT_EMAILCreate a draft email without sending it. The draft is saved in the drafts folder for later review, editing, or sending. Use this when the user wants to compose an email for later, save a draft, or prepare a message without sending it immediately.

Input Parameters

array
array
Empty drafts allowed; required when sending.
array
string
array
string
string
string
string
HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text.
string
Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent.
string
Attach the message to an existing thread.
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
array
array
string
string
Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send.
array
Drive file IDs to attach.
string
Optional retry key. Reusing the same key with the same send request returns the original send.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_EVENTCreate a new calendar event. Requires a title, start time, and end time. Optionally add a description, location, attendees, recurrence, and more. Use this when the user asks to schedule a meeting, add an event, or book time. If the user doesn’t specify a calendar, use list_calendars to find their default calendar ID first.

Input Parameters

string
boolean
Allow creating an event in the past.
string
required
string
required
array
The event’s outside guests by email. On create it adds them; on update it replaces the outside-guest list (members are unaffected). An address a workspace member owns becomes a member guest instead.
string ("confirmed" | "tentative" | "cancelled" | "outofoffice")
Event status. outofoffice is used by the OOO responder.
boolean
string
string
string
required
array
Everyone on the event. Each entry is a string (UUID or email) or an iCal-natural object naming the attendee via email, id, or user_id; any other object key is ignored. An object with none of those three returns 400. An email no workspace member owns becomes an outside guest (returned in guests); it never creates a workspace invitation.
string
string
string ("default" | "outOfOffice" | "focusTime")
Calendar event type — a display/filter category. It does not change event behavior: OOO auto-decline keys on status: "outofoffice", and free/busy keys on transparency (independent inputs). The one behavioral value is agentDispatch, which routes a confirmation task to the assignee on create.
string ("default" | "public" | "private")
Visibility scope for the event.
string
required
string
array
Resources (rooms/equipment) to book for the new event; booked server-side after insert.
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string ("opaque" | "transparent")
Free/busy classification (RFC 5545 TRANSP). opaque = Busy (default; blocks availability). transparent = Free (e.g. focus time).
string
Video-call URL. Accepts explicit http(s) or a schemeless hostname/path, which is stored as absolute HTTPS. Any other scheme is rejected 400. Empty string or null clears the link and provider.
array
Existing-event ids the new_and_existing bulk-decline should leave untouched.
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
boolean
string ("new_only" | "new_and_existing")
OOO auto-decline granularity (only meaningful when status=outofoffice). new_only declines invitations arriving during the window; new_and_existing also bulk-declines events already attended.
boolean
string
string
Auto-reply note sent with an OOO decline.
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
Slug: AMBIGUOUS_MCP_CREATE_FOLDERCreate a new folder in Drive. Returns the created folder with id, name, and path. Use this when the user asks to create, make, or add a new folder for organizing files. Supports nested folders via parent_folder_id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_FORMCreate a new form for collecting data (surveys, feedback, registrations, quizzes). Returns the created form with id and public slug. Use this when the user asks to create a survey, questionnaire, feedback form, registration form, or any structured data collection. Define fields with types, labels, validation, and optional conditional logic.

Input Parameters

string
string
array
object
Alternative to fields — pass {fields: [...]} instead.
object
string
boolean
Publish the form immediately on create.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_FORM_VARIANTCreate a new A/B test variant by duplicating the parent form. Optionally override fields to change question wording, field types, options, or validation. Traffic weight (0–100) controls the percentage of visitors who see this variant versus the control. Use when the user asks to set up an A/B test or add a variant.

Input Parameters

string
required
string
array
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_MAIL_LABELCreate a mail label for organizing threads.

Input Parameters

string
required
string ("red" | "orange" | "yellow" | "green" | "blue" | "purple" | "pink" | "cyan" | "gray")
Built-in label palette.
string
string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_MAIL_RULECreate a mail rule that acts on matching messages.

Input Parameters

string
required
array
required
boolean
array
required
string ("all" | "any")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_MAIL_TEMPLATECreate a reusable mail template for composing.

Input Parameters

string
required
string
required
string
string
HTML import normalized to Markdown when body_markdown is absent; wins over body_text.
string
Literal plain-text body normalized to Markdown when Markdown/HTML are absent.
string
Canonical Markdown body; wins over HTML/text even when explicitly empty.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_NAMED_RANGECreate a named range or named expression on a spreadsheet. Send either an A1 range or an exact literal Excel expression, such as a structured table reference. External-workbook expressions are preserved verbatim and remain unresolved.

Input Parameters

string
required
string
required
string
string
string ("fixed" | "caller-relative-a1")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PIPELINECreate a new CRM pipeline with ordered stages. Each stage has a name and an optional default probability (0-100). Most workspaces need only one pipeline; create additional ones for distinct sales processes (e.g., ‘New Business’ vs ‘Renewals’).

Input Parameters

string
required
array
Ordered pipeline stages as a JSON array of objects, each {name, probability?} where probability is the win-odds 0-100. Stage order follows array position; an optional sort_order is accepted for symmetry with update but ignored. Example: [{“name”:“Lead”,“probability”:10},{“name”:“Qualified”,“probability”:40},{“name”:“Won”,“probability”:100}]
boolean
string ("workspace" | "private")
workspace (default) shares the pipeline’s deals with the whole workspace via the Everyone team; private scopes deals to explicit pipeline members.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PIVOT_TABLECreate a pivot table from sheet data. A new sheet tab is automatically created to hold the pivot. Specify the source data range, which columns to group by (rows/columns), and which columns to aggregate (values).

Input Parameters

string
required
string
array
string
array
array
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PRESENTATIONCreate a new presentation deck. Omit content for a deck with one blank slide, or pass deck JSON to create it with its slides in place: { slides: [{ elements: [{ type: "text", x: 80, y: 60, w: 800, h: 80, text: "Q1 review", fontSize: 44 }] }] }. A slide is 960 by 540 units with a top-left origin, and elements take the shape add_slide accepts. Returns the created SlideDeck envelope.

Input Parameters

string
Title for the new deck. Defaults to ‘Untitled’ if omitted.
string
Optional deck JSON: { settings?, slides: [{ elements, background?, notes?, layout? }], masterSlides? }. A string is parsed as JSON; Markdown is not accepted. Omit for a deck with one blank slide.
string ("restricted" | "workspace")
Initial visibility. Defaults to ‘restricted’.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Shared drive to create the deck in; omit for My Drive.
string
Drive folder to create the deck in.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PRODUCTCreate a product in the workspace catalog. Products are the reusable items that can be attached to deal line items and quote line items. Set is_active=false to retire without deleting.

Input Parameters

string
string
required
string
boolean
number
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("one_time" | "monthly" | "quarterly" | "yearly")
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PROJECTCreate a new project to group related tasks. Use this when the user asks to start a new project or create a container for tasks.

Input Parameters

string
string
required
string
string ("private" | "team" | "workspace")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("fibonacci" | "linear" | "t-shirt")
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_PROJECT_UPDATEPost a status update on a project. Use this when the user wants to report progress, flag a risk, or share a status update on a project. The status field captures the health signal (on_track, at_risk, off_track, paused, completed, cancelled).

Input Parameters

string
string ("on_track" | "at_risk" | "off_track" | "paused" | "completed" | "cancelled")
required
Latest status update on the project. null when no updates have been posted.
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_QUOTECreate a CRM quote (proposal) with line items. Auto-computes subtotal, tax, discount, and total. Link to a deal/contact/company via IDs. Status defaults to ‘draft’ — use send_quote to email it.

Input Parameters

string
string
string
required
string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired")
Quote lifecycle. accepted/rejected are terminal; viewed is recorded by the open-tracking pixel.
string
string
string
number
string
string
array
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_RESOURCE_COMMENTCreate a comment on a document, task, wiki page, mail conversation, pull request, or code review. Replies use parent_id. Documents, wiki pages and Code support anchor; documents, tasks, wiki pages and Code support idempotency_key. Unsupported fields are rejected by the owning module. Mail comments are internal notes and cannot be sent as email.

Input Parameters

string
required
string
string
string
string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_ROLECreate a custom role with specific permissions. Requires admin role.

Input Parameters

string
required
string
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SCORING_RULECreate a lead scoring rule. When a contact matches (field + operator + value), the specified points are added to their lead score. Positive points indicate engagement; negative points indicate disqualification signals.

Input Parameters

string
required
string
required
string
integer
required
string ("equals" | "not_equals" | "contains" | "not_contains" | "is_set" | "is_not_set" | "greater_than" | "less_than")
required
Comparison operator for a lead-scoring rule.
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SEQUENCECreate a multi-step CRM sequence (email/wait/task/call/branch steps). Use this when the user asks to build a nurture campaign or outreach cadence.

Input Parameters

string
required
array
required
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SHARED_DRIVECreate a shared drive. Creator becomes a manager.

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SHEETCreate a new spreadsheet. Returns the full Sheet envelope (id, title, owner, visibility, timestamps, and data body) so the caller can immediately read or edit cells without a second round-trip. Optional content may be a SheetData JSON object or a string that parses as JSON.

Input Parameters

string
Optional title. Defaults to ‘Untitled’ when omitted.
array
string
Optional initial SheetData (JSON canvas). String is parsed as JSON server-side; object is stringified.
string ("restricted" | "workspace" | "link" | "public")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Shared drive to create the sheet in; omit for My Drive.
string
Drive folder to create the sheet in.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SHEET_IMAGECreate editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

Input Parameters

string
required
string
integer
required
integer
required
string
required
string
number
required
number
required
number
required
number
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SHEET_PICTURE_GROUPCreate editable picture groups with cell anchors and CSS pixel geometry. Every leaf references an image asset owned by this sheet; native group transforms use EMU coordinates.

Input Parameters

string
required
string
integer
required
integer
required
string
string
required
number
required
number
required
number
required
number
required
number
required
number
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SHEET_SHAPECreate editable floating shapes with editable text, cell anchors and CSS pixel geometry.

Input Parameters

string
required
integer
required
integer
required
string
string
required
string
string ("rect" | "ellipse")
required
number
required
number
required
string
number
required
number
required
number
number
string ("left" | "center" | "right")
string
string
string
string ("standard" | "excel")
number
number
number
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SIGN_DOCUMENTCreate a draft signing document.

Input Parameters

string
string
string
string ("pdf" | "doc")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("parallel" | "sequential")
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SIGN_TEMPLATECreate a reusable signing template from field layout and signer roles.

Input Parameters

string
required
array
string
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SLICERAdd a slicer to a tab of the sheet. Slicers filter pivot tables and charts that share the same source range by the values selected for a single column. selectedValues: null passes everything through; [] filters everything out; a non-empty array passes only those values. Returns the created slicer with its server-assigned id.

Input Parameters

number
number
string
required
string
Tab name where the slicer lives. Defaults to the first tab.
string
number
number
string
required
boolean
object
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SLIDE_MASTERCreate a new master slide for a deck. If no elements are provided, a default Title + Subtitle layout is used.

Input Parameters

string
required
string
array
string
Slide background color, for example “#0F1B33”.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_SUBTASKCreate a subtask under the given parent task. Equivalent to POST /api/tasks with parent_task_id pre-filled from the URL parameter.

Input Parameters

string
required
string
required
Task title. Required. Max 255 chars; trimmed before insert.
string ("todo" | "in_progress" | "done" | "cancelled" | "blocked")
Initial status. Defaults to todo. If task_status_id is also set, that takes precedence and status is overridden by the custom status’s category.
string
Link the task to a CRM deal.
string
Link the task to an OKR-style goal.
string
Sprint/cycle this task is scheduled in.
string
ISO 8601 date (YYYY-MM-DD). If unset and a priority is given, the SLA policy auto-sets a due date and stamps due_date_source: 'sla'.
integer
Story-point estimate (typically 1, 2, 3, 5, 8, 13).
string ("urgent" | "high" | "medium" | "low")
Defaults to medium.
array
Labels to assign at create time. Each ID must reference a label in the caller’s workspace (404 otherwise).
string
Link the task to a CRM contact; auto-logs a CRM activity row.
string
number
Drag-reorder weight. Lower sorts first.
string
ISO 8601 date (YYYY-MM-DD); with due_date defines a date range.
string
User to assign the task to. Must be in the caller’s workspace (403 otherwise). Omit for unassigned.
string
Stringified ProseMirror JSON for the rich description. Legacy plain text and Markdown remain readable.
string
Parent task for subtasks. Omit for top-level tasks.
array
Users to subscribe to the task at create time so they receive update notifications. Each must be a member of the caller’s workspace; IDs outside the workspace are silently skipped. Use to link a bug reporter to the filed task.
string
Custom status ID; overrides status category.
string
Stable caller key for one creation request. Matching retries return the same task; different content with the same key is rejected.
string
RFC 5545 RRULE string. When set, completing the task spawns the next occurrence.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
Time-budget estimate in minutes.
object
Per-task custom-field values keyed by task_custom_fields.id.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_TASKCreate a new task. Auto-subscribes the creator and (if assigned) the assignee. Auto-sets SLA due date when priority is set without an explicit due_date. Auto-logs a CRM activity if linked to a contact.

Input Parameters

string
required
Task title. Required. Max 255 chars; trimmed before insert.
string ("todo" | "in_progress" | "done" | "cancelled" | "blocked")
Initial status. Defaults to todo. If task_status_id is also set, that takes precedence and status is overridden by the custom status’s category.
string
Link the task to a CRM deal.
string
Link the task to an OKR-style goal.
string
Sprint/cycle this task is scheduled in.
string
ISO 8601 date (YYYY-MM-DD). If unset and a priority is given, the SLA policy auto-sets a due date and stamps due_date_source: 'sla'.
integer
Story-point estimate (typically 1, 2, 3, 5, 8, 13).
string ("urgent" | "high" | "medium" | "low")
Defaults to medium.
array
Labels to assign at create time. Each ID must reference a label in the caller’s workspace (404 otherwise).
string
Link the task to a CRM contact; auto-logs a CRM activity row.
string
number
Drag-reorder weight. Lower sorts first.
string
ISO 8601 date (YYYY-MM-DD); with due_date defines a date range.
string
User to assign the task to. Must be in the caller’s workspace (403 otherwise). Omit for unassigned.
string
Stringified ProseMirror JSON for the rich description. Legacy plain text and Markdown remain readable.
string
Parent task for subtasks. Omit for top-level tasks.
array
Users to subscribe to the task at create time so they receive update notifications. Each must be a member of the caller’s workspace; IDs outside the workspace are silently skipped. Use to link a bug reporter to the filed task.
string
Custom status ID; overrides status category.
string
Stable caller key for one creation request. Matching retries return the same task; different content with the same key is rejected.
string
RFC 5545 RRULE string. When set, completing the task spawns the next occurrence.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
Time-budget estimate in minutes.
object
Per-task custom-field values keyed by task_custom_fields.id.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_TEAMCreate a new team in the workspace. The caller becomes the team admin. Teams can serve as email distribution lists (when email_local_part is set) and/or permission targets. Use this when the user asks to create a team, distribution list, or mailing list.

Input Parameters

string
string
required
string
string
string ("public" | "private")
string
string ("open" | "request" | "invite")
string
string ("open" | "members_only" | "admins_only")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_WIKI_PAGECreate a new wiki page within a space. Pages use Markdown content and support nested hierarchies via parent_page_id. Use this when the user asks to create a wiki page, add documentation, write a runbook, or add to the knowledge base. Call list_wiki_spaces first to get the space ID.

Input Parameters

string
required
string
string
string
required
string
Page content as Markdown string or ProseMirror JSON object.
number
string
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Legacy alias for content.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_WIKI_PAGE_VERSIONCreate a manual snapshot of the current wiki page state. Useful before a risky edit or when the user wants to mark a ‘known good’ checkpoint. Optional label names the snapshot. Returns the new version’s id + metadata.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_WIKI_SPACECreate a new wiki space (a top-level container for pages). Use this when the user asks to create a new knowledge base area, team wiki, or documentation section. Spaces organize pages by team or domain (e.g., ‘Engineering’, ‘Product’, ‘Company Handbook’).

Input Parameters

string
string
required
string
boolean
string ("restricted" | "workspace" | "link" | "public")
Space/page visibility. restricted = invitees only. workspace = any workspace member. link = anyone with the link. public = indexable.
string
string ("viewer" | "commenter" | "editor")
Role the Everyone-team row grants when visibility is workspace.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_WIKI_SYNCED_BLOCKCreate a synced block — a reusable content fragment that can be embedded in multiple wiki pages and stays in sync everywhere it’s used. Returns the new block’s id. Use this when the user asks to create a shared snippet, reusable callout, or cross-page content.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CREATE_WORKSPACE_INVITECreate workspace invites. With no recipient it mints a generic shareable invite link (returned as invite_url) and emails nobody; with recipients it creates one invite per address and emails each. Role defaults to member and is forced to member for any value other than admin.

Input Parameters

string
admin or member. Defaults to member; any other value becomes member.
string
One recipient to invite by email.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_CONTACT_FILE_ATTACHAttach a Drive file to a contact. The file becomes readable by every workspace member who can read the contact, so a file you do not own needs the share right on it (403 file_attach_requires_share when you can only view it).

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_CONTACT_FILE_DETACHDetach a file from a contact

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_CONTACT_FILES_LISTList files attached to a contact

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_CONTACT_PHOTO_GETServe the photo image stored for a CRM contact.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_DEAL_ACTIVITIESList activities for deal (owner-scoped)

Input Parameters

string
required
string ("note" | "call" | "email" | "meeting" | "task" | "chat")
Activity timeline event type. Used for filtering and badges in the UI.
integer
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_DEAL_FILE_ATTACHAttach a Drive file to a deal. The file becomes readable by everyone who can read the deal, so a file you do not own needs the share right on it (403 file_attach_requires_share when you can only view it).

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_DEAL_FILE_DETACHDetach a file from a deal

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_DEAL_FILES_LISTList files attached to a deal

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CRM_QUOTE_PDFExport quote as PDF (or printable HTML with ?format=html)

Input Parameters

string
required
string
string ("html" | "pdf")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_ADD_TASKSAdd tasks to the cycle. Body {task_ids: [...]}.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_ANALYTICSBurndown + summary analytics for the cycle.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_COMPLETEComplete a cycle. If auto_rollover is set, incomplete tasks are moved to the next cycle.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_CREATECreate a new cycle. Body fields: name, start_date, end_date, status?, cooldown_days?, auto_rollover?.

Input Parameters

string
string
string
string
boolean
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_DELETEDelete a cycle. Tasks attached to the cycle are unlinked, not deleted.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_GETGet one task cycle and its dates by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_LISTList cycles in the active workspace. ?status= filters by status; ?limit= (1–200) and ?offset= paginate. has_more is set when the underlying query returned a hint of more rows.

Input Parameters

string
string
string
string
string ("planned" | "active" | "completed" | "cancelled")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_REMOVE_TASKSRemove tasks from the cycle. Body {task_ids: [...]}.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_UPDATEUpdate cycle fields.

Input Parameters

string
required
string
string
string
string
boolean
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_CYCLES_VELOCITYCross-cycle velocity (last N closed cycles). Default limit=10.

Input Parameters

string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DECIDE_ACCESS_REQUESTApprove an open access request at a named role, or decline it. Only principals entitled to share the resource may decide. Returns 409 once decided.

Input Parameters

string
required
string ("viewer" | "commenter" | "editor" | "member")
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DECIDE_MAIL_APPROVALApprove and send, request changes, reject, or (as the sender) withdraw one submitted email. The decision names the revision it applies to: exactly one decision per revision succeeds, and a decision on a superseded revision conflicts rather than releasing content the caller has not read. Approving records the human and time against that revision; it authorizes nothing else — not the thread, not a reply, not a later email.

Input Parameters

string
required
string
Surfaced to the sender — the reason on Request changes or Reject.
string ("approved" | "changes_requested" | "rejected" | "withdrawn")
required
The outcome asked for. withdrawn is the SENDER’s retraction; the other three are the reviewer’s.
integer
required
The revision this decision applies to. A decision never applies to another one — if the sender has withdrawn and resubmitted since you read it, this conflicts rather than releasing content you have not seen.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_ACTIVITYDelete one logged CRM activity by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CANVAS_ELEMENTDelete one element from a board by id. Use when removing an object; connectors attached to it are not auto-deleted, so patch or delete those separately. Every other element is untouched. Coordinates: board units, top-left origin, +x right / +y down (unchanged by a delete). Example: delete_canvas_element({ id: “<boardId>”, elId: “<elId>” }).

Input Parameters

string
required
Canvas board id.
string
required
Element id within the board.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CHARTRemove a chart from the sheet. Returns { deleted: true } on success.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CONDITIONAL_FORMATDelete a conditional formatting rule from a spreadsheet by its ID. Returns 200 on success, 404 if the rule does not exist.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CONTACTDelete a CRM contact (owner-scoped). Permanently removes the contact record. Use with caution — prefer updating lifecycle_stage to ‘evangelist’ or archiving via merge instead.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CONTACT_GROUPDelete a contact group. Memberships are removed but contacts themselves are preserved.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CONTACT_PHOTODelete a CRM contact’s profile photo. Clears the avatar_url and removes the stored image.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_COWORKERDelete a coworker (revokes API key + tears down config).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CRM_PROPERTY_DEFINITIONDelete a custom-property definition. Existing custom_properties values are left in place; they simply stop being typed.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CRM_VIEWDelete a saved CRM view.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_CUSTOM_EMOJIDelete a custom emoji from the workspace. Use this when the user asks to remove or clean up a custom emoji. This does not remove existing reactions or messages that used the emoji — it only stops new usage.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_DATA_CONNECTORDelete a data connector. Does not affect the cells it previously wrote to.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_DEALDelete a CRM deal (owner-scoped). Permanently removes the deal record and its line items. Prefer updating status to ‘lost’ with a lost_reason for reporting purposes.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_DEAL_LINE_ITEMDelete a deal line item. By default the deal’s total amount is re-synced after deletion.

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("true" | "false")
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_DEAL_TEMPLATEDelete a deal template (does not affect deals previously created from it).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_DOCUMENT_VERSIONDelete a version snapshot of a document. At least one version must always remain — returns an error if attempting to delete the last version. Requires editor permission.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_EMAILDelete one email message by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_EVENTDelete a calendar event. This is a destructive action — always confirm with the user before calling. If the user is currently viewing an event, use the event ID from the page context. Guests are emailed a cancellation only when send_updates asks for it.

Input Parameters

string
required
string
string
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_FILEDelete a file or folder from Drive. This is a destructive action — always confirm with the user before executing. Deleting a folder also deletes all files inside it. Use this when the user explicitly asks to delete, remove, or trash a file or folder.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_FORMDelete a form and all its responses. This is a destructive action — always confirm with the user before executing. Use this when the user explicitly asks to delete or remove a form.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_FORM_RESPONSEDelete a single form response. This is destructive — always confirm with the user before executing. Use when the user asks to remove or delete a specific submission.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_FORM_VARIANTDelete an A/B test variant (and its underlying duplicated form). Destructive — always confirm with the user. Use when the user asks to remove a variant or end an experiment.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_MAIL_LABELDelete one mail label from this mailbox.

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_MAIL_RULEDelete one mail rule by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_MAIL_TEMPLATEDelete one saved mail template by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_NAMED_RANGEDelete a named range from a spreadsheet by name. Names are matched case-insensitively.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_PIPELINEDelete a CRM pipeline and all of its stages. Deals in the pipeline must be moved or deleted first.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_PIVOT_TABLERemove a pivot table from the sheet. The host tab itself stays — only the pivot row in pivotTables[] is removed. Returns { deleted: true } on success.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_PRODUCTDelete a product from the workspace catalog. Existing deal/quote line items referencing it are NOT deleted, but their product_id is nulled.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_PROJECTDelete a project by ID. Only project admins or workspace admins can delete. Tasks belonging to the project are not deleted — they become unassigned from the project.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_QUOTEDelete a CRM quote and its line items.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_RECURRING_EVENT_FUTUREDelete this and all future occurrences of a recurring event by adding an UNTIL clause to the master’s RRULE, ending the series the day before the given split_date.

Input Parameters

string
required
string
required
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_RECURRING_EVENT_SINGLEDelete a single occurrence of a recurring event by adding the occurrence date to the master’s excluded_dates. The occurrence is suppressed without affecting other instances.

Input Parameters

string
required
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_RESOURCE_COMMENTDelete an existing document, task, wiki, mail-thread or Code comment by its comment ID. Existing author, ownership, and parent-resource permissions apply; each module’s reply-deletion behavior is preserved.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_ROLEDelete a custom role. System roles cannot be deleted. Requires admin role.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SCORING_RULEDelete a lead scoring rule.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SEQUENCEDelete a sequence (and all its enrollments).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHARED_DRIVEDelete a shared drive (destructive, manager-only).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHEET_COLUMNSDelete columns atomically and return the bounded change receipt for undo or redo.

Input Parameters

string
required
string
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHEET_IMAGEDelete editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHEET_PICTURE_GROUPDelete editable picture groups with cell anchors and CSS pixel geometry. Every leaf references an image asset owned by this sheet; native group transforms use EMU coordinates.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHEET_ROWSDelete rows from a sheet tab by 0-based index.

Input Parameters

string
required
string
array
0-based row indices to delete.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SHEET_SHAPEDelete editable floating shapes with editable text, cell anchors and CSS pixel geometry.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SLICERRemove a slicer from the sheet. Returns { deleted: true } on success.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_SLIDE_MASTERDelete an unused master slide. Returns 409 with the referencing slide count while the master is in use.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_TEAMPermanently delete a team from the workspace. Only team admins or workspace admins can delete. All memberships are removed. Child teams are orphaned (parent set to null). Use this when the user asks to delete, remove, or dissolve a team.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_USERIrreversibly delete a member. Requires admin and refuses the last owner. Reassigns CRM contacts to successor_user_id (default: acting admin); an ineligible successor aborts before mutation.

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Who inherits the departing member’s CRM contacts. Defaults to the acting admin. An ineligible id is refused with 400 contact_successor_ineligible and nothing is deleted.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_WIKI_PAGEMove a wiki page to Trash, together with every page beneath it. Trashed pages leave the tree and search, and can be brought back with wiki_page_restore; only wiki_page_permanent_delete removes them for good. A page that has child pages answers 409 with requires_cascade and children_count unless cascade=true is passed, so confirm with the user before trashing a sub-tree. Use this when the user asks to delete or remove a wiki page.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DELETE_WIKI_SYNCED_BLOCKSoft-delete a synced block. Embedded references will show error chips until restored. Use restore_wiki_synced_block to undo.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DETACH_MASTER_FROM_SLIDEDetach a slide from its master. The slide keeps its current rendered elements but no longer inherits from the master.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCS_CREATE_NAMED_RANGECreate a named range (template placeholder) on a document. Named ranges anchor to ProseMirror node positions and are used for template-based document generation. Use replace_named_range_content to fill a named range with content. Name must be alphanumeric + underscore, must not start with a digit (e.g., party_name, companyAddress).

Input Parameters

string
required
string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCS_DELETE_NAMED_RANGEDelete a named range (template placeholder) from a document by name. Names are unique per document.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCS_LIST_NAMED_RANGESList all named ranges (template placeholders) defined on a document. Returns each range’s name and its anchored node positions.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_ASSET_CREATEAdd an image to a doc, sheet, slide deck or canvas board as one of its own assets and get back the URL its body should store (/api/assets/{id}/content). Send the bytes as content_base64, source_file_id to copy a Drive file the caller can view, or source_url to import a public HTTPS image through the SSRF guard; neither source is referenced afterwards. The type is decided from the bytes and only images are accepted (415 otherwise); SVG uploads are sanitized before storage and refused with 415 when malformed. Stored SVG is sanitized on every read and served inline as image/svg+xml under a restrictive Content-Security-Policy; malformed stored SVG is refused with 404. Drive SVG downloads remain attachments. The bytes count against the container owner’s storage (413 past it). The same image added to the same container again returns the asset already held. The asset is never visible in Drive and is readable exactly when the container is.

Input Parameters

string
required
string
File name to keep with the image; defaults to image.
string
Declared type. The stored type is decided from the bytes.
string
Fetch a public HTTPS image into this container. Private network addresses and redirects to them are refused; the source URL is not stored in the body.
string
The image bytes, base64-encoded (no data: prefix).
string
Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_DELETEDelete a comment. Author or document owner only.

Input Parameters

string
required
string
required
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_REACTION_ADDAdd an emoji reaction to a comment. Idempotent per (user, emoji). Returns the comment’s updated reaction aggregate.

Input Parameters

string
required
string
required
string
required
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_REACTION_REMOVERemove the caller’s emoji reaction from a comment. Returns the comment’s updated reaction aggregate.

Input Parameters

string
required
string
required
string
required
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_RESOLVEEdit your own comment or resolve a thread. Content edits require commenter access; resolution requires editor access. expected_content rejects stale edits with 409.

Input Parameters

string
required
string
boolean
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Original content captured when editing began. A changed comment returns 409.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_CREATEAdd a threaded comment. Commenter permission required. parent_id makes it a reply; anchor carries CRDT-stable position info.

Input Parameters

string
required
object
string
required
string
string
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_LISTList threaded comments. Response includes per-user unread_count (comments by other users since the requester’s last mark-read, not resolved).

Input Parameters

string
required
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_MARK_READAdvance the requester’s last-seen marker so the unread badge clears. Idempotent.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_THREAD_MARK_READMark one comment thread read for the requester, clearing its unread badge. Idempotent. commentId must be a root comment on this document; a reply id or a comment on another document is refused 404.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_COMMENT_THREAD_MARK_UNREADMark one comment thread unread for the requester so it stays flagged until reopened, even when its only comments are the requester’s own. commentId must be a root comment on this document; a reply id or foreign-document id is refused 404, and a resolved thread is refused 409 comment_resolved.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_DELETESoft-delete a document (move to trash). Owner only.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_DUPLICATEMake a copy. Title becomes ‘Copy of <orig>’. Visibility resets to restricted; labels/pin/star are NOT inherited. Requires viewer access on the source.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_PERMANENT_DELETEPermanently delete a trashed document. Irreversible.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_PINToggle pinned state. Editor permission required (workspace-wide pin, not per-user).

Input Parameters

string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_RESTORERestore a trashed document.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_SHARED_WITH_MEDocuments shared with the calling account through an explicit permission grant, across every workspace and every identity the account owns. Excludes documents the account owns. Each row names the workspace that shared it and the role the grant carries. scope=workspace narrows discovery to resources in the authenticated current workspace without changing access.

Input Parameters

string ("doc" | "sheet" | "slide" | "canvas")
Filter by document type.
integer
string ("account" | "workspace")
Account-wide by default. workspace lists only resources in the authenticated current workspace; grants and resource access remain unchanged.
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_STARToggle starred state. Viewer permission is sufficient. Body {starred: bool} is optional — omit to toggle.

Input Parameters

string
required
boolean
Omit to toggle the current state.
Slug: AMBIGUOUS_MCP_DOCUMENTS_THUMBNAILContent-derived thumbnail for doc/sheet/slide cards. Returns SVG by default or PNG for Accept: image/png; cached privately for 60 seconds.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_TRASH_LISTFind all deleted native Docs, Sheets, Slides and Canvas items owned by the caller. Returns their document IDs for documents_restore or documents_permanent_delete; optional type filters doc, sheet, slide or canvas. Uploaded Drive files and folders use list_trashed_files, which can also include materialized native-document shadow rows but is not a complete native-document trash list. An empty Drive-file trash result does not mean this document trash is empty.

Input Parameters

string ("doc" | "sheet" | "slide" | "canvas")
Filter by document type.
integer
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_VERSION_GETGet a version’s metadata + serialized content snapshot.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_VERSION_REVERTRevert the document to a prior version. Force-snapshots current state first.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_VERSIONS_CREATECreate a manual snapshot (forces past the 5-minute throttle).

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DOCUMENTS_VERSIONS_LISTList version snapshots, newest-first, cursor-paginated (default 50 per page). Walk via next_cursor until has_more is false.

Input Parameters

string
required
integer
string
Opaque cursor from a prior next_cursor.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_CONFIRM_UPLOADConfirm a presigned upload completed successfully. Verifies the blob exists, rechecks its real size and stored bytes, then marks the file as confirmed and emits the upload event. A retryable storage-inspection failure leaves the upload pending and returns 503; a missing object removes the pending row and returns 410. Idempotent — confirming an already-confirmed file returns it unchanged without repeating the upload event.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_CONTENTA file’s bytes. A browser is redirected to a short-lived signed storage URL where signing is available and is otherwise sent the bytes; an MCP tool call always gets the bytes, refused 413 above the MCP result size limit. Pass ?download=true for Content-Disposition: attachment; default is inline. Content retrieval failures can return 503/504 via raw Response because those statuses are outside the typed contract error-code enum.

Input Parameters

string
required
string
string
string
Slug: AMBIGUOUS_MCP_DRIVE_FILE_IMPORTAdd a file to Drive from JSON, for clients that cannot send multipart: give either an https url to fetch (up to 100 MB) or the bytes as content_base64 (up to 25 MB decoded), plus a name. The file goes through the same checks as a browser upload: its type is decided from the bytes, blocked types are refused, and it counts against the caller’s storage quota. Links to private network addresses are refused, including through redirects. Returns the stored file.

Input Parameters

string
An https link to fetch the file from, up to 100 MB. Links to private or internal network addresses are refused, and every redirect is checked the same way.
string
required
File name to store, including its extension.
string
A hint only: the stored type is decided from the file’s bytes, so a mislabelled file is never stored as what it claims to be.
string
The file’s bytes, base64-encoded, up to 25 MB once decoded. Send this or url, not both.
string
Reuse this key only to retry the same import. A changed request returns 409. Use a new key for each new import.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Folder to place the file in. Omit for the Drive root.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_CREATECreate a revocable, write-only public file request for a folder. The capability token is returned only in this response.

Input Parameters

string
required
string
required
integer
required
string
required
string
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_REMINTReplace a live file request’s capability token without changing its request identity, limits, upload progress, or expiry. The previous token stops working immediately and the replacement token is returned only in this response.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_REVOKERevoke a folder’s public file request immediately.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_REQUESTS_LISTList the caller’s file requests for one owned Drive folder.

Input Parameters

string
string
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILES_RECENTRecently used files for the current user — files they opened in the last 30 days (their own views, including files shared with them that they can still open) OR files they own created in the last 24 hours. Sorted newest first by their own last view, or creation for their own new files.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILES_SHARED_WITH_MEFiles shared with the current user through a direct, team or external grant, newest share first (sort=modified orders by last modified instead). Each row carries shared_at and shared_by. Excludes files the user owns.

Input Parameters

string ("shared" | "modified")
shared (default): most recently shared with you first. modified: most recently modified first.
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILES_STARREDFiles the current user has starred.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILES_SUGGESTEDFiles the current user is likely to want next, each with the reason it is suggested: they opened it (opened), someone shared it with them (shared), or someone else added it to a folder they own or an agent they manage created it (added). Covers the last 14 days, newest reason first, at most one entry per file and only files the caller can still open. Stars never influence it. Use this for the My Drive home, not for a full history; use drive_files_recent for everything the user opened.

Input Parameters

string
How many to return, 1 to 10. Defaults to 3.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_TAG_ATTACHAttach one of your tags to a Drive file, a doc/sheet/slide, or a form, so one tag can group a PDF with the document it belongs to. Owner-only (anyone else gets 404) and idempotent. Pass resource_type to name the kind, or omit it to infer it from the id.

Input Parameters

string
required
string
required
string ("file" | "document" | "form")
What the id names: a Drive file, a doc/sheet/slide (document) or a form. Omit to infer it from the id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_TAG_DETACHDetach a tag from a Drive file, a doc/sheet/slide, or a form. Owner-only. Pass ?resource_type= to name the kind, or omit it to infer it from the id.

Input Parameters

string
required
string
required
string
string
string ("file" | "document" | "form")
What the id names: a Drive file, a doc/sheet/slide (document) or a form. Omit to infer it from the id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_UPDATERename, move, or star/unstar a file. Requires edit access — the owner or an editor/owner share. A move also needs editor access on the destination folder (contributor in a shared drive), and an item whose sharing is restricted moves only with its owner (403 drive_move_requires_owner).

Input Parameters

string
required
string
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FILE_UPLOAD_INITInitiate a file upload. Reserves a Drive row + storage key and returns a short-lived presigned PUT URL the client uploads the bytes to.

Input Parameters

string
required
string ("chat" | "mail")
Set to chat when the file is a chat attachment: it is filed in the workspace’s Chat attachments folder; mail files it in the Email attachments folder. For chat, then post it as [name](drive://&lt;file_id&gt;) in the message content, with ?w=<width>&h=<height> when the confirmed file has both. The sender’s own attached files become readable to the channel’s members when the message is sent.
string
required
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_FOLDER_ANCESTORSBreadcrumb chain (root → leaf) for a folder. Powers breadcrumb hydration on deep-link reloads. Viewer permission is sufficient.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_SHARED_DRIVE_FOLDER_CREATECreate a folder inside a shared drive. Requires contributor+ on the drive. Pass parent_folder_id to nest.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_TAG_CREATECreate a new tag in the user’s catalog.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_TAG_DELETEDelete a tag (cascades to all file assignments).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_TAG_FILES_LISTList everything you tagged with the given tag: Drive files, docs/sheets/slides and forms you own, newest first. Docs and forms carry document_type.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_TAGS_LISTCurrent user’s tag catalog. Each tag carries name, color, and sort order.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DRIVE_TAG_UPDATERename, recolor, or reorder a tag.

Input Parameters

string
required
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DUPLICATE_SLIDEDeep-copy a slide within the same deck. The duplicate is inserted immediately after the source slide. All elements (including group children) receive new unique IDs to avoid collisions. Useful for template-based workflows: duplicate a template slide, then update the copy with new content.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_DUPLICATE_TASKClone a task — copies title (appends ’ (copy)’), description, priority, project, goal, cycle, estimate, due/start date, recurrence, custom fields, and labels. The clone starts at status ‘todo’ with a fresh task key.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_ALLEdit all occurrences in a recurring series. Updates the master event.

Input Parameters

string
required
string
boolean
string
string
array
The event’s outside guests by email. On create it adds them; on update it replaces the outside-guest list (members are unaffected). An address a workspace member owns becomes a member guest instead.
string ("confirmed" | "tentative" | "cancelled" | "outofoffice")
Event status. outofoffice is used by the OOO responder.
boolean
string
string
string
array
Everyone on the event. Each entry is a string (UUID or email) or an iCal-natural object naming the attendee via email, id, or user_id; any other object key is ignored. An object with none of those three returns 400. An email no workspace member owns becomes an outside guest (returned in guests); it never creates a workspace invitation.
string
string
string ("default" | "outOfOffice" | "focusTime")
Calendar event type — a display/filter category. It does not change event behavior: OOO auto-decline keys on status: "outofoffice", and free/busy keys on transparency (independent inputs). The one behavioral value is agentDispatch, which routes a confirmation task to the assignee on create.
string ("default" | "public" | "private")
Visibility scope for the event.
string
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string ("opaque" | "transparent")
Free/busy classification (RFC 5545 TRANSP). opaque = Busy (default; blocks availability). transparent = Free (e.g. focus time).
string
Video-call URL. Accepts explicit http(s) or a schemeless hostname/path, which is stored as absolute HTTPS. Any other scheme is rejected 400. Empty string or null clears the link and provider.
array
Existing-event ids the new_and_existing bulk-decline should leave untouched.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
boolean
string ("new_only" | "new_and_existing")
OOO auto-decline granularity (only meaningful when status=outofoffice). new_only declines invitations arriving during the window; new_and_existing also bulk-declines events already attended.
string
string
Auto-reply note sent with an OOO decline.
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
Slug: AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_FUTUREEdit this and all future occurrences of a recurring event by splitting the series at the given date. Use this for ‘change the meeting time from next week onwards’ or ‘update our recurring Friday sync starting next month’.

Input Parameters

string
required
string
boolean
string
string
array
The event’s outside guests by email. On create it adds them; on update it replaces the outside-guest list (members are unaffected). An address a workspace member owns becomes a member guest instead.
string ("confirmed" | "tentative" | "cancelled" | "outofoffice")
Event status. outofoffice is used by the OOO responder.
boolean
string
string
string
array
Everyone on the event. Each entry is a string (UUID or email) or an iCal-natural object naming the attendee via email, id, or user_id; any other object key is ignored. An object with none of those three returns 400. An email no workspace member owns becomes an outside guest (returned in guests); it never creates a workspace invitation.
string
string
string ("default" | "outOfOffice" | "focusTime")
Calendar event type — a display/filter category. It does not change event behavior: OOO auto-decline keys on status: "outofoffice", and free/busy keys on transparency (independent inputs). The one behavioral value is agentDispatch, which routes a confirmation task to the assignee on create.
string
required
Date at which to split the series; the master ends the day before.
string ("default" | "public" | "private")
Visibility scope for the event.
string
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string ("opaque" | "transparent")
Free/busy classification (RFC 5545 TRANSP). opaque = Busy (default; blocks availability). transparent = Free (e.g. focus time).
string
Video-call URL. Accepts explicit http(s) or a schemeless hostname/path, which is stored as absolute HTTPS. Any other scheme is rejected 400. Empty string or null clears the link and provider.
array
Existing-event ids the new_and_existing bulk-decline should leave untouched.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
boolean
string ("new_only" | "new_and_existing")
OOO auto-decline granularity (only meaningful when status=outofoffice). new_only declines invitations arriving during the window; new_and_existing also bulk-declines events already attended.
string
string
Auto-reply note sent with an OOO decline.
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
Slug: AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_SINGLEEdit a single occurrence of a recurring event, creating an exception without affecting other occurrences. Use this when the user says ‘move just next Tuesday’s meeting to 3pm’ or ‘cancel only this one occurrence’.

Input Parameters

string
required
string
boolean
string
string
array
The event’s outside guests by email. On create it adds them; on update it replaces the outside-guest list (members are unaffected). An address a workspace member owns becomes a member guest instead.
string ("confirmed" | "tentative" | "cancelled" | "outofoffice")
Event status. outofoffice is used by the OOO responder.
boolean
string
string
string
array
Everyone on the event. Each entry is a string (UUID or email) or an iCal-natural object naming the attendee via email, id, or user_id; any other object key is ignored. An object with none of those three returns 400. An email no workspace member owns becomes an outside guest (returned in guests); it never creates a workspace invitation.
string
string
string ("default" | "outOfOffice" | "focusTime")
Calendar event type — a display/filter category. It does not change event behavior: OOO auto-decline keys on status: "outofoffice", and free/busy keys on transparency (independent inputs). The one behavioral value is agentDispatch, which routes a confirmation task to the assignee on create.
string ("default" | "public" | "private")
Visibility scope for the event.
string
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string ("opaque" | "transparent")
Free/busy classification (RFC 5545 TRANSP). opaque = Busy (default; blocks availability). transparent = Free (e.g. focus time).
string
Video-call URL. Accepts explicit http(s) or a schemeless hostname/path, which is stored as absolute HTTPS. Any other scheme is rejected 400. Empty string or null clears the link and provider.
array
Existing-event ids the new_and_existing bulk-decline should leave untouched.
string
required
RECURRENCE-ID of the occurrence to split out as an exception.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
boolean
string ("new_only" | "new_and_existing")
OOO auto-decline granularity (only meaningful when status=outofoffice). new_only declines invitations arriving during the window; new_and_existing also bulk-declines events already attended.
string
string
Auto-reply note sent with an OOO decline.
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
Slug: AMBIGUOUS_MCP_EMPTY_TRASHPermanently delete the trashed files the user holds the owner rung on. Shared-drive files are included only for drives the user manages. Irreversible — confirm with user first. Returns the number of files deleted.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ENROLL_CONTACT_IN_SEQUENCEEnroll a contact in a CRM sequence so they begin receiving the automated steps (emails, tasks, calls). Use this when the user asks to start a campaign for a specific contact.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ENSURE_WIKI_REVERSE_RELATIONAuto-create the reverse relation property on the target database if missing. Idempotent — returns the existing or newly-created reverse property id.

Input Parameters

string
required
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_EXPORT_DOCUMENTExport a document, sheet, or slide to one of its supported standard formats. Sheets support xlsx, csv, tsv, and ods. Returns the file bytes with Content-Type and Content-Disposition attachment headers.

Input Parameters

string
required
string
string
string
array
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_EXPORT_DRIVE_FILEExport a workspace document (Doc, Sheet, or Slide) to a file format via its Drive ID. Docs support: docx, pdf, html, md. Sheets support: xlsx, csv. Slides support: pptx, pdf, html. Binary Drive files (images, archives, etc.) cannot be exported — use download instead.

Input Parameters

string
required
string
Target export format (e.g., docx, pdf, xlsx, csv, pptx). Validated by the handler.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_EXPORT_FORM_RESPONSESDownload all matching form responses as CSV with field labels, display values, blank unanswered cells, and ISO submission timestamps. Streams beyond the response-list page size.

Input Parameters

string
required
string
Required when field_id is set (legacy single-filter).
string
string
string
URL-encoded JSON array of {field_id, op, value} objects. Operators: contains, equals, is_empty, is_not_empty. Multiple filters AND together.
string
Filter by exact value of a specific field (legacy single-filter).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
ISO 8601 timestamp; only responses submitted after this.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_FIND_AND_REPLACE_IN_DECKFind and replace text across all slides in a presentation. Searches every text element and table cell on every slide. Useful for template-based workflows: create a deck from a template with placeholders like {{company_name}}, then replace them programmatically. Plain string matching only (no regex).

Input Parameters

string
required
string
required
string
required
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_FORMATTER_SETSet a flat map of fields on the node output. Native equivalent of the n8n Set node — alias n8n-nodes-base.set → formatter_set. Pure passthrough: parameters.values is resolved upstream by the dispatcher’s resolveActionParameters walker, so JSONLogic rules referencing {var: "<UpstreamNode>.<field>"} produce the literal value the handler echoes back. Downstream nodes reference the result via {var: "<NodeName>.values.<key>"}. Spec line 41: formatters are formatter_* operationIds.

Input Parameters

object
required
Key-value map of fields to set on the node’s output. Each value may be a literal (string/number/bool/array/object) OR a JSONLogic rule the dispatcher resolves against the node’s inputs before invocation. The handler is a passthrough — no per-key validation; downstream consumers (or the workflow author’s own filter/branch nodes) own the typing.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_ACCOUNT_ERASURE_OUTCOMERead a deleted member’s durable erasure outcome and notice-delivery state. Requires admin or owner.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_ACTIVITYGet a single activity by ID. Useful for reading back a just-created activity via the resource URL in the activity.created event payload.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_BILLING_BONUSESReturn the workspace’s full earned-bonus history, newest-first — perpetual activation bonuses merged with one-time activation grants. Powers the Home Action-bonuses card, which needs the whole history the notification feed cannot show. Any authenticated caller in the workspace.
Slug: AMBIGUOUS_MCP_GET_BILLING_QUOTAReturn the workspace’s unified action-meter view: plan, base/earned/topup quota, consumed-this-month, reset_at, member count + cap, trial state, active bonuses, auto-recharge config. Replaces the deprecated /api/billing/usage + /api/billing/ai-usage endpoints. Any authenticated caller in the workspace.
Slug: AMBIGUOUS_MCP_GET_CALENDARGet a single calendar by ID. Returns the calendar’s name, color, timezone, default status, and owner. Use this when the user asks about a specific calendar’s settings or before creating events to verify the timezone.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CALENDAR_COLORSGet the available color palette for calendars and events. Returns 24 calendar colors and 11 event colors, each with a background and foreground hex value. Use this when the user asks what colors are available, or before setting a calendar or event color.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CANVASGet a full canvas by id, including every element in data.elements. Use when you need the complete board; for a large board prefer get_canvas_manifest (ids/types/bounds only) or get_canvas_frame to stay within context budget. Coordinates: board units, top-left origin, +x right / +y down. Example: get_canvas({ id: “<boardId>” }) → the board with all elements.

Input Parameters

string
required
Canvas board id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CANVAS_ELEMENTSBatch-fetch specific elements of a board by id — pass ids as a comma-separated list (max 500) and only those elements are returned, never the whole board. Use to refresh just the elements that changed (a collaborator’s edit named in a canvas.updated change-feed frame carries their ids), staying element-scoped rather than reloading the board body. A requested id that is ABSENT from the response means the element was deleted — drop it locally. Coordinates: board units, top-left origin, +x right / +y down. Example: get_canvas_elements({ id: “<boardId>”, ids: “el-a,el-b” }) → { elements: [{ id: “el-a”, … }] } (el-b was deleted).

Input Parameters

string
required
Canvas board id.
string
required
Comma-separated element ids to fetch (max 500).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CANVAS_FRAMEGet a frame (or swimlane) element and its children — every element whose frameId points at it. Use to read one region of a large board in full detail. Coordinates: board units, top-left origin, +x right / +y down. Example: get_canvas_frame({ id: “<boardId>”, frameId: “<frameId>” }) → { frame, elements: […] }.

Input Parameters

string
required
Canvas board id.
string
required
Frame (or swimlane) element id within the board.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CANVAS_MANIFESTGet a bounded manifest of a board — element ids, types, and bounds only (no style/content). Use this to survey a large board cheaply, then fetch a specific frame or the full board for detail. Coordinates: board units, top-left origin, +x right / +y down. Example: get_canvas_manifest({ id: “<boardId>” }) → { element_count, elements: [{ id, type, x, y, w, h }] }.

Input Parameters

string
required
Canvas board id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CHANNEL_MESSAGESGet recent messages from a chat channel. Returns messages with id, content (Markdown), author info, reactions, thread reply count, and timestamps. Use this when the user asks to read messages, catch up on a channel, or find a specific conversation. If the user is currently viewing a channel, use the channel ID from the page context. Messages are returned in reverse chronological order (newest first).

Input Parameters

string
Message ID — return the page of messages newer than this message (the forward twin of before), oldest-of-the-page first in the same newest-first envelope. Reports has_more_newer. Ignored when around is also set. An ID outside this channel is ignored and the newest page is returned.
string
Max messages to return (default 50, cap 100).
string
Message ID — return a window centred on this message (roughly half the limit on each side) instead of the newest page. Takes precedence over cursor/before/before_date. An ID outside this channel is ignored and the newest page is returned.
string
Message ID — return messages older than this message.
string
Opaque cursor from a prior next_cursor.
string
string
string
Offset for legacy pagination.
string
required
string
ISO timestamp — return messages created before this instant.
string ("true" | "false")
Pass ‘true’ to include soft-deleted messages (rendered as tombstones).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CHANNEL_READ_RECEIPTSGet per-member read positions for a channel — who has read up to which message. Useful for reporting on whether an announcement has been seen by everyone.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CONTACTGet a single CRM contact by ID, including full details: name, email, phone, title, company, lifecycle stage, custom properties, and timestamps. If the user is currently viewing a contact, use the contact ID from the page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CONTACT_SCOREGet a contact’s current lead score with a breakdown of which scoring rules matched and how many points each contributed. Use this to explain why a contact is hot/cold.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_COVER_THUMBNAILGet the PNG thumbnail bytes for the first slide (cover image) of a presentation. Convenience endpoint — equivalent to get_slide_thumbnail with index 0.

Input Parameters

string
Opaque client cache-bust version.
string
required
string
small (200px), medium (800px, default), or large (1600px).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_COWORKERGet one AI coworker’s configuration by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_COWORKER_STATUSGet a coworker’s runtime status (proxied from coworker service).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CRM_ANALYTICSGet analytics for accessible deals, optionally scoped to one pipeline: pipeline value by stage, conversion rates, average deal size, sales velocity, and deals breakdown.

Input Parameters

string
string
string ("this_month" | "this_quarter" | "this_year")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CRM_METRICSGet pipeline metrics summary: total open deals, total deal value, win rate, deals won/lost, and recent activity counts. Useful for high-level pipeline health questions.

Input Parameters

string
string
string ("this_month" | "this_quarter" | "this_year")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CRM_REPORTSGet CRM revenue, deals-by-source, pipeline-by-owner, and activity reports for accessible records, optionally scoped to one pipeline. Each report preserves its own timestamp axis.

Input Parameters

string
string
string ("ytd" | "this_quarter" | "this_month" | "all_time")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_CURRENT_WORKSPACEGet the active workspace (name, slug, logo). Accessible to any authenticated user.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DATA_CONNECTORGet a single data connector by ID, including its config and last-run status.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DEALGet a single CRM deal by ID, including full details: title, amount, currency, stage, pipeline, contact, company, owner, probability, close date, custom properties, and timestamps. Pass embed=line_items to include the full line-items array. If the user is currently viewing a deal, use the deal ID from the page context.

Input Parameters

string
required
string
Comma-separated embed fields. Supported: line_items.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DEAL_TEMPLATEGet a single deal template with its line items and resolved pipeline/stage names.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DETAILED_USER_PRESENCEGet detailed presence for a set of users — online (≤5min), idle (5–30min), or offline — plus the lastActiveAt timestamp. Capped at 100 user IDs. Fallback/cold-hydrate surface only — the primary presence path is the full-state push over the presence /ws/mux channel; poll this on connect or when the socket is down, not on a steady timer.

Input Parameters

string
required
Comma-separated user IDs (capped at 100 per request).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DOCS_PAGE_LAYOUT_DEFAULTGet the caller’s default layout for new Docs: pageless_default: true (the default) means new Docs start pageless, false means they start in pages.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DOCUMENTGet a single document by ID, including its full content and comments. If the user is currently viewing a document, use the document ID from the page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DOCUMENT_FOOTNOTESGet the footnotes from a document. Returns an array of footnotes, each with a footnoteId, body content (PM JSON), and the positions of inline references (footnoteRef nodes) in the body text.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DOCUMENT_HEADERS_FOOTERSGet the default, first-page, and even-page headers and footers from a document as ProseMirror JSON nodes (or null if not set).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DOCUMENT_PAGE_STYLEGet the page-level formatting for a document: margins (in PT), page size (letter/A4/legal or custom {width, height} in PT), and orientation (portrait/landscape). Empty object means default formatting.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DRIVE_STORAGEGet Drive storage usage.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_DRIVE_STORAGE_BREAKDOWNStorage breakdown by file type.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAILGet a single email by ID, including full Markdown body, sender, recipients (to/cc/bcc), subject, and timestamps. Use this when the user wants to read an email, see its contents, or reply to a specific message. If the user is currently viewing an email, use the email ID from the page context. Use detail=‘headers’ for envelope fields only (no body), or ‘minimal’ for id + labels only.

Input Parameters

string
required
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
string ("true" | "false")
Set to false to read without marking the message read.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAIL_ATTACHMENT_URLGet an attachment download URL: signed in cloud storage, authenticated API content in local storage.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAIL_CALENDAR_INVITEGet calendar invite embedded in an email.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAIL_DELIVERABILITYGet email deliverability statistics (sent/bounced/complained/opened rates) for the past 30 days. Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAIL_OPENSFetch open events for an email (sender only) Returns the rollup (first/last seen, open count) plus up to the most recent 50 individual open events. 403 if the caller doesn’t own the email’s mailbox.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EMAIL_SIGNATUREGet the workspace default email signature (Markdown). Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_ENTITY_PREVIEWLook up a hover-card style preview of any referenced entity (document, task, contact, deal, channel, chat message, user, event, file, wiki page, form, email). Module keys include docs, tasks, channels, messages, users. Returns rich details — title, status, owner, due date, amount, etc. — without fetching the full record. Use this when an entity is referenced by ID and you need a quick summary.

Input Parameters

string
required
Entity ID.
string
required
Entity module (e.g. ‘document’, ‘task’).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EVENTGet a single calendar event by ID, including full details: title, description, location, start/end times, recurrence rule, status, visibility, and attendees with RSVP status. If the user is currently viewing an event, use the event ID from the page context.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_EVENT_INSTANCESList individual occurrences of a recurring event within a date range. Expands the RRULE server-side and returns instance objects with computed start/end times. Use this to find specific occurrences (e.g., ‘what meetings are on next Tuesday?’) or to list upcoming instances of a series.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FEEDBACKRead back one submission by its receipt. Answers only the submitter — anyone else, including other members of the submitter’s workspace, gets 404. Returns the public projection: a status word (filed | accepted | declined | shipped, derived from the task Ambiguous works), the title, the priority, the task key, and timestamps. Nothing else on the task is exposed.

Input Parameters

string
required
The receipt returned by POST /api/feedback.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FILE_INFOGet detailed information about a file or folder in Drive. Returns id, name, mime_type, size_bytes, storage_key, owner info, parent folder, and timestamps. Use this when the user asks about a specific file’s details, size, type, or location. If the user is currently viewing a file in Drive, use the resource ID from page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FORMGet a form’s full details including field schema, settings, publish status, and slug. Use this when the user asks about a form’s fields, structure, or configuration. If the user is currently viewing a form, use the resource ID from page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FORM_AB_ANALYTICSGet A/B test comparison analytics for a form with variants. Returns control + each variant with views, responses, completion rate, and traffic weight. Use when the user asks which variant is winning, for A/B test results, or experiment performance comparison.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FORM_ANALYTICSGet analytics for a form: total views, total responses, completion rate, average completion time, responses-by-day (last 30 days), per-field drop-off funnel, and per-field summaries (option counts for select fields, numeric stats for rating/number fields). Use when the user asks about form performance, response rate, completion rate, or field-level statistics.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_FORM_RESPONSEGet a single form response by ID. Returns respondent info, submitted data (keyed by field ID), and timestamp. Use when the user asks about a specific submission or wants to review a particular response.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_APPROVALRead one submitted email exactly as it will send — From, Reply-To, the complete To/Cc/Bcc set, subject, body with signature applied, attachment manifest, threading and requested schedule. A caller without access gets 404, never 403.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_APPROVAL_ATTACHMENT_URLPresigned URL for one frozen attachment, addressed by its position in the manifest. The bytes are the copy taken at submit time, so a later edit of the source Drive file does not change what the reviewer reads. The URL is minted only after the review access check.

Input Parameters

string
required
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_RULEGet one mail rule’s conditions and actions by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_SIGNATUREGet the effective email signature.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_TEMPLATEGet one saved mail template by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MAIL_THREADGet all emails in a thread + muted flag.

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MESSAGE_READERSList the users who have read a specific message (i.e. whose read-cursor is at or past this message). Use this to check whether a message (e.g. an important announcement) has been seen by specific people.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_MODULE_AVAILABILITYWhich productivity modules are enabled for the caller’s workspace: module key → boolean. Bootstrap gate for nav + routes.
Slug: AMBIGUOUS_MCP_GET_MY_ACCESS_REQUESTWhether you have an open access request for a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar, task, project, or CRM pipeline.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_NOTIFICATION_KEYWORDSGet the current user’s notification keywords. The user receives a mention-style notification whenever any of these words appears in a message they can read.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_OOO_STATUSCheck out-of-office status for one or more users. Returns per-user OOO flag and event details when applicable. Call this before scheduling to avoid inviting people who are OOO.

Input Parameters

string
string
string
Comma-separated user IDs.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_PIPELINEGet a single CRM pipeline by ID with its ordered stages and its visibility — workspace when the pipeline is shared with the whole workspace, private when only its members reach its deals. A caller who is not a member receives 404.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_PRESENTATIONGet a presentation’s full data including all slides and their elements. Returns the SlideDeck envelope: top-level metadata (id, title, slide_count, owner, visibility, timestamps) plus the structured deck body nested under data (see SlideDeckData). Read settings/slides/masterSlides as response.data.slides[…], not at the response root. If the user is currently viewing a presentation, use the presentation ID from the page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_PRODUCTGet one CRM product from the catalog by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_PROJECTGet a single project by ID, including task count, visibility, and metadata.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_QUOTEGet a single CRM quote with its line items and linked deal/contact/company/owner.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_READ_RECEIPTS_DEFAULTGet read-receipts default for new compose.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_RESOLVED_PRESENCECold-hydrate the resolved presence dot for a set of users in the current workspace. Returns user_id → { kind, state } — the same already-resolved dot the projector pushes over the presence WebSocket channel. Used on connect and as the WS-down fallback; the client renders the state and computes nothing. Capped at 100 user IDs.

Input Parameters

string
required
Comma-separated user IDs (capped at 100 per request).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SECURITY_SETTINGSGet workspace security settings (require_2fa, session_timeout_hours, password_min_length, ip_allowlist). Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SEQUENCEGet a single sequence with its full step list and current enrollment count.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SETTINGSGet all workspace settings. Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SHARED_DRIVEGet shared drive details.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SHEETGet a spreadsheet’s structured data including columns, rows, and formulas. Returns the Sheet envelope: top-level metadata (id, title, owner, visibility, timestamps) plus the structured sheet body nested under data (see SheetData). Read the tab list as response.data.sheets; columns and rows are under response.data.sheets[0], not at the response root. If the user is currently viewing a sheet, use the sheet ID from the page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SHEET_RANGEGet a rectangular range of cell values from a sheet. Useful when you only need a slice of a large sheet (max 10,000 cells). Returns a 2D array of values plus the resolved start/end column letters and row numbers. Use orientation=COLUMNS to get column-major arrays (each inner array is one column). valueRenderOption controls how cells render: STORED (default) returns stored values verbatim — formula cells return the formula string; FORMULA forces formula strings; EVALUATED runs the server-side formula engine and returns computed values (e.g., ‘=SUM(A1:A3)’ becomes 6). Same-sheet refs across tabs (Sheet2!A1) resolve when evaluating; IMPORTRANGE returns #REF! (server cannot recurse cross-document).

Input Parameters

string
required
string
A1-style range — Sheet1!A1:D10. Required.
string
string
string
ROWS (default) or COLUMNS.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
STORED (default), FORMULA, or EVALUATED.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SIGN_AUDITGet the append-only audit trail for a visible signing document.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SIGN_DOCUMENTGet a signing document with signers and fields.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SLIDE_THUMBNAILGet the PNG thumbnail bytes for a specific slide. Sizes: small (200px), medium (800px, default), large (1600px).

Input Parameters

string
Opaque client cache-bust version.
string
required
string
small (200px), medium (800px, default), or large (1600px).
string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SNOOZE_PRESETSGet the user’s custom snooze quick-presets. Returns defaults when no custom presets are saved.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_SWIPE_ACTIONSGet the caller’s own mail-row swipe actions. Returns the defaults (right archive, left trash) when nothing is saved.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_TASKGet a single task by ID, including full details: title, description, status, priority, assignee, due date, labels, and subtask count.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_TEAMGet details of a single team including its first 10 members. Returns team metadata (name, slug, visibility, join policy, email) and an embedded members list with each member’s user_id, display_name, email, role, and added_at. Use this when the user asks about a specific team, its members, or ‘who is in team X?’.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_UNDO_SEND_SETTINGGet undo-send duration preference.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_UNREAD_COUNTSGet the full unread projection (mail inbox, per-channel chat badges with mute/preference resolved, notifications, total). Used for cold-connect / reconnect hydration; live updates arrive on the mux unread channel.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_USAGE_STATSGet workspace usage statistics including storage breakdown by user and module, active user count, API call volume, and per-module adoption metrics. Requires admin or owner role. Use this when the user asks about workspace usage, storage consumption, billing metrics, or capacity planning.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_USER_PRESENCEGet online status (true = online within the last 5 minutes) for a set of users in the current workspace. Returns user_id → boolean. Capped at 100 user IDs. Fallback/cold-hydrate surface only — the primary presence path is the full-state push over the presence /ws/mux channel; poll this on connect or when the socket is down, not on a steady timer.

Input Parameters

string
required
Comma-separated user IDs (capped at 100 per request).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_USERS_NOTIFICATION_PREFERENCESReturn the user’s notification preferences, merged with defaults so newly-added keys always render.
Slug: AMBIGUOUS_MCP_GET_USER_STATUSGet the current user’s active chat status (emoji + text) and DND-until timestamp. Use this before setting or clearing the status to know the current state.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_VACATION_SETTINGSGet vacation auto-reply settings.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WIKI_DATABASE_ROWGet a single database row by id.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WIKI_PAGEGet a wiki page’s full details including Markdown content, child pages, backlinks (pages that link to this page), and metadata. Use this when the user asks about a page’s content, wants to read documentation, or needs to check what links to a specific page. If the user is currently viewing a wiki page, use the resource ID from page context.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WIKI_PAGE_VERSIONGet a wiki page version’s full content (title + markdown body). Use this when the user asks what a previous version looked like, wants to compare versions, or needs the content of a specific snapshot.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WIKI_SPACE_GRAPHGet backlink graph data for a wiki space. Returns nodes (pages) and edges (links between pages). Use this when the user asks to visualize the knowledge graph, see how pages connect, or find highly-linked ‘hub’ pages.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WIKI_SYNCED_BLOCKGet a synced block by ID. Returns the block’s content and metadata. Use this when you need to read the current content of a shared block.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GET_WORKSPACEGet the current workspace details (id, name, slug). Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GRANT_ACCESSShare a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar with exactly one user_id or named team_id (workspace members/teams), or email (anyone; sends an invitation). For all current/future workspace humans and agents use set_visibility(visibility=workspace, workspaceRole), not per-person grants or the Everyone entry. invite_to_workspace=true sends a membership invite (admin-only); message applies only to email. Unsupported roles are rejected; re-sharing cannot lower a live grant.

Input Parameters

string
required
ID of the resource whose access is being managed, from that resource’s own read or list result. A permission entry’s id identifies its user or team, not the resource; supply that recipient separately as user_id or team_id.
string ("viewer" | "commenter" | "editor")
required
string
string
string
The specific named team’s ID, separate from the resource id. For the entire workspace audience, use set_visibility instead of managing the system Everyone team as a named share.
string
The specific person’s ID, separate from the resource id. On update/removal, use the user ID from that resource’s permission entry.
string
ISO 8601 deadline for the grant, or null for no expiry. Bounded by the shareExpiryMaxDays platform limit.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_GROUP_SLIDE_ELEMENTSGroup existing top-level elements on a slide into a single group. The group’s bounding box is computed automatically from the children. Children positions become relative to the group origin. At least 2 element IDs required. A named element may itself be a group — groupElements validates only that each id is top-level on the slide, so groups nest.

Input Parameters

string
required
string
required
array
required
Element IDs to group on the slide.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_HOME_DIGESTWorkspace-home roll-up: trailing-window task velocity (with prior-window deltas) plus the actor-aggregated team digest, visibility-gated per viewer. The window param selects the trailing window (7d default, or 1d for Today). Accessible to any authenticated workspace member.

Input Parameters

string
string
string ("7d" | "1d")
Trailing window for the velocity counts and the digest: ‘7d’ (default) or ‘1d’ (Today).
Slug: AMBIGUOUS_MCP_INSERT_PAGE_BREAKInsert a page break into a document at a given position. Forces subsequent content to start on the next page in exported .docx and .pdf files. The page break is inserted as a block node between paragraphs.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_INSERT_PAGE_NUMBERInsert a page number placeholder into a document. The placeholder renders as the current page number in exported .docx and .pdf files. Commonly used inside headers or footers (e.g., ‘Page X’) but can also appear inline in the body text. The placeholder is inserted as an inline node within a paragraph.

Input Parameters

string
required
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_INSERT_SECTION_BREAKInsert a section break into a document at a given position. Section breaks divide the document into sections that can have different formatting. A ‘next_page’ section break forces content to the next page (like a page break but marks a new section). A ‘continuous’ section break starts a new section on the same page.

Input Parameters

string
required
string ("continuous" | "next_page")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_INVITE_USERInvite a human by email with a member or admin role. Requires admin.

Input Parameters

string ("admin" | "member")
Defaults to member.
string
required
Single recipient email.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LEAVE_RESOURCERemove your own direct grant on a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar. The owner cannot leave. Returns an undo_token that shared_with_me_undo_leave accepts for ten minutes.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ACCESSList named/team grants, workspace/link tiers and pending invitations for a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar. id names the resource; grant IDs name recipients. To remove broad access but keep explicit collaborators and their roles, use set_visibility(visibility=restricted). The Everyone entry mirrors workspace access, not a named share. Resource kind is inferred from id.

Input Parameters

string
required
ID of the resource whose access is being managed, from that resource’s own read or list result. A permission entry’s id identifies its user or team, not the resource; supply that recipient separately as user_id or team_id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ACTIVITYList recent workspace activity (last 30 days). Scoped to the current user’s workspace. Filterable by resource type, resource ID, and acting user.

Input Parameters

string
Max entries to return (capped at 100, default 50).
string
string
string
Pagination offset.
string
Filter to actions performed by a specific user (UUID).
string
Filter to a specific resource (UUID).
string
Filter to a single resource type (e.g. ‘document’, ‘task’).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ADDRESS_BOOKList the caller’s address book: the shared CRM contacts they can see unioned with their own privately captured addresses, deduplicated on email with the shared record winning. Use this to resolve a recipient the user has written to before instead of asking them to retype an address. Private entries are never visible to another member.

Input Parameters

string
integer
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ARCHIVED_THREADSList archived threads (one per thread)

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_BLOCKED_SENDERSList all blocked senders for current user’s mailbox

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CALENDAR_EVENTSList events scoped to a single calendar by its id — the RESTful path variant of list_events (/api/calendars/events?calendar_id=…). Requires at least viewer access to the calendar.

Input Parameters

string
string
integer
string
string
string
string
integer
string
string
string
string
string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CALENDARSList the user’s calendars. Returns calendar id, name, color, timezone, and whether it’s the default. Use this to find the user’s default calendar ID before creating events.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CHANNELSList the user’s chat channels. Returns channels with id, name, type (public/private/dm), description, member count, and creator info. Use this when the user asks to see their channels, find a specific channel by name, or when you need a channel ID to send a message.

Input Parameters

string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Pass ‘1’ or ‘true’ to include archived channels.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CHARTSList every chart across every tab of the sheet. Each entry is annotated with the tab name it lives in.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CONDITIONAL_FORMATSList all conditional formatting rules on a spreadsheet. Returns each rule’s ID, ranges (A1 notation), and one canonical rule payload.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CONTACT_ACTIVITIESList activities (notes, calls, emails, meetings, tasks) on a specific contact’s timeline. Useful for summarizing recent interactions with a contact before sending an email or making a call.

Input Parameters

string
required
string ("note" | "call" | "email" | "meeting" | "task" | "chat")
Activity timeline event type. Used for filtering and badges in the UI.
integer
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CONTACT_GROUP_MEMBERSList all contacts that are members of a contact group. Returns the contact id, name, email, and type for each member.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CONTACT_GROUPSList all contact groups in the workspace with their member counts. Groups are named collections for organizing contacts (e.g., ‘Conference leads 2026’).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CONTACTSList CRM contacts. Supports filtering by type, lifecycle stage, owner, and text search. Returns contacts with id, name, email, phone, type, lifecycle_stage, company, and timestamps. Use this when the user asks to see their contacts, find a person, or list companies. Also use this with the ‘q’ parameter to search for existing contacts BEFORE creating new ones to prevent duplicates.

Input Parameters

string
Free-text search across name/email/phone.
string ("person" | "company")
Filter by contact type (person or company).
integer
Max rows per page (1-500, default 50). The People view requests 500 for the unified company-grouped UI.
string
Opaque cursor from a prior next_cursor for page-after-page walking.
string
string
integer
Offset-based pagination; use cursor for large result sets.
string
Filter to contacts that are members of this contact group.
string
Filter to contacts owned by this user.
string
Filter to contacts belonging to this company.
string ("subscriber" | "lead" | "mql" | "sql" | "opportunity" | "customer" | "evangelist")
Filter by funnel stage.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CRM_ACTIVITIESList recent CRM activity visible to the current user across contact and deal timelines.

Input Parameters

string ("note" | "call" | "email" | "meeting" | "task" | "chat")
Activity timeline event type. Used for filtering and badges in the UI.
integer
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CRM_PROPERTY_DEFINITIONSList the workspace’s typed custom-property definitions for contacts and deals, including relation properties that link a record to another contact, company, or deal. Optionally filter by entity_type.

Input Parameters

string
string
string ("contact" | "company" | "deal")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CRM_VIEWSList the user’s saved CRM views (filter + sort presets for contacts/companies/deals). Views personalize how CRM data is displayed without changing the underlying records.

Input Parameters

string
string
string ("contacts" | "companies" | "deals")
Which list page the saved view applies to.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CRM_WORKSPACE_USERSList all users (humans and agents) in the current workspace who can own CRM records. Use before assigning contacts or deals to a specific owner_id.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_CUSTOM_EMOJISList all custom emojis uploaded to the current workspace. Returns each emoji with id, name (without colons), image URL, and creator info. Use this to discover what custom emojis are available before referring to them by name.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DATA_CONNECTOR_RUN_HISTORYList recent execution history for a data connector. Each row records one manual or scheduled run with its status, duration, row count, and error (if any). Use the limit query param to cap the page size (default 20, max 100). Results are ordered by completion time, newest first.

Input Parameters

string
required
string
Page size, integer 1–100 (default 20).
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DATA_CONNECTORSList data connectors registered on a sheet. Connectors fetch data from external sources (URL, CSV, etc.) into specific cells.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DEAL_LINE_ITEMSList all line items for a deal, plus the computed total.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DEALSList CRM deals. Supports filtering by pipeline, stage, and status. Returns deals with id, title, amount, currency, stage, pipeline, contact, status, and timestamps. Use this when the user asks to see their deals, check the pipeline, or find opportunities.

Input Parameters

string
Free-text search across deal titles.
string
Comma-separated embed fields. Supported: line_items.
integer
string
string
string
integer
string ("open" | "won" | "lost")
Lifecycle of a deal. won and lost close the deal; lost requires a lost_reason.
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DEAL_TEMPLATESList deal templates in the workspace (reusable deal presets: default pipeline, stage, amount, probability, and line items).

Input Parameters

string
Search by name or SKU.
string
string
boolean
Hide products where active=false when true.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DOCUMENTSList the current user’s documents. Optionally filter by type. Includes externally owned documents by default; scope=workspace limits discovery to the authenticated current workspace.

Input Parameters

string ("doc" | "sheet" | "slide" | "canvas")
Filter by document type.
integer
Page size. Clamped server-side to the paginationMax platform limit (200) — a larger value is served at the cap with has_more and a next_cursor, never rejected.
string ("account" | "workspace")
Account-wide by default. workspace lists only resources in the authenticated current workspace; grants and resource access remain unchanged.
string
Opaque cursor from a prior next_cursor.
string
string
integer
Rows to skip. Clamped server-side to the paginationOffsetMax platform limit; page deeper with cursor, which walks the whole set at constant cost.
string ("true" | "false")
Pass ‘true’ to return only starred documents.
integer
Alias for limit; clamped the same way.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DRAFTSList the unsent draft emails in this mailbox.

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_DRIVE_FOLDERSList only folders (not files) in Drive — useful for folder pickers. Pass root to scope the listing to My Drive, shared drives, or Shared with me.

Input Parameters

string
Name filter. Spans every root at any depth, so parent_id and root are ignored.
string ("my_drive" | "shared_drives" | "shared_with_me")
Omit for the legacy merged listing; supply to scope results to one root.
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_EMAIL_ATTACHMENTSList attachments for an email

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ENROLLMENT_EVENTSGet the event log for a single sequence enrollment (step-executed, email-opened, email-replied, branch-taken, completed). Useful for auditing why a contact moved to a particular step.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_EVENT_RESOURCESList resources currently booked for an event (rooms, equipment).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_EVENTSList calendar events across all of the user’s calendars. Supports filtering by date range, calendar, and free-text search. Returns events with id, title, start/end times, location, status, and attendees. Use this when the user asks to see their schedule, upcoming meetings, or events for a date. Use the q parameter to search for events by keyword (matches title, description, location, and attendee names).

Input Parameters

string
string
integer
string
string
string
string
integer
string
string
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FEEDBACKList the caller’s own submissions, newest first, as public projections (see get_feedback). Paginated with limit (default 50) and offset.

Input Parameters

string
Page size (default 50, capped at the platform pagination max).
string
string
string
Rows to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FILESList files and folders in the user’s Drive. Returns items with id, name, mime_type, size_bytes, is_folder, parent_folder_id, owner info, and timestamps. Use this when the user asks to see their files, browse a folder, find a specific file, or check what’s in Drive. If the user is currently viewing Drive, use context for the current folder. A parent_id the caller cannot view answers 404, exactly as an absent folder does; a folder shared from another workspace is browsed through GET /api/drive/{id}/children instead.

Input Parameters

string
Search text. When set, the listing is a search across everything the caller can open: every word must appear in an item’s name, its scanned text, or a document’s body. kind, owner_id, modified_after, added_by, location and in_folder filter it; results are most relevant first (more words in the name first, scanned-text matches last) unless sort is modified or name; limit (at most 50) and offset page it. Each result carries location and search_match. Operators such as type:pdf and modified:this-week in the text still work.
string ("folders" | "documents" | "spreadsheets" | "presentations" | "forms" | "images" | "pdf")
Restrict the listing to one kind of item. documents, spreadsheets and presentations include both workspace docs and uploaded office files of that kind; images and pdf include uploaded files only.
string ("name" | "owner" | "modified" | "last_opened" | "created" | "size")
Order of the listing. Folders come before files unless folders_first=false. Defaults to modified. last_opened uses the caller’s own last view and falls back to the modified, then created, time for items they never opened.
string
Legacy search-only kind filter: folders, documents, images, videos, audio or archives. Ignored without q; prefer kind.
string
Page size.
string ("asc" | "desc")
Direction of sort. Defaults to desc for modified, otherwise asc for name and owner and desc for the rest.
string
Opaque continuation token from next_cursor. Only returned for the default order (modified, newest first).
string
string
string
Number of items to skip; use with any order or filter, following has_more.
string
trash lists trashed items instead of a folder.
string ("agents")
agents: only items an agent added (the item’s owner is an agent identity).
string ("my_drive" | "shared_with_me" | "shared_drives")
Search only: my_drive is what you own outside shared drives, shared_with_me is what others own outside shared drives, shared_drives is shared-drive content.
string
Only items owned by this user.
string
Search only: the folder to search inside, including its subfolders. A folder the caller cannot view answers 404.
string
string ("true" | "false")
true (default) lists folders before files. false orders folders and files together by sort; keyset cursors are then not returned, so page with offset.
string
Only items modified at or after this instant (ISO 8601).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FOLDER_CHILDRENList the direct children of one folder, named in the path. Use this to browse into a folder — including one shared with you from another workspace, which the parent_id form of the list endpoint cannot return. Answers 404 for a folder the caller cannot view, exactly as an absent one does.

Input Parameters

string
required
string ("folders" | "documents" | "spreadsheets" | "presentations" | "forms" | "images" | "pdf")
Restrict the listing to one kind of item. documents, spreadsheets and presentations include both workspace docs and uploaded office files of that kind; images and pdf include uploaded files only.
string ("name" | "owner" | "modified" | "last_opened" | "created" | "size")
Order of the listing. Folders come before files unless folders_first=false. Defaults to modified. last_opened uses the caller’s own last view and falls back to the modified, then created, time for items they never opened.
string
Page size.
string ("asc" | "desc")
Direction of sort. Defaults to desc for modified, otherwise asc for name and owner and desc for the rest.
string
Opaque continuation token from next_cursor. Only returned for the default order (modified, newest first).
string
string
string
Number of items to skip; use with any order or filter, following has_more.
string ("agents")
agents: only items an agent added (the item’s owner is an agent identity).
string
Only items owned by this user.
string ("true" | "false")
true (default) lists folders before files. false orders folders and files together by sort; keyset cursors are then not returned, so page with offset.
string
Only items modified at or after this instant (ISO 8601).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FORM_RESPONSESList responses submitted to a form. Returns responses with respondent info, submitted data (keyed by field ID), and timestamps. Use this when the user asks to see form results, check submissions, analyze feedback, or export response data.

Input Parameters

string
required
string
string
Required when field_id is set (legacy single-filter).
string
string
string
string
string
URL-encoded JSON array of {field_id, op, value} objects. Operators: contains, equals, is_empty, is_not_empty. Multiple filters AND together.
string
Filter by exact value of a specific field (legacy single-filter).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
ISO 8601 timestamp; only responses submitted after this.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FORMSList the user’s forms. Returns forms with id, title, slug, is_published, response count, timestamps, and the caller’s own star and Drive tags. Pass starred=true for only the forms you starred. Use this when the user asks to see their forms, find a specific form, or check form status.

Input Parameters

string
Search filter on title/description.
string
string
string
string
string ("true" | "false")
‘true’ to list only the forms you starred.
string ("true" | "false")
‘true’ or ‘false’ to filter by publish state.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FORM_VARIANTSList A/B test variants for a form. Returns each variant’s id, name, traffic weight, active status, and variant form ID. Use when the user asks about their A/B tests, variant list, or experiment setup.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_FORWARDING_ADDRESSESList forwarding addresses + recent log.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_IDENTITY_API_KEYSList the calling user’s own API keys. Scoped to c.var.user.id — does not return keys belonging to other users in the same workspace. Admins managing other users’ keys should use GET /api/admin/api-keys.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_INBOXList the user’s received emails (inbox). Returns emails with id, from, subject, preview, read status, and sent timestamp. Use this when the user asks to check their inbox, see recent emails, or find a specific email. Use detail=‘headers’ for bandwidth-efficient scanning (omits body), or ‘minimal’ for id + labels only. Use label_ids to filter by specific labels (AND semantics — all listed labels must be present).

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string ("inbox" | "sent" | "drafts" | "starred" | "snoozed" | "scheduled")
inbox (default) | sent | drafts | starred | snoozed | scheduled.
string
integer
string
string ("me" | "unassigned")
Shared-mailbox queue only: me for threads you hold, unassigned for threads nobody holds. 400 on a personal mailbox or with a non-inbox folder.
string
Default true; pass false to flatten.
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MAIL_APPROVALSList email submissions awaiting a human decision. Returns the caller’s own submissions plus the ones they may decide — as the submitting agent’s current manager, or as a workspace admin/owner. A former manager sees nothing.

Input Parameters

string ("author" | "reviewer")
Narrow to the caller’s side of the queue. Omitted returns both.
integer
string
string
integer
string ("pending" | "approved" | "changes_requested" | "rejected" | "withdrawn")
Narrow to one decision state. pending is the Needs approval queue.
string
Narrow to one agent’s submissions: email it sent, and external email addressed to it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MAIL_BY_LABELList emails with a specific label

Input Parameters

string
required
integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MAIL_LABELSList every mail label in this mailbox.

Input Parameters

string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MAIL_RULESList mail rules / filters.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MAIL_TEMPLATESList the saved mail templates in this mailbox.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MUTED_THREADSList muted threads (inbox view for muted conversations)

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MY_TEAMSList teams the current user belongs to, with their role (admin or member) in each. Use this when the user asks ‘what teams am I in?’ or ‘my teams’ or ‘my memberships’.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_MY_WORKSPACESList workspaces the current user belongs to (human users may have multiple). Returns workspace id, name, slug, role, and which one is active.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_NAMED_RANGESList named ranges and named expressions on a spreadsheet. Each entry returns its name and either an A1 range or an exact literal expression. External-workbook expressions remain unresolved.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PINNED_MESSAGESList all pinned messages in a channel. Pinned messages are highlighted by members for ongoing reference (announcements, canonical links, etc.). Returns messages in newest-pin-first order.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PIPELINE_MEMBERSList the members of a CRM pipeline. Deal visibility is pipeline membership: a deal is visible to admins/owners and to members of its pipeline (directly or via a team). Roles are admin (can manage the pipeline + members) or member.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PIPELINESList all CRM pipelines with their stages. Each pipeline contains an ordered list of stages with names, sort order, and default probabilities. Use this before creating or moving deals to find valid pipeline_id and stage_id values.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PIVOT_TABLESList every pivot table across every tab of the sheet. Each entry is annotated with the tab name it lives in.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PRODUCTSList products in the workspace catalog. Use this when the user asks about pricing or available SKUs, or before adding a product as a deal line item.

Input Parameters

string
Search by name or SKU.
string
string
boolean
Hide products where active=false when true.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PROJECTSList accessible projects in the current workspace, optionally filtering by a case-insensitive name query before pagination. Returns each project with name, icon, color, visibility, and task count. Use this when the user asks to see their projects or find a project by name.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PROJECT_UPDATESList status updates for a project, newest first. Returns the health timeline with author and timestamp.

Input Parameters

string
string
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_PROTECTED_RANGESList all protected ranges on a spreadsheet. Returns each range with its ID, A1 range, description, warningOnly flag, and editorUserIds allowlist.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_QUOTESList CRM quotes/proposals. Filter by status (draft, sent, accepted, rejected, expired), deal, or contact. Useful for finding outstanding quotes or recently-accepted ones.

Input Parameters

string
string
string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired")
Quote lifecycle. accepted/rejected are terminal; viewed is recorded by the open-tracking pixel.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_RESOURCE_COMMENTSRead comments on a document, task, wiki page, mail conversation, pull request, or code review. Resource type is resolved from ID; a mail conversation can use its thread key with mailbox_id. result preserves threading, pagination, unread counts, and entity references supplied by its owning module.

Input Parameters

string
required
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_RESOURCESList bookable resources (rooms, equipment) in the workspace. Call before booking a room to see what’s available.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_ROLESList all roles in the workspace (system roles + custom roles). Requires admin role.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_RUNNING_EXECUTIONSList in-flight executions across every coworker in the active workspace. Joins coworker_executions → coworkers, filtered by status IN (‘PENDING’,‘RUNNING’). Powers the ‘Coworkers — running now’ saved filter on People & Access.

Input Parameters

string
string
string
string
string
string ("chat" | "mention" | "mail" | "tasks" | "documents")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SAVED_MESSAGESList all messages the current user has saved (bookmarked) across all channels. Returns messages with saved_at timestamp, channel name, and channel type. Saved messages are private to the current user (unlike pinned messages, which are shared with the channel).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SCHEDULED_MAILList scheduled (unsent) emails

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SCHEDULED_MESSAGESList all pending scheduled messages for the current user across all channels. Returns each scheduled message with channel name/type and the scheduled_at timestamp. Use this to review what’s queued to send later, or before updating/cancelling a scheduled message.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SCHEDULER_BOOKINGSList all bookings (across all scheduler links) owned by the current user. Useful for summarizing the user’s upcoming meetings.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SCORABLE_FIELDSList the contact fields that can be used in scoring rules (lifecycle_stage, industry, title, website, custom_properties.*, etc.) and the operators each supports.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SCORING_RULESList all lead scoring rules for the workspace.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SEND_AS_ADDRESSESList available send-as addresses for current user

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SENT_MAILList the emails sent from this mailbox.

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SEQUENCE_ENROLLMENTSList all enrollments for a sequence, including each contact’s current step, status, and next execute time. Useful for checking progress or finding an enrollment ID to unenroll.

Input Parameters

string
required
integer
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SEQUENCESList all CRM email/task sequences (multi-step automated outreach campaigns). Returns sequences with their steps, active status, and current enrollment count.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHARED_DRIVE_FILESList files in a shared drive.

Input Parameters

string
string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHARED_DRIVE_MEMBERSList shared drive members.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHARED_DRIVESList shared drives user is a member of.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHEET_IMAGESList editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHEET_PICTURE_GROUPSList editable picture groups with cell anchors and CSS pixel geometry. Every leaf references an image asset owned by this sheet; native group transforms use EMU coordinates.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHEETSList the current user’s spreadsheets (owned + shared). Convenience alias for GET /api/documents?type=sheet. Returns the lightweight SheetSummary shape without the structured data body — call GET /api/sheets/:id to load a specific sheet’s tabs/columns/rows.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHEET_SHAPESList editable floating shapes with editable text, cell anchors and CSS pixel geometry.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SHEET_VALIDATIONSList all data validation rules on a spreadsheet. Returns each rule’s range (A1 notation) and rule definition (type, values, strict, inputMessage).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SIGN_DOCUMENTSList signing documents in the workspace.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SIGN_TEMPLATESList reusable signing templates.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SLICERSList every slicer across every tab of the sheet. Slicers are interactive filter widgets that filter pivots / charts on a shared source range. Each entry is annotated with the tab name it lives in.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SLIDE_MASTERSList the master slide templates registered on a presentation. Child slides link to masters by reference and resolve current master elements at render time, beneath child-owned elements.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_SNOOZED_MAILList the snoozed emails in this mailbox.

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_STARRED_MAILList the starred emails in this mailbox.

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_TASK_ATTACHMENTSList Drive files attached to a task.

Input Parameters

string
required
string
Max items to return (per-endpoint default/cap).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_TASKSList tasks in the workspace. Pass assignee_id to filter by assignee (use the caller’s user ID for ‘my tasks’). Supports filtering by status, priority, project, and free-text query.

Input Parameters

string
Free-text search across title + description.
string ("updated_at" | "sort_order" | "created_at" | "due_date" | "priority")
Sort order for GET /api/tasks. updated_at (recently-touched first) is the default; sort_order for board / drag-reorder; created_at for chronology; due_date for deadline proximity; priority for urgency ranking.
integer
Page size. Values above the platform pagination maximum are clamped server-side.
string
Opaque cursor from a prior next_cursor.
string
string
integer
Offset-based pagination fallback.
string
Filter by system status. Comma-separated for multi-select.
string
Filter to tasks linked to this CRM deal.
string
Filter by cycle ID. none returns tasks with no cycle.
string
Filter by a single label ID (must be a UUID).
string
string
Pass ‘true’ to filter to tasks assigned to AI coworkers in the caller’s workspace.
string
Comma-separated label IDs (AND match).
string ("true" | "false")
Pass ‘true’ to filter to tasks with no project_id.
string
Filter to tasks linked to this CRM contact.
string
Filter by creator user ID.
string ("true" | "false")
Pass ‘true’ to return tasks linked to a CRM contact or deal.
string
string
Pass ‘me’ to filter to tasks the caller is subscribed to.
string
Filter to tasks assigned to this user. unassigned to filter to unassigned.
integer
Alias for limit.
string
ISO 8601 lower bound on updated_at.
string
YYYY-MM-DD upper bound (inclusive).
string ("true" | "false")
Pass ‘true’ to filter to tasks with a due date set.
string ("true" | "false")
Pass ‘true’ to filter out tasks blocked via task_relations.
string
Comma-separated label IDs (OR match).
string
Exclusive ISO 8601 upper bound on cancelled_at.
string
Inclusive ISO 8601 lower bound on cancelled_at.
string
ISO 8601 upper bound on completed_at.
string
ISO 8601 lower bound on completed_at.
string ("true" | "false")
Pass ‘true’ to include archived tasks (default: hidden).
string
string
YYYY-MM-DD lower bound (inclusive).
string
Filter by parent task ID. Special value null (string) returns top-level tasks only.
string
Filter by custom status ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
Pass ‘true’ to filter to tasks assigned to AI coworkers managed by the caller.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Comma-separated custom status IDs to exclude.
Slug: AMBIGUOUS_MCP_LIST_TASK_TEMPLATESList task templates in the workspace. Templates pre-fill fields when creating tasks. Optionally filter by project. Returns name, default fields (priority, status, estimate, assignee, labels), and creator.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_TEAMSList workspace teams visible to the current user. Returns public teams and private teams the user is a member of, with member counts. Filterable by q (case-insensitive substring match on name + slug). Optional limit caps the result count. Use this when the user asks to see teams, distribution lists, or workspace teams.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_TRASHED_FILESFind deleted Drive file rows and folders the caller owns, trashed themselves, or holds the owner rung on (a folder above it is theirs, or they manage its shared drive). Returns paginated file IDs and metadata for restore_file or permanent_delete_file. Can include materialized native-document shadow rows, but does not list every native Docs, Sheets, Slides or Canvas item: use documents_trash_list for the complete native-document trash owned by the caller. An empty result does not mean the whole workspace trash is empty.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_USERSList workspace members and agents with identity, role, status, storage usage, and timestamps. Requires admin or owner.

Input Parameters

string
Free-text search across display name + email.
string
Filter by role name.
string
Filter by user type (human | agent).
integer
Page size (default 50, max 500).
string
Opaque pagination cursor (preferred over offset).
string
string
integer
Offset for legacy pagination (must be ≥ 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
When true, hydrate each user with their coworker_config row (or null). Skips a second roundtrip when the caller needs to discriminate Coworker vs Agent in one fetch.
Slug: AMBIGUOUS_MCP_LIST_USER_STATUSESList active chat statuses (emoji + text + DND) for users in the workspace. Only returns users who currently have a non-null status or active DND. Useful for ‘who’s on vacation?’, ‘is anyone in meetings?’, or similar presence queries.

Input Parameters

string
string
string
Comma-separated user IDs to filter; omit for all users with an active status.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_WIKI_PAGE_DATABASESList all inline databases hosted on a wiki page.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_WIKI_PAGE_VERSIONSList the saved version snapshots for a wiki page (most recent first). Use this when the user asks for revision history, wants to see who edited and when, or needs to find a version to revert to.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_WIKI_SPACE_PAGESList pages in a wiki space with offset/limit pagination. Returns page summaries (id, title, slug, icon, parent_page_id, sort_order). Use this when the user asks to see all pages in a space, or when you need to paginate through a large space.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_WIKI_SPACESList all wiki spaces. Returns spaces with id, name, slug, description, icon, owner info, privacy setting, and page count. Use this when the user asks to see wiki spaces, browse the knowledge base, or when you need a space ID to create a page.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LIST_WIKI_SYNCED_BLOCKS_BY_PAGEList synced blocks that were originally created on a specific page. Use this when the user asks what shared content a page publishes, or to audit reuse.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_LOG_ACTIVITYLog an activity on a CRM contact or deal timeline. Activities track interactions like calls, emails, meetings, notes, and tasks. Use this when the user asks to log a call, record meeting notes, or add a note to a contact/deal.

Input Parameters

string
string ("note" | "call" | "email" | "meeting" | "task" | "chat")
required
Activity timeline event type. Used for filtering and badges in the UI.
string
Alias for body. Either field is accepted; sending both with different values returns 400.
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_ALIAS_CREATEAdd a new alias on a verified workspace domain

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_ALIAS_DELETEDelete a send-from alias address by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_ALIASES_LISTList all aliases for current user’s mailbox

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_ALIAS_SET_DEFAULTSet alias as default send-as identity

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_BLOCKLIST_CLEARUnblock by raw pattern (convenience for “Unblock sender” button)

Input Parameters

string
string
string
required
Sender address or domain to remove from blocklist.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_BLOCKLIST_REMOVEUnblock a sender by their blocklist entry id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_BULK_MODIFYApply one bulk action to emails chosen by id or search query.

Input Parameters

array
Explicit email IDs. Omit when using search_query.
string
Bulk mail action; validated server-side.
string
string
object
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_EXPORT_EMLExport a message as RFC 5322 EML, returning retained source octets when available.

Input Parameters

string
required
string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_EXTERNAL_AUTH_URLStart connected-mailbox (Gmail) OAuth — returns the consent URL.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTION_DELETEDisconnect a connected mailbox.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTIONS_LISTList connected mailboxes.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTION_TESTVerify a connected mailbox by fetching its Gmail profile.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_FOLDER_COUNTSPer-folder badge counts for sidebar Returns { inbox: unread_count, drafts, scheduled, snoozed } — Gmail-style.

Input Parameters

string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_LABEL_COUNTSPer-label unread counts for sidebar badges. A separate endpoint so the sidebar can refresh counts on read/receive without re-fetching the label definitions themselves. Shape mirrors /folder-counts.

Input Parameters

string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_MESSAGE_UNSUBSCRIBEOne-click unsubscribe. Triggers the List-Unsubscribe URL (RFC 8058) on the user’s behalf. Falls back to telling the client to open a mailto: link if no HTTP URL is present.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_ASSIGNEESThe people who can hold a thread in this shared mailbox — team grants flattened to their members.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_CREATECreate a shared mailbox and address it on a workspace domain (admin only)

Input Parameters

string
required
Local part of the mailbox address, e.g. support.
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Domain to address the mailbox on. Defaults to the workspace domain.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_DELETERetire a shared mailbox (admin only). Soft: stored mail is retained and the address stays reserved.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOXES_LISTList the shared mailboxes the caller holds, or every one in the workspace with scope=managed (admin only)

Input Parameters

string
Admin only: every shared mailbox in the workspace, not just the ones you hold.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_GETGet one shared mailbox and its members

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_MEMBER_ADDGrant a user or a team access to a shared mailbox (admin only)

Input Parameters

string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_MEMBER_REMOVERevoke a user’s or team’s access to a shared mailbox (admin only)

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_RESTORERestore a retired shared mailbox (admin only). Total — delete cascaded nothing.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_UPDATERename a shared mailbox’s display name; its address is unchanged (admin only)

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_SMART_COMPOSESuggest a short continuation of an email draft being written. Takes the text typed so far, optionally the subject and the earlier messages of the thread being replied to, and streams the suggested next words.

Input Parameters

string
required
The draft so far — the email text already typed, which the suggestion continues.
string
The draft’s subject line.
string
Earlier messages of the email thread this draft replies to, as plain text — the functional context for the suggestion. Optional; at most 32,000 characters.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_THREAD_MUTE_STATUSCheck if a thread is muted

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_TRASH_LISTList trashed (soft-deleted) emails — the caller’s own rows in folder=‘trash’. Restore one with untrash_email; nothing is purged automatically.

Input Parameters

integer
string
Opaque cursor from a prior next_cursor.
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Comma-separated label UUIDs (AND semantics).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MAIL_UNREAD_SUMMARYUnread mail summary for a cross-module unread view: the total unread count plus the top N (default 5, max 25) unread inbox rows with sender, subject, preview and timestamp, so a unified list can render without pulling the full inbox.

Input Parameters

integer
string
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_ALL_CHANNELS_READMark all channels as read for the current user. Advances the read cursor in every channel the user is a member of to the latest message, clearing all unread badges at once. Use this when the user wants to dismiss all chat unreads (e.g. returning from vacation).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_CHANNEL_READMark a channel as read up to a specific message. This clears the unread badge for the current user. Use this after the user has finished catching up on a channel, or programmatically to dismiss unread counts after the assistant reports on recent messages.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_CHANNEL_UNREADMark a channel as unread starting from a specific message. Moves the calling user’s read cursor back to just before that message, so the channel shows an unread badge and the message becomes the unread boundary. Use this when the user wants to revisit a conversation later.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_EMAIL_READUpdate email status (read/unread, starred, snoozed)

Input Parameters

string
required
boolean
array
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_THREAD_READMark a thread as fully read up to the latest reply. Use this after the user has finished catching up on a thread, or when you want to programmatically dismiss unread reply counts for a specific thread.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MARK_THREAD_UNREADMark a thread as unread so it reappears in the threads inbox with an unread badge. An optional reply_id marks that reply onward unread. Omit it to mark the whole thread unread. Restore accepts the prior cursor and its expected current cursor; a newer intent returns 409.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MERGE_CONTACTSMerge two CRM contacts that represent the same person/company. The secondary contact is deleted, and its activities and deals are re-linked to the primary. Use this when you discover duplicates (same email or name). The primary contact is the one kept; the secondary is removed.

Input Parameters

string
required
string
required
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MIGRATE_DOCUMENT_SOURCEActivate source-preserving editing on an existing document. Only its owner may migrate; the expected content hash prevents stale activation and the command ID makes retries idempotent.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MODIFY_CONTACT_GROUP_MEMBERSBulk add or remove contacts from a contact group. Idempotent — adding an already-present contact or removing an absent one is a no-op.

Input Parameters

string
required
array
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MOVE_SHEET_COLUMNMove a column to a new position. Rewrites dependent formulas so they follow the moved column to the same logical data, and re-anchors notes and comment anchors.

Input Parameters

string
required
string
integer
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_MOVE_SHEET_ROWMove a row to a new zero-based position, carrying its values, formatting, geometry and dependent references.

Input Parameters

string
required
string
integer
required
integer
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_DISMISSSoft-delete (hide from default feed). Preserved for audit / undismiss.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_LISTList notifications for the current user. Supports cursor pagination via ?cursor=; legacy offset pagination still works. Filters: resource_types, excluded_resource_types, event_types, unread_only; visibility toggles: include_dismissed, include_snoozed.

Input Parameters

string
string ("asc" | "desc")
Creation order; defaults to newest first. A cursor carries its own order.
string
string
string
string
string
Comma-separated event types to include.
string
string
Comma-separated resource types to include.
string ("true" | "false")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("true" | "false")
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Comma-separated resource types to exclude.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MARK_ALL_READMark every unread notification in the optional resource/event scope as read.

Input Parameters

string
string
string
Comma-separated event types to mark read.
string
Comma-separated resource types to mark read.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Comma-separated resource types to exclude.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MARK_READMark a single notification read. Returns was_unread — true only if THIS call flipped it. A consumer that gets false skips the work, so two processes on one identity cannot both act on one notification.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MARK_UNREADConvenience alias for PATCH /api/notifications/:id with {read:false}.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MUTE_CREATECreate or refresh your in-app/live notification suppression rule for resourceId, eventType, or both. Matching direct mentions are suppressed there too; email and push delivery are unchanged. This does not change a chat channel’s mute setting or notification preference. For ordinary channel mute/unmute use set_channel_muted. At least one selector is required; resourceId also requires resourceType. until=null or omitted means indefinite. A matching rule’s expiry is refreshed.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MUTE_DELETERemove a mute rule by id. Scoped to the owning user.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_MUTES_LISTList active mute rules. Pass ?include_expired=true to also see rules whose until has passed (these no longer suppress notifications).

Input Parameters

string
string
string ("true" | "false")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_SNOOZEHide until {until: ISO8601}. Pass {until: null} to clear snooze.

Input Parameters

string
required
string
ISO 8601 timestamp, or null to clear snooze.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_NOTIFICATIONS_UNDISMISSRestore a dismissed notification.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PATCH_CANVAS_ELEMENTUpdate one element’s fields (geometry, style, text, connector endpoints, lock). Use when moving, restyling, relabeling, or re-anchoring a single element. Provide only the fields to change; the element’s id and type stay fixed and every other element is untouched (per-element diff — never a full-board replace). Coordinates: board units, top-left origin, +x right / +y down — set x,y to move the top-left corner. Example: patch_canvas_element({ id: “<boardId>”, elId: “<elId>”, x: 240, y: 80 }) moves an element right by 140 units.

Input Parameters

number
Height in board units.
number
Width in board units.
number
Board x (top-left). +x right.
number
Board y (top-left). +y down.
number
Paint order (Arrange front/back): higher paints on top.
string
required
Canvas board id.
object
type connector only.
string
type image only.
string
type codeBlock only.
string
required
Element id within the board.
object
type connector only.
Navigational target (Link to…); send null to clear the link.
string
type frame only.
string
type metric only; send null to clear.
object
type connector only.
array
type swimlane only.
string ("straight" | "elbow" | "curved")
type connector only.
string ("rect" | "roundedRect" | "ellipse" | "diamond" | "parallelogram" | "cylinder")
type shape only.
object
string
type metric only; send null to show the report’s name.
boolean
A locked element rejects geometry/content mutation until unlocked.
string
type metric only.
string
type metric only; send null to inherit the frame’s or board’s window.
string
The element’s text: a plain string (“Ship the beta”), or ProseMirror document JSON for formatting. type sticky, text, shape only.
string
Owning frame id; send null to detach the element from its frame (clear).
string
Group membership; send null to ungroup (clear).
object
type image only.
string
type connector only; send null to remove the endArrow property.
string
Code language; send null to remove the language property. type codeBlock only.
number
Degrees about the element’s center.
string
type metric only; send null to show the trend chart.
string
type metric only; send null to show the change.
string
type connector only; send null to remove the startArrow property.
string ("horizontal" | "vertical")
type swimlane only.
string
type frame only; send null to clear.
number
type frame only.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PATCH_USERS_NOTIFICATION_PREFERENCESPartial update of notification preferences. Unknown keys → 400. Non-boolean values → 400.

Input Parameters

boolean
Send email when this user is @mentioned in a comment or message. Default: true.
boolean
Send email when a deal owned by this user is marked won. Default: true.
boolean
Send email when a deal owned by this user is marked lost. Default: true.
boolean
Send transactional email when someone comments on a doc/task/etc. owned by this user. Default: true.
boolean
Send email when a task is assigned to this user. Default: true.
boolean
Client-only UX cue. Update the tab title with (N) Ambiguous when the tab has unread notifications. Default: false.
boolean
Send email when a document, sheet, slide, wiki page, file, or calendar is shared with this user. Default: true.
boolean
Client-only UX cue. Play a chime when a new notification arrives in this browser tab. Default: false.
boolean
Client-only UX cue. Show an OS-level browser push notification. Default: false.
Slug: AMBIGUOUS_MCP_PAUSE_COWORKERPause coworker (stops scheduled executions).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PERMANENT_DELETE_FILEPermanently delete a trashed file. Needs the owner rung; shared-drive content additionally needs a manager of that drive. A caller who can see the file without that authority gets 403. Irreversible — confirm with user first.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_CLOSEClose a poll to further voting (creator or channel admin).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_CREATECreate a poll in a channel. Creator must be a channel member.

Input Parameters

array
required
string
string
required
boolean
string
required
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_DELETEDelete a poll (creator or channel admin).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_GETPoll details (question, options, the caller’s votes).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_GET_BY_MESSAGEPoll results for the poll attached to a chat message.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_RESULTSTallied poll results (respects anonymity).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_UNVOTERemove the caller’s vote for a poll option.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_POLL_VOTECast a vote for a poll option.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_MEMBERS_ADDAdd a member. Body {user_id, role?} — or {team_id, role?} for a team share. A project editor may add, capped at its own role: granting a role above it is refused 403. Notifies the new member.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_MEMBERS_LISTList project members.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_MEMBERS_REMOVERemove a grant from the project. The path id is the principal id: a user by default, or a team with ?type=team. Notifies the removed user (unless self-removal). The Everyone team’s row is refused — workspace access is set through the project’s visibility, which is its only control.

Input Parameters

string
required
string ("user" | "team")
Which principal the path id names — {userId} is a principal id, not necessarily a user. Defaults to user.
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_MEMBERS_UPDATE_ROLEChange a member’s role.

Input Parameters

string
required
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_NOTIFICATION_PREF_GETGet the caller’s notification preference for the project.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_NOTIFICATION_PREF_SETSet the caller’s notification preference (level) for the project.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_TEMPLATES_APPLYCreate a new project from a template. Pass {name, description} in the body.

Input Parameters

string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_TEMPLATES_CREATECreate a project template.

Input Parameters

string
string
string
object
string ("private" | "team" | "workspace")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_TEMPLATES_DELETEDelete a project template.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_TEMPLATES_GETGet a single project template.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_TEMPLATES_LISTList project templates in the workspace.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_UPDATES_DELETEDelete a status update. Author or admin only.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROJECT_UPDATES_EDITEdit a status update. Author or admin only.

Input Parameters

string
required
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PROTECT_RANGEProtect a range in a spreadsheet. Protected ranges restrict editing to users in editorUserIds. Set warningOnly to true for soft warnings instead of hard blocks.

Input Parameters

string
required
string
string
boolean
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PUBLISH_CALENDARPublish a calendar as a public read-only .ics feed URL (no auth required). Returns a shareable feed URL that anyone can subscribe to from Google/Apple/Outlook Calendar. Anyone holding the URL can read every event on the calendar until it is unpublished or its URL is rotated.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_PUBLISH_FORMPublish a form so it accepts public responses. Semantic shortcut for PATCH /api/forms/{id} with is_published=true; same validation (every field needs a non-empty label).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_QUERY_WIKI_DATABASEQuery rows from an inline database with optional view, filter, and sort. Returns paginated results.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REALTIME_EXCHANGE_CONNECTION_CAPABILITYExchange the caller’s normal credential (JWT or ak_ API key) for a short-lived realtime connection capability scoped to exactly the caller’s own workspace and credential session. Takes no input — workspace, principal and session are read off the authenticated credential, never a request field, so the endpoint has no field a caller could set to another principal’s value. The capability names no resource, channel or operation: object-scoped channels each need their own resource capability, and every durable mutation is independently re-authorized API-side. Refused with 429 + Retry-After when the per-principal rate budget or this instance’s concurrent database-admission budget is exhausted.

Input Parameters

string
Optional random session correlation UUID. Presentation-only: never authority, routing input, or durable identity.
Slug: AMBIGUOUS_MCP_REALTIME_EXCHANGE_RESOURCE_CAPABILITYExchange the caller’s normal credential for a short-lived capability over ONE object-scoped channel. The caller names the channel; it never names its own authority — the granted operations are resolved from the caller’s real role on that object through the same can() seam the REST surface authorizes with, so the capability and a later durable commit cannot disagree about what this principal may do. operations may narrow that set and may never widen it: a request naming an operation the caller does not hold is refused rather than quietly reduced, because a clamped token lets a client believe it may write and discover otherwise only as frames dropped at the edge. An object the caller cannot reach answers 404 exactly as an absent one does.

Input Parameters

string
required
The object-scoped mux channel this capability is for, e.g. doc:<uuid>. Parsed by the shared channel classifier; a static, control or unrecognized channel is refused.
array
Optional narrowing. Omit to receive exactly what the caller’s role on the object grants. When present it must be a non-empty, duplicate-free SUBSET of that set; a request for an operation the caller does not hold is refused, never quietly reduced.
string
Optional random session correlation UUID. Presentation-only: never authority, routing input, or durable identity.
Slug: AMBIGUOUS_MCP_RECALCULATE_LEAD_SCORESRecalculate lead scores for all contacts in the workspace. Use this after creating or updating scoring rules so existing contacts pick up the new scoring.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REGISTER_CUSTOM_DOMAINRegister a custom email domain as a pending row; ownership must be verified via DNS TXT before sending is enabled. Requires admin role.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_ACCESSRemove a named grant, pending invitation or link access on a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar. Give exactly one user_id, team_id, pending_share_id (unaccepted invitation), or link=true (restricts the link tier; unavailable on calendars). To remove broad access while retaining explicit collaborators use set_visibility(visibility=restricted), not Everyone removal.

Input Parameters

string
required
ID of the resource whose access is being managed, from that resource’s own read or list result. A permission entry’s id identifies its user or team, not the resource; supply that recipient separately as user_id or team_id.
string
string
string
The specific named team’s ID, separate from the resource id. For the entire workspace audience, use set_visibility instead of managing the system Everyone team as a named share.
string
The specific person’s ID, separate from the resource id. On update/removal, use the user ID from that resource’s permission entry.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_FORWARDING_ADDRESSRemove a forwarding address

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_PIPELINE_MEMBERRemove a user or team from a CRM pipeline. The principalId is the user_id or team_id of the member to remove.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_ROLERemove a role from a user. Requires admin role.

Input Parameters

string
required
Role name to remove.
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_SHARED_DRIVE_MEMBERRemove a shared drive member (manager-only; cannot remove last manager).

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_SHEET_COLUMNRemove a column from a sheet tab by column ID. Use ?sheet= to target a tab other than the first.

Input Parameters

string
required
string
Tab name; defaults to the first tab.
string
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_SHEET_TABRemove a sheet tab by name. Cannot remove the last remaining tab.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_SLIDERemove the slide at the given zero-based index.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REMOVE_TASK_ATTACHMENTRemove a file attachment from a task. Does not delete the Drive file.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RENAME_DOCUMENT_VERSIONRename a version snapshot of a document. Useful for labeling meaningful versions (e.g., “Pre-launch draft”, “Board approved”). Requires editor permission.

Input Parameters

string
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RENAME_SHEET_TABRename an existing sheet tab.

Input Parameters

string
required
string
Alias for new_name.
string
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REORDER_MAIL_LABELSReorder the mail labels shown in the sidebar.

Input Parameters

string
string
array
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REORDER_MAIL_RULESReorder the mail rules to change which runs first.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REORDER_SLIDESReorder slides in a presentation. Provide the full list of slide indices in the desired new order. Example: [2, 0, 1, 3] moves the third slide to the front.

Input Parameters

string
required
array
required
New slide order — array of original indices in the desired sequence.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REPLACE_NAMED_RANGE_CONTENTReplace all content within a named range with new content. Used for template-based document generation — define named ranges as placeholders, then call this to fill each one. The named range must have positional anchors (startNodeId/endNodeId). Content can be Markdown text or PM JSON. Returns 409 if the anchored nodes no longer exist (stale range after CRDT edits).

Input Parameters

string
required
string
required
string
required
Markdown string OR ProseMirror node / node array. Server normalizes to PM JSON.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REPLACE_SHAPES_WITH_IMAGEReplace text placeholder elements with an image across all slides. Finds text elements whose text matches the search string and replaces them with image elements at the same position and size. Like Google Slides ReplaceAllShapesWithImage — useful for template-based workflows where placeholder shapes like {{logo}} are swapped with actual images.

Input Parameters

string
required
string
required
string
required
boolean
string ("CENTER_INSIDE" | "CENTER_CROP")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REPLACE_SHEET_TABReplace a sheet tab’s columns and/or rows wholesale. Use for bulk data replacement. Use update_cells for surgical edits.

Input Parameters

string
required
array
string ("visible" | "hidden" | "veryHidden")
array
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REQUEST_ACCESSAsk the owner of a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar, task, project, or CRM pipeline for access at a role higher than any you hold. Documents, Drive items and wiki pages offer viewer, commenter and editor; forms and calendars viewer and editor; projects commenter and editor; tasks editor; pipelines member. Returns 409 while a request is already open.

Input Parameters

string
required
string ("viewer" | "commenter" | "editor" | "member")
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESCHEDULE_SCHEDULED_EMAILChange the delivery time of a pending scheduled email without changing its content.

Input Parameters

string
required
string
required
Future ISO-8601 delivery time.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESEND_FORWARDING_VERIFICATIONResend verification email

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESTORE_FILERestore a file from trash. Needs the owner rung (the owner, the owner of a folder above it, or a manager of its shared drive); a caller who can see the file without it gets 403.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESTORE_SHEET_STRUCTUREUndo or redo a structural change receipt without overwriting unrelated later edits.

Input Parameters

string
required
object
required
string ("undo" | "redo")
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESTORE_TASKRestore a soft-deleted task when the caller has task editor access.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESTORE_WIKI_SYNCED_BLOCKRestore a previously deleted synced block. Embedding pages will render the block again instead of showing error chips.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RESUME_COWORKERResume a paused coworker.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REVERT_WIKI_PAGE_VERSIONRevert a wiki page to a previous version snapshot. This replaces the current content with the version’s content and rebuilds the page’s collaborative state from it. A snapshot of the current state is automatically created before reverting. This is destructive for the in-progress edit — always confirm with the user first.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REVOKE_API_KEYRevoke an API key. Immediate — any requests using the key will fail. Requires admin role.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_REVOKE_IDENTITY_API_KEYRevoke (permanently delete) one of the calling user’s own API keys. 404 if the key doesn’t belong to the calling user. Returns 204 No Content on success.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_ROTATE_CALENDAR_PUBLISH_URLRotate a published calendar’s read-only subscription URL. The previous URL is revoked immediately.

Input Parameters

string
required
string
required
Required. Any unique string, such as a UUID. Retry with the same key for the same URL; an earlier rotation’s key returns 409.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RSVP_EMAIL_INVITERSVP to a calendar invite on an email.

Input Parameters

string
required
string ("accepted" | "declined" | "tentative")
required
RSVP response on an inbound calendar invite.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RSVP_EVENTRSVP to a calendar event that the user is invited to. Use this when the user asks to accept, decline, or mark tentative on an event invitation.

Input Parameters

string
required
string ("accepted" | "declined" | "tentative" | "needs_action")
required
RSVP state for an attendee.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_RUN_DATA_CONNECTORExecute a data connector: fetch the latest data and write it to the connector’s target cells. Returns the connector with updated last-run metadata.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SAVE_MESSAGEBookmark an EXISTING chat message in the current user’s private Later/saved list. Resolve the original message_id with search_chat_messages or get_channel_messages when it is not supplied. Does not post or copy a message, and does not set a timed reminder (use set_reminder for that). Saving an already-saved message is a no-op.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SCAN_BUSINESS_CARDOCR a photo of a business card and extract structured contact fields (name, title, company, email, phone, website, address, notes). Returns JSON with each field nullable when not present on the card. Use when the user uploads or references a business card image and wants to add the contact to CRM. The image must be passed as a base64 data URL (data:image/jpeg;base64,…) of an image format Gemini Vision supports (JPEG, PNG, WebP, HEIC). Max 6 MB.

Input Parameters

string
required
Base64-encoded image as a data: URL (data:image/png;base64,...). Capped at ~6MB of raw image data to protect the upstream OCR call.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_CALENDAR_EVENTSFull-text search across all calendar events for the current workspace. Returns matching events with id, title, start/end times, and calendar info. Use this when the user asks to find a specific event by name or description keyword.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_CHAT_MESSAGESFind existing chat messages by keyword, phrase, or topic across the caller’s accessible channels. Results include the message id and channel context needed to bookmark, remind, react, reply, or edit that message. Use channel_id to restrict the search to a known channel; this read does not post messages.

Input Parameters

string
Search text. Empty/missing returns no results.
string
Max results (default 25, cap 50).
string
string
string
Restrict the search to one channel.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_MAILFull-text + operator search (Gmail-style: from:, to:, cc:, bcc:, subject:, has:attachment, is:read|unread|starred, in:inbox|sent|drafts|trash|archive, label:, after:YYYY-MM-DD, before:YYYY-MM-DD, size:N, larger:N, smaller:N, “phrase”). cc:/bcc: filter by recipient type. size:/larger:/smaller: filter by body byte size.

Input Parameters

string
Operator-syntax query (Gmail-style).
integer
string ("full" | "headers" | "minimal")
Response shape: full (default), headers (envelope only), minimal (id + labels).
string
string
integer
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_PALETTECross-module command-palette search — every module including chat messages. q is the query string; limit caps results (default 30, max 50). Empty query returns an empty response. Module diversity is preserved. counts carries the per-module match total before the per-module cap.

Input Parameters

string
Search query string.
string
Max results (capped at 50, default 30).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_WIKICase-insensitive substring search across wiki page titles and Markdown content. Returns only pages the caller can view under the effective page-to-space permission rules, with id, title, space, and content snippets. Use this when the user asks to find information in the wiki, look up documentation, or search the knowledge base. More efficient than reading individual pages.

Input Parameters

string
required
string
string
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEARCH_WORKSPACESearch across every module in the user’s workspace (docs, sheets, slides, canvas, tasks, contacts, deals, channels, chat messages, wiki, forms, calendar, users, mail, files, teams, and saved Analytics reports for callers who can read them). Returns a flat list of results with module-aware metadata, plus counts — the per-module match total before the per-module cap. Optional module filter narrows the search to one or more modules; sort picks relevance or recency. Use this when the user asks to find something but you don’t know which module it lives in.

Input Parameters

array
Chat message state. Honored by messages alone; every other active module drops out of the result set.
array
Restrict to rows authored by these people, matched against each module’s author-equivalent (document owner, task assignee, message sender, mail sender) by display name or email. Multiple values widen the match.
string ("relevant" | "recent")
relevant (default) is the cross-module score order; recent orders the merged page by updated_at descending before slicing, so paging stays monotonic under either.
string
Keep only rows created on or after this date (YYYY-MM-DD, UTC). Same creation axis as before.
integer
string
Search query string.
string
Keep only rows created strictly before this date (YYYY-MM-DD, UTC). Bounds the row’s creation timestamp — mail uses its sent date — never its last-modified time.
integer
array
Restrict to specific modules (docs, sheets, slides, tasks, etc).
array
Chat channel names (no leading #). Honored by messages alone; every other active module drops out of the result set.
Restrict to rows that contain a link.
boolean
Restrict to rows that carry an attachment.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_DRAFT_EMAILSend a previously created draft email. The draft transitions from the drafts folder to sent, SES delivery is triggered, and recipient inbox copies are created. Use this when the user wants to send a draft they previously saved. A send is not always a delivery: when the sender is an agent limited to workspace recipients and any To/Cc/Bcc address is external, the WHOLE email is queued for a human decision instead of being sent — the response carries delivery_status: pending_approval and pending_approval.review_id, and nothing has reached the recipients. Report that state; do not report it as sent, and do not re-send it.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_EMAILSend an email from the current user. The body is written in Markdown and automatically converted to a beautifully formatted HTML email for delivery. Use this when the user asks to send an email, message someone, or share something via email. Supports to, cc, and bcc recipients. Recipients are specified by email address. A send is not always a delivery: when the sender is an agent limited to workspace recipients and any To/Cc/Bcc address is external, the WHOLE email is queued for a human decision instead of being sent — the response carries delivery_status: pending_approval and pending_approval.review_id, and nothing has reached the recipients. Report that state; do not report it as sent, and do not re-send it.

Input Parameters

array
array
Empty drafts allowed; required when sending.
array
string
array
string
string
string
string
string
HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text.
string
Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent.
string
Attach the message to an existing thread.
string
string
Send-as address (must be a verified alias/domain).
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
array
array
string
string
ISO-8601. Defers send.
string
Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send.
string
Legacy alias for scheduled_at.
array
Drive file IDs to attach.
string
Retry key scoped to the sender and mailbox. Repeat the same key and send parameters to receive the original send; different parameters return 409. Also accepted as body.idempotency_key. The header takes precedence.
string
Optional retry key. Reusing the same key with the same send request returns the original send.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Archive this thread once the reply succeeds.
boolean
integer
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_MESSAGEPost a NEW message visible to the chat channel’s members, or send a thread reply. Use for requested communication, not for finding, bookmarking, or reminding about an existing message: those actions use search_chat_messages/get_channel_messages then save_message/set_reminder on the returned message id. Content is Markdown with @mentions, code blocks, and links. Use the current channel ID when supplied by page context. To reply, set thread_id to the original parent message’s id. To attach a file, upload it with drive_file_upload_proxy (source=chat) and include [name](drive://&lt;file_id&gt;) in content.

Input Parameters

string
required
Markdown body. To attach a file, upload it first (POST /api/drive/upload-proxy with source=chat), then include [name](drive://&lt;file_id&gt;) here; append ?w=<width>&h=<height> from the upload response when it returns both, so the preview keeps its size while it loads. One link per attachment.
string
Legacy alias for thread_id.
string
string
required
string
Per-channel idempotency key that stitches a top-level message into an existing thread by key.
string
ISO 8601 time to publish this NEW message to channel members, only when new publication is requested. A channel reference in a personal reminder request identifies its source message, not recipients, and is not a request to publish. Use set_reminder for a caller-only notification about an existing message.
string
Legacy alias for scheduled_at: publishes a NEW channel-visible message only when requested. Naming a source channel for a personal reminder does not request new publication.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
Send this message as its own block — it renders its own header even where author + timestamp would group it under the previous message.
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_QUOTESend a CRM quote via email to the contact. Marks the quote as ‘sent’. By default, sends to the linked contact’s email address.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_SCHEDULED_MESSAGE_NOWDeliver a pending scheduled message immediately instead of waiting for its scheduled time. Flips the message to sent and fans it out to the channel right now. Fails if the message has already been sent or cancelled. Use this when the user wants to send a queued message without waiting.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SEND_TEST_NOTIFICATION_EMAILSend a test notification email (useful for checking email rendering and deliverability). Requires admin role.

Input Parameters

string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_CHANNEL_ARCHIVEDArchive or unarchive a chat channel. Archiving freezes writes for everyone. Requires the same administrative authority as the individual archive and unarchive actions.

Input Parameters

string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_CHANNEL_MUTEDMute or unmute a chat channel for yourself, including DMs, temporarily or indefinitely. Muting silences ordinary message, keyword and subscribed-thread alerts and removes the channel-presence badge contribution; direct mentions and broadcasts still reach you. This changes the channel mute setting, not its notification preference or a delivery-suppression rule. muted=true optionally accepts until or duration_ms; omit both for indefinite mute. muted=false cannot include timing fields.

Input Parameters

string
required
boolean
required
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_DECK_FONTSSet the heading and/or body font across a whole presentation: every text box, shape and table on every slide and master, group children and per-run rich-text fonts included. Text at 28px or larger takes the heading font; smaller text and tables take the body font. Fonts are a closed list. The saved deck is re-read before responding: a 409 means some elements still use another font, so the change is incomplete and must not be reported as done.

Input Parameters

string
required
string ("Inter" | "Inter Light" | "Lato" | "Lato Black" | "Helvetica Light" | "Inter Display" | "JetBrains Mono" | "Arial" | "Arimo" | "Arial Black" | "Arial Narrow" | "Georgia" | "Times New Roman" | "Tinos" | "Courier New" | "Verdana" | "Trebuchet MS" | "Palatino Linotype" | "Impact")
Font for body text — text below 28px, and every table.
string ("Inter" | "Inter Light" | "Lato" | "Lato Black" | "Helvetica Light" | "Inter Display" | "JetBrains Mono" | "Arial" | "Arimo" | "Arial Black" | "Arial Narrow" | "Georgia" | "Times New Roman" | "Tinos" | "Courier New" | "Verdana" | "Trebuchet MS" | "Palatino Linotype" | "Impact")
Font for headings and titles — text at 28px or larger.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_DEFAULT_SEND_ASSet the user’s default send-as address.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_DOCS_PAGE_LAYOUT_DEFAULTSet the caller’s default layout for new Docs (pageless_default: true = pageless, false = pages). Affects only Docs created afterwards; existing Docs keep their layout.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_DOCUMENT_FOOTNOTESSet footnote body content on a document. Replaces all existing footnoteBody nodes. Each footnote must have a footnoteId and either a text string (auto-wrapped in a paragraph) or a content array (PM JSON). To add inline footnote references in the body text, use update_document with PM JSON content containing footnoteRef nodes with matching footnoteIds.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_DOCUMENT_HEADERS_FOOTERSSet default, first-page, and even-page headers and footers. Each field accepts a plain text string (auto-wrapped in a paragraph), a ProseMirror JSON node, or null to remove. Omit a field to leave unchanged.

Input Parameters

string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_EMAIL_ARCHIVEDArchive an email or return it to the inbox. archived=true archives; false unarchives. Existing mailbox access rules apply.

Input Parameters

string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_EMAIL_SIGNATURESet the workspace default email signature. Pass null (or omit markdown) to clear. Requires admin role.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_MAIL_SIGNATURESet personal email signature. Pass null to clear.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_MAIL_THREAD_ASSIGNEEAssign a shared-mailbox conversation to a member, or clear its assignment with user_id=null. Does not change its folder.

Input Parameters

string
required
string
string
string
required
A mailbox member’s ID, or null to clear the assignment.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_MAIL_THREAD_MUTEDMute or unmute a mail conversation. muted=true moves it out of the inbox and keeps future replies muted; false restores it. mailbox_id selects a shared mailbox.

Input Parameters

string
required
boolean
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_NOTIFICATION_KEYWORDSReplace the current user’s notification keyword list. Keywords are case-insensitive, whole-word, and capped at 20 entries (each up to 50 characters). Duplicates/empties are dropped. Use this when the user says ‘alert me whenever someone mentions X’ or ‘stop notifying me about Y’.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_PINNED_HEADER_ROWSSet the number of pinned (repeating) header rows on a table in a document. Pinned header rows repeat on every printed page when the table spans multiple pages in exported .docx and .pdf files. Set to 0 to clear the pinned header rows attribute.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
required
Top-level content index of the target table.
integer
required
Number of header rows to pin. Set to 0 to clear.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_REACTIONAdd or remove your emoji reaction on a chat message or a document, task, wiki, mail-thread or Code comment. The target is resolved from ID. present=true adds; false removes. Existing parent visibility, workspace custom-emoji rules, broadcast-message identity, and missing-reaction errors apply.

Input Parameters

string
required
string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_READ_RECEIPTS_DEFAULTToggle the default for new compose windows

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_REMINDERRemind only the signed-in user about an existing chat message at a future time. A channel named in a personal reminder request locates the source message; it is not an audience or a request to post there. When message_id is unknown, first find the original with search_chat_messages or get_channel_messages; an unknown ID does not mean the message is absent. If the target cannot be identified, ask for clarification instead of publishing a replacement. Automatically bookmarks the original in Later. remind_at is an ISO 8601 datetime and must be in the future.

Input Parameters

string
required
Future ISO 8601 time to notify only the signed-in user about the existing message. Does not send or schedule a new message to the channel’s members.
string
required
Channel containing the existing message to be reminded about. This identifies the source message, not notification recipients; only the signed-in user receives the reminder.
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_RESOURCE_STARREDAdd or remove favorites (star/unstar) for documents, spreadsheets, presentations, canvases, Drive items, forms, channels or teams. Resource type is resolved from ID; existing starring/access rules apply. Tasks-sidebar view/project pins use tasks_favorites_add/remove instead.

Input Parameters

string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_SHEET_VALIDATIONSet a data-validation rule on a spreadsheet cell range in A1 notation. Supports dropdown/range lists, numeric/text/date conditions, checkbox values, and custom formulas. Numeric constraints use JSON numbers, not numeric strings. Strict configures invalid-entry rejection rather than warnings in the editor; API cell writes do not enforce these rules.

Input Parameters

string
required
object
Data-validation rule with required type (ANY, ONE_OF_LIST, ONE_OF_RANGE, NUMBER_BETWEEN, NUMBER_NOT_BETWEEN, NUMBER_GREATER, NUMBER_GREATER_THAN_EQ, NUMBER_LESS, NUMBER_LESS_THAN_EQ, NUMBER_EQUAL, NUMBER_NOT_EQ, TEXT_CONTAINS, TEXT_NOT_CONTAINS, TEXT_EQ, DATE_IS, DATE_BEFORE, DATE_AFTER, DATE_BETWEEN, BOOLEAN, CUSTOM_FORMULA). Supported keys: type, values, numberKind, strict, allowBlank, showDropdown, showInputMessage, inputTitle, inputMessage, showErrorMessage, errorTitle, errorMessage, errorStyle. values contains JSON numbers for numeric constraints, strings for text/date/custom-formula constraints, or the permitted list/checkbox choices. Between constraints use two values; single-bound comparisons and custom formulas use one; ONE_OF_LIST requires a nonempty list; BOOLEAN may omit values or supply checked and unchecked values. strict: true rejects invalid editor entries; strict: false allows invalid entries without validation warnings. API cell writes do not enforce these rules.
string
A1-style cell range, optionally qualified by a tab name. An unqualified range uses the first tab.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_SNOOZE_PRESETSSet the user’s custom snooze quick-presets (up to 10). Pass an empty array to reset to defaults.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_SWIPE_ACTIONSSet the caller’s own mail-row swipe actions — one action per direction, chosen from archive, trash, read, star, snooze.

Input Parameters

string ("archive" | "trash" | "read" | "star" | "snooze")
required
Action bound to one swipe direction on a mail row.
string ("archive" | "trash" | "read" | "star" | "snooze")
required
Action bound to one swipe direction on a mail row.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_TASK_ARCHIVEDArchive or unarchive a task. Archive is separate from Trash; archived=false does not restore a trashed task. Existing project and task permissions apply.

Input Parameters

string
required
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_TASK_SUBSCRIPTIONSubscribe or unsubscribe yourself from a task’s notifications. When subscribed=true, user_id may select another subscriber under the existing subscription rules; unsubscribe applies only to yourself. Subscription does not grant task access.

Input Parameters

string
required
string
boolean
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_UNDO_SEND_SETTINGSet undo-send duration (seconds).

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
required
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_USER_DNDEnable or disable Do-Not-Disturb for the current user. Pass an ISO-8601 timestamp in the future to snooze notifications until that time, or pass null to disable DND immediately. Use this when the user says ‘mute me for an hour’, ‘DND until 5pm’, or ‘turn off DND’.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_USER_STATUSSet the current user’s chat status — an emoji, short text (<=100 chars), and optional auto-clear timestamp. All fields are optional; pass null to clear a single field. Use this when the user says things like ‘set my status to lunch until 1pm’ or ‘I’m on vacation’.

Input Parameters

string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_VACATION_SETTINGSUpdate vacation auto-reply settings.

Input Parameters

boolean
string
string
string
string
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SET_VISIBILITYSet broad access to a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar: restricted removes broad tiers but keeps owner and explicit collaborators; workspace covers current/future workspace humans and agents at workspaceRole; link/public use linkPermission, optionally behind linkPassword until linkExpiresAt. Use this for Everyone/workspace access, not individual grants or the Everyone entry. Calendars allow only restricted/workspace; forms publish responder links separately. Unsupported fields are rejected.

Input Parameters

string
required
string
One of the values in VALID_VISIBILITY_VALUES. What each one grants, measured against both read routes: restricted: the owner and explicit shares only. workspace: every member of the owning workspace, at workspace_role. A caller outside that workspace gets 404 on both routes. link and public: identical in behaviour today. Both grant every workspace member a role, and both publish the document to everyone outside the workspace at link_permission, signed in or not. A caller with no credential uses the ordinary routes (GET /api/documents/{id}, and the edits and comments link_permission allows) exactly as a signed-in non-member does, or reads a snapshot at GET /api/public/documents/{id}. Every outside caller sends X-Link-Password on a gated link: without it a caller with no credential gets 401 password_required and a signed-in non-member gets 404. Past link_expires_at both get 404, so an elapsed link is indistinguishable from an id that was never shared and never reports expiry. Handing a document to an agent in another workspace: public or link plus GET /api/documents/{id} works whether or not it signs in; leave link_password unset if it cannot.
Empty string or null clears the password; non-empty hashes + stores.
ISO 8601 timestamp, or null to clear.
string ("viewer" | "commenter" | "editor")
Role granted to every workspace member when visibility is workspace. Stored as the workspace-wide share itself, so this is how ‘everyone can edit’ is expressed. Defaults to viewer on first switch to workspace; only applies when visibility is (or stays) workspace.
What anyone outside the workspace can do through the document’s link, signed in or not. Defaults to viewer. Edits and comments made without signing in are recorded as Anonymous.
boolean
The owner’s opt-out. true (the default) lets an editor grant, change and revoke shares and set the tier; false moves every share operation back to the owner alone. Owner-only: a lower rung sending it is refused 403 editors_can_share_owner_only.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SHARED_WITH_ME_HIDEHide one row from the caller’s own Shared-with-me list. Revokes nothing — the grant is untouched and the resource stays reachable by its id or link; only the list entry goes. 404 when the caller holds no live grant or the key lacks that resource’s read scope. Idempotent.

Input Parameters

string
required
string ("document" | "file" | "wiki_page" | "form" | "calendar")
required
Which Pat8 surface the row is on. document covers docs, sheets and slides — they are one table and one permission model.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SHARED_WITH_ME_LISTEverything shared with the calling account through a direct grant, a team grant, or a bound external grant, across docs / sheets / slides, Drive, Wiki, Forms and Calendar — and across every workspace and identity the account owns. Excludes what the account owns, and excludes workspace-tier access, which is standing authority rather than a share. An API key sees only resource families within its read scopes. Newest share first. scope=workspace narrows discovery to resources in the authenticated current workspace without changing access.

Input Parameters

integer
string ("account" | "workspace")
Account-wide by default. workspace lists only resources in the authenticated current workspace; grants and resource access remain unchanged.
string
Opaque; from a previous page’s next_cursor. Absent starts at the newest share.
string
string
string ("doc" | "sheet" | "slide")
Narrow the document surface to one of its three types. Docs, sheets and slides share one table, so resource_type=document alone returns all three. No effect on the other four surfaces.
string ("document" | "file" | "wiki_page" | "form" | "calendar")
Narrow to one surface. Absent returns all five — the point of the route.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SHARED_WITH_ME_UNDO_LEAVEUndo a “Remove me”: restore the exact grant the caller removed, from the undo_token the leave call returned. The token is bound to the caller, single-use, and lasts ten minutes. An outside grant is re-checked against the workspace’s current outside-sharing policy. 400 undo_token_invalid / undo_token_expired / undo_token_used; 403 outside_sharing_off / outside_sharing_domain_not_allowed; 404 when the resource is gone or the key lacks its read scope.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SHEET_GET_DATAGet the spreadsheet as the structured JSON canvas. Returns the Sheet envelope: top-level metadata plus the structured sheet body nested under data (see SheetData). Read the tab list as response.data.sheets; columns and rows are under response.data.sheets[0], not at the response root.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SHEET_UPDATE_CELLSUpdate specific cells in a spreadsheet. Provide an array of cell updates, each specifying the row index (0-based), column ID, and new value. If the user is currently viewing a sheet, use the sheet ID from the page context.

Input Parameters

string
required
string
array
Alias for updates — accepted by the API client.
string
string
string
array
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Pass true to echo the updated cell values in the response.
Slug: AMBIGUOUS_MCP_SIGN_ADD_FIELDAdd a signature field to a signing document.

Input Parameters

number
required
number
required
number
required
number
required
string
required
integer
required
string ("signature" | "initial" | "text" | "date" | "checkbox" | "number" | "file")
required
boolean
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_ADD_SIGNERAdd a signer or CC recipient. An agent user can be a CC recipient but never a signer; adding one as a signer is refused.

Input Parameters

string
required
string
required
string ("signer" | "cc")
string
required
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_GET_CERTIFICATEDownload the Certificate of Completion for a completed document.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_GET_REFERENCESList signing documents that use this document as a source.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_PREPARE_SENDValidate signers and render the PDF preview (draft → preview_pending).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_REMOVE_FIELDRemove a field from a signing document.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_REMOVE_SIGNERRemove a signer or CC recipient from a draft signing document.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_REORDER_SIGNERSAtomically set the sequential signing order: the full ordered list of the document’s signer-role ids. Draft only.

Input Parameters

string
required
array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_UPDATE_FIELDReassign, reposition, resize, or change requiredness for a field on a draft signing document. The field id is stable — updates never re-create the field.

Input Parameters

number
number
number
number
string
required
string
required
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SIGN_VERIFY_DOCUMENTVerify the integrity and signature of a completed document.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_APPLY_TEMPLATEApply a slide template — built-in or workspace — to the deck or to a single slide.

Input Parameters

string
required
string ("all" | "current_slide")
required
all repaints the entire deck with the template; current_slide replaces just one slide with the template’s first slide.
string
required
ID of the template to apply (e.g. business-pitch).
object
Map of {{key}} → value substitutions. Unknown keys are left literal so the user can spot them.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
Required when scope = current_slide. Zero-based index of the slide to replace.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_LAYOUTS_LISTList the slide-level layouts the editor knows about.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_SAVE_AS_TEMPLATESave an existing deck as a reusable workspace template. Deep-copies the deck with fresh element IDs into a new workspace-visible template document; the source deck is left untouched. Returns the new template’s ID.

Input Parameters

string
required
string
required
Display name for the workspace template.
string
Optional description shown on the template card.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_STARStar a deck. Idempotent — re-starring is a no-op.

Input Parameters

string
required
Slug: AMBIGUOUS_MCP_SLIDE_STARS_LISTList IDs of slide decks the current user has starred.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_TEMPLATES_LISTList the built-in slide deck templates.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SLIDE_UNSTARUnstar a deck. Idempotent.

Input Parameters

string
required
Slug: AMBIGUOUS_MCP_SLIDE_USE_TEMPLATEStart a new deck from a template — built-in or workspace. Deep-copies the template deck with fresh element IDs into a new deck, substitutes {{key}} placeholders to bracketed prompts (e.g. {{client_name}} → [Client Name]), and returns the new deck’s ID.

Input Parameters

string
Optional title for the new deck. Defaults to the template’s name.
string
required
ID of the template to start a deck from — a built-in id (e.g. business-pitch) or a workspace template document id.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SNOOZE_EMAILSnooze an email until a datetime.

Input Parameters

string
required
string
required
ISO-8601 wake-up time.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SNOOZE_REMINDERRe-snooze an existing saved message by updating its remind_at time. Resets reminded to false so the scheduler picks it up again. Accepts ISO 8601 datetime string; must be in the future.

Input Parameters

string
required
Future ISO 8601 time to notify only the signed-in user about the existing message. Does not send or schedule a new message to the channel’s members.
string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SORT_SHEETSort a tab’s rows by one column, optionally within an exact filter range. Re-anchors formulas, comment anchors, and cell notes so nothing orphans.

Input Parameters

string
required
string
string
required
string ("asc" | "desc")
required
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_START_TASK_TIMERStart a time-tracking timer on a task for the current user. If another timer is already running for this user, it is stopped automatically (only one active timer per user).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_STOP_TASK_TIMERStop the current user’s active timer. The duration is accumulated onto the task’s time_spent_minutes total. Returns null if no timer is active.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SUBMIT_FEEDBACKTell Ambiguous what happened in your own words. Only description is required; do not choose a report category or supply a goal outcome. Optional context and attachments are welcome, never required. Ambiguous handles classification and triage. Accepts unauthenticated REST calls; valid credentials optionally identify the submitter. Rate-limited per user when authenticated and per IP otherwise. Body shape: {title?, description, priority?, screenshotDataUrl?, attachments?, context?} — see FeedbackInput. The submission is stored as a task in Ambiguous’s own Feedback project and the 200 carries that task’s id as the receipt; there is no receipt without a record, so a storage failure is a 500 and the caller should retry. Returns 503 with {error: "Feedback reporting not available"} when the intake is not configured (outside the contract error-code enum, surfaced via raw Response).

Input Parameters

string
object
string
array
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_SUBMIT_FORMSubmit a response to a published form, identified by its public slug or form ID. Data is a map keyed by field ID with user answers. Use when an agent is filling out a form on behalf of a user or when completing a structured data-entry task.

Input Parameters

object
Legacy alias for answers. Same payload.
string
required
object
Canonical wire name. Map of field_id -> respondent value. Either answers or data (alias) is required; sending both with disagreeing values returns 400.
string
Cloudflare Turnstile token (when captcha_enabled).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASK_ASSET_CREATEAdd an image to a task description as one of its own assets and get back the URL its body should store (/api/assets/{id}/content). Send the bytes as content_base64, source_file_id to copy a Drive file the caller can view, or source_url to import a public HTTPS image through the SSRF guard; neither source is referenced afterwards. The type is decided from the bytes and only images are accepted (415 otherwise); SVG uploads are sanitized before storage and refused with 415 when malformed. Stored SVG is sanitized on every read and served inline as image/svg+xml under a restrictive Content-Security-Policy; malformed stored SVG is refused with 404. Drive SVG downloads remain attachments. The bytes count against the container owner’s storage (413 past it). The same image added to the same container again returns the asset already held. The asset is never visible in Drive and is readable exactly when the container is.

Input Parameters

string
required
string
File name to keep with the image; defaults to image.
string
Declared type. The stored type is decided from the bytes.
string
Fetch a public HTTPS image into this container. Private network addresses and redirects to them are refused; the source URL is not stored in the body.
string
The image bytes, base64-encoded (no data: prefix).
string
Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASK_COLLABORATORS_ADDShare a task with one workspace member: grants editor on this task and its subtasks (never on its project) and subscribes them. A projectless task is shared by its creator or assignee; a project task by an editor on that project.

Input Parameters

string
required
string
required
The workspace member to share this task with. Subscribed on add.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASK_COLLABORATORS_LISTList the collaborators on a task — the people holding editor on it (and its subtasks) without a role on its project.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASK_COLLABORATORS_REMOVERevoke a task collaborator’s grant. The add-time subscription is left in place — it grants no access on its own.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_ACTIVITYList audit-log activity entries for a task (status changes, assignments, comments, label edits, etc.). Paginated via limit/offset.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_BATCHBatch-fetch up to 50 tasks by ID. Powers LinkedTaskItem hydration in Docs/Wiki.

Input Parameters

string
Comma-separated task IDs (max 50).
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_BY_KEYResolve a workspace-scoped task key (e.g. WS-123) to its task ID. Used by deep links and integrations.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_DELETESoft-delete a task. Only the creator can delete.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_EXPORTExport authorized tasks matching the selected filters as CSV (default) or JSON. CSV includes human-readable columns and a task_json column containing the complete public task representation. Owned description images are embedded; an unavailable or malformed owned image refuses the export with its task reference.

Input Parameters

string
Free-text search across title + description.
string
string
‘csv’ (default) | ‘json’. Validated by handler so the 400 error message is preserved.
string
string
Filter by system status. Comma-separated for multi-select.
string
Filter to tasks linked to this CRM deal.
string
Filter by cycle ID. none returns tasks with no cycle.
string
Filter by a single label ID (must be a UUID).
string
string
Pass ‘true’ to filter to tasks assigned to AI coworkers in the caller’s workspace.
string
Comma-separated label IDs (AND match).
string ("true" | "false")
Pass ‘true’ to filter to tasks with no project_id.
string
Filter to tasks linked to this CRM contact.
string
Filter by creator user ID.
string ("true" | "false")
Pass ‘true’ to return tasks linked to a CRM contact or deal.
string
string ("on_track" | "at_risk" | "breached" | "achieved" | "failed" | "not_applicable")
Match the worst actionable SLA leg. not_applicable requires a measured neutral leg and no actionable leg.
string
Pass ‘me’ to filter to tasks the caller is subscribed to.
string
Filter to tasks assigned to this user. unassigned to filter to unassigned.
string
ISO 8601 lower bound on updated_at.
string
YYYY-MM-DD upper bound (inclusive).
string ("true" | "false")
Pass ‘true’ to filter to tasks with a due date set.
string ("true" | "false")
Pass ‘true’ to filter out tasks blocked via task_relations.
string
Comma-separated label IDs (OR match).
string
Exclusive ISO 8601 upper bound on cancelled_at.
string
Inclusive ISO 8601 lower bound on cancelled_at.
string
ISO 8601 upper bound on completed_at.
string
ISO 8601 lower bound on completed_at.
string ("true" | "false")
Pass ‘true’ to include archived tasks (default: hidden).
string
string
YYYY-MM-DD lower bound (inclusive).
string
Filter by parent task ID. Special value null (string) returns top-level tasks only.
string
Filter by custom status ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
Pass ‘true’ to filter to tasks assigned to AI coworkers managed by the caller.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Comma-separated custom status IDs to exclude.
Slug: AMBIGUOUS_MCP_TASKS_FAVORITES_ADDPin a saved task view or project in your Tasks sidebar. For document, Drive, channel or team favorites, use set_resource_starred.

Input Parameters

string
required
string ("view" | "project")
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_FAVORITES_LISTList your Tasks-sidebar pins: saved views and projects, not starred documents, Drive items, channels or teams.

Input Parameters

string
Max items to return (per-endpoint default/cap).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_FAVORITES_REMOVEUnpin a saved task view or project from your Tasks sidebar, matching resource_type and resource_id. For other resource favorites, use set_resource_starred.

Input Parameters

string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_FAVORITES_REORDERReorder your Tasks-sidebar view/project pins using ordered_ids (favorite-row IDs, top-to-bottom), not resource IDs.

Input Parameters

array
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_INBOX_COUNTCount of triage-bucket tasks (untriaged + projects in ‘triage’ status). Powers the sidebar inbox badge.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_ASSIGNAssign a label to a task. Returns the task’s full label list.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_CREATECreate a workspace task label. Returns 409 if a label with the same name already exists in the group.

Input Parameters

string
string
required
string
Hex color (e.g. ‘#6B7280’).
string
string
Set to scope this label to a single project; omit (or null) for a workspace-level label.
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_DELETEDelete a task label. Existing assignments are removed.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_LISTList task labels visible in the workspace, grouped by group_name. Without project_id, returns workspace-level labels only. With project_id, returns workspace-level labels plus labels scoped to that project.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_REMOVERemove a label assignment from a task. Returns the task’s remaining label list.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_LABELS_UPDATEUpdate a task label.

Input Parameters

string
string
string
string
required
string
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_RELATIONS_BATCHBatch-fetch every relation type for up to 200 tasks. Powers relation overlays and sweeps.

Input Parameters

string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_RELATIONS_CREATECreate a relation between two tasks. blocking/blocked_by auto-creates the inverse edge. With type=duplicate, mark_as_duplicate=true the source task is cancelled with a system comment.

Input Parameters

string
required
string ("related" | "blocking" | "blocked_by" | "duplicate")
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
When type=duplicate: also cancel the source task and add a system comment.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_RELATIONS_DELETEDelete a task relation edge. Auto-deletes the inverse edge for blocking/blocked_by pairs.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_RELATIONS_LISTList edges in the task-relations graph for a task (related, blocking, blocked_by, duplicate).

Input Parameters

string
required
string
Max items to return (per-endpoint default/cap).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_REMOVE_SUBSCRIBERRemove another user’s subscription from a task. Requires task access.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SLA_DASHBOARDAggregate SLA metrics for the workspace (compliance rates, avg times, counts per status). Optionally scope to a project.

Input Parameters

string
Window in days (1..365, default 90).
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SLA_THRESHOLDSGet the workspace’s SLA thresholds (response + resolution times per priority). Auth-only.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SUBSCRIBEDList task IDs the caller is subscribed to (manual + auto-subscribed via creator/assignee/comment).

Input Parameters

string
Max items to return (per-endpoint default/cap).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SUBSCRIPTIONS_LISTList all users subscribed to a task (with the reason each is subscribed).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SUBSCRIPTION_STATUSCheck whether the current user is subscribed to a task (and the reason if so).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_SUBTASKSList immediate subtasks of a task (parent_task_id = :id).

Input Parameters

string
required
string
Max items to return (default 50, max 200).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_TEMPLATES_DELETEDelete a task template. Workspace admins or project admins only.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_TEMPLATES_GETGet a single task template by ID.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_TEMPLATES_UPDATEUpdate a task template. Workspace admins or project admins only.

Input Parameters

string
string
If set, only project admins + workspace admins can edit. Pass null for workspace-wide.
number
string
required
string
array
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
object
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_CREATECreate a saved task view (filter + layout). Setting is_shared: true exposes it to the workspace.

Input Parameters

string
string
required
string
boolean
string
number
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_DELETEDelete a saved task view.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_LAYOUT_GETGet the caller’s layout preferences for a view, or fall back to the view’s defaults. source indicates which.

Input Parameters

string
string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_LAYOUT_UPDATEUpsert the caller’s layout preferences for a view (per-project scope optional).

Input Parameters

string
string
required
string
string
string
string
string
boolean
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_LISTList task views accessible to the caller (own + shared + system defaults).

Input Parameters

string
Max items to return (per-endpoint default/cap).
string
string
string
Number of items to skip (default 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TASKS_VIEWS_UPDATEUpdate a saved task view (rename, change filters or layout defaults, toggle sharing).

Input Parameters

string
string
string
required
string
boolean
string
number
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Slug: AMBIGUOUS_MCP_TEAMS_CANCEL_JOIN_REQUESTCancel your own pending join request for this team.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_GET_SUBSCRIPTIONGet the caller’s email-delivery preference for the team. Returns {team_id, user_id, email_delivery}.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_JOINJoin a team. Open teams grant instant membership; request teams create a pending join request; invite teams reject.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_LEAVELeave a team. Cannot leave if you’re the last admin.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_MEMBERS_LISTPaginated member list. Private teams visible only to members or admins.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_MEMBERS_REMOVERemove a member. Admin only. Cannot remove the last admin.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_MEMBERS_UPDATE_ROLEChange a member’s role. Admin only. Cannot demote the last admin.

Input Parameters

string
required
string ("admin" | "member")
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_REQUESTS_APPROVEApprove a join request — adds the user as a member.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_REQUESTS_DENYDeny a join request.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_REQUESTS_LISTList pending join requests. Admin only.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_SEARCHABLESearch teams visible to the caller for the share dialog. Returns the union of public teams and private teams where the caller is a member. Supports case-insensitive name filtering via q and a configurable limit.

Input Parameters

string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TEAMS_UPDATE_SUBSCRIPTIONUpdate the caller’s email-delivery preference for the team. Body: {email_delivery: 'each' | 'daily_digest' | 'weekly_digest' | 'none'}. none is refused on the workspace-wide all-members list, which has no opt-out.

Input Parameters

string
required
string ("each" | "daily_digest" | "weekly_digest" | "none")
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TRANSFER_OWNERSHIPMake another principal owner of a document, spreadsheet, presentation, canvas, Drive item or form. The new owner needs a live explicit share: check list_access and do not re-grant an existing share. The previous owner keeps editor. Wiki and calendars cannot transfer ownership.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_TRASH_MAIL_THREADTrash all messages in a thread atomically. Moves every message in the thread to the trash folder.

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNBLOCK_SENDERUnblock by id or pattern.

Input Parameters

string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNDO_SEND_EMAILUndo an in-flight send within the undo-send window.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNENROLL_CONTACT_FROM_SEQUENCEPermanently remove a contact from a CRM sequence (terminal — sets status to ‘unenrolled’). The contact will not receive any further sequence steps. Returns 409 if already in a terminal status. Provide the enrollment ID (not the contact ID — find it via list_sequence_enrollments).

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNGROUP_SLIDE_ELEMENTSDissolve a group element on a slide back into independent top-level elements. Children positions are converted from group-relative to absolute coordinates. The group element is removed and its former children become top-level elements on the slide.

Input Parameters

string
required
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNPROTECT_RANGERemove a protected range from a spreadsheet by its ID. Returns 200 on success, 404 if the range does not exist.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNPUBLISH_CALENDARRevoke the public .ics feed for a calendar, making it private again.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNPUBLISH_FORMUnpublish a form so it stops accepting public responses. Semantic shortcut for PATCH /api/forms/{id} with is_published=false.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNSAVE_MESSAGERemove a saved (bookmarked) message from the user’s saved list. The message itself is untouched; only the personal bookmark is deleted.

Input Parameters

string
required
string
required
ID of an existing message in this channel, supplied by the user or returned by search_chat_messages/get_channel_messages. Not message text or a newly generated ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNTRASH_EMAILRestore a trashed email to inbox

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UNTRASH_MAIL_THREADRestore all trashed messages in a thread to inbox. Only affects messages currently in trash.

Input Parameters

string
string
string
required
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_ACCESSChange an existing named user/team grant on a document, spreadsheet, presentation, canvas, Drive item, form, wiki page, or calendar. id names the resource; exactly one user_id or team_id names the recipient. For the workspace tier use set_visibility and workspaceRole, not the Everyone entry. role and expires_at are set exactly, including shorter expiry.

Input Parameters

string
required
ID of the resource whose access is being managed, from that resource’s own read or list result. A permission entry’s id identifies its user or team, not the resource; supply that recipient separately as user_id or team_id.
string ("viewer" | "commenter" | "editor")
string
The specific named team’s ID, separate from the resource id. For the entire workspace audience, use set_visibility instead of managing the system Everyone team as a named share.
string
The specific person’s ID, separate from the resource id. On update/removal, use the user ID from that resource’s permission entry.
string
ISO 8601 deadline for the grant, or null for no expiry. Bounded by the shareExpiryMaxDays platform limit.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_API_KEYUpdate an API key’s name, scopes, or rate limit. Requires admin role.

Input Parameters

string
required
Resource ID.
string
array
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CANVASUpdate canvas-level metadata (title, preview cover). Use to rename a canvas or set its preview; never touches elements — use the element ops for board content. Coordinates: board units, top-left origin, +x right / +y down. Example: update_canvas({ id: “<boardId>”, title: “Renamed board” }).

Input Parameters

string
required
Canvas board id.
string
Owner-chosen preview cover.
string
Rename the board.
object
Board settings (grid style).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CANVAS_TIMERControl a board’s shared brainstorm countdown. Use to time-box a round: start (with duration_ms), pause (banks remaining time), resume (from banked time), or reset (clear). The server stamps ends_at from its own clock, so every participant renders the same countdown regardless of local clocks; the timer touches no elements. Coordinates: board units, top-left origin, +x right / +y down (unaffected by the timer). Example: update_canvas_timer({ id: “<boardId>”, action: “start”, duration_ms: 300000 }) starts a 5-minute countdown.

Input Parameters

string
required
Canvas board id.
string
required
integer
Countdown length in milliseconds (server stamps ends_at = now + this). action start only.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CHANNEL_MEMBER_ROLEChange a channel member’s role to ‘admin’ or ‘member’. Requires channel admin privileges. Use this when the user asks to promote or demote a member in a channel.

Input Parameters

string ("admin" | "member")
required
Role of a user inside one channel. Workspace role is separate. channel_members.role stores only these two and is nullable, so a member row can carry no role at all.
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CHARTPatch a chart’s config — type, title, data range, overlay position, or series styling. Only the fields you send are updated; the rest of the chart config is preserved.

Input Parameters

number
number
string
required
string
object
string ("bar" | "stackedBar" | "line" | "area" | "pie" | "donut" | "scatter" | "combo")
string
number
number
object
string
required
object
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CONDITIONAL_FORMATUpdate a conditional formatting rule by ID. Partial update: ranges or one canonical rule payload; replacing the kind clears the previous kind.

Input Parameters

string
required
array
string
required
object
object
object
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CONTACTUpdate an existing CRM contact’s fields. Provide only the fields you want to change. For interrupted sync recovery, read the contact and send expected_updated_at with only remaining changes. A 409 means the contact changed: read again and reconcile; never replay an earlier snapshot over newer values. If the user is currently viewing a contact, use the contact ID from the page context.

Input Parameters

string
required
string
string
string
string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
The updated_at from the last contact read. A stale revision returns 409; read again and submit only remaining changes.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CONTACT_GROUPUpdate an existing contact group’s name, color, or sort order. Group name must remain unique within the workspace.

Input Parameters

string
required
string
string
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_COWORKERUpdate coworker metadata (persona, focus areas, display name, avatar).

Input Parameters

string
required
string
string
array
string
string
Scope the coworker to these skills. Null clears the scope (full skill set).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CRM_PROPERTY_DEFINITIONUpdate a custom-property definition’s label or select options.

Input Parameters

string
required
string
array
boolean
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_CRM_VIEWUpdate a saved CRM view (rename, change filters, toggle default/shared).

Input Parameters

string
required
string
object
boolean
boolean
string
string ("contacts" | "companies" | "deals")
Which list page the saved view applies to.
string ("asc" | "desc")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DATA_CONNECTORUpdate a data connector’s name, config, target cells, or refresh schedule.

Input Parameters

string
required
string
object
string
string
number
number
string
string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DEALUpdate an existing CRM deal’s fields. Provide only the fields you want to change. Use this to move a deal to a new stage, update the amount, mark as won/lost, etc. If the user is currently viewing a deal, use the deal ID from the page context.

Input Parameters

string
required
string
string
string ("open" | "won" | "lost")
Lifecycle of a deal. won and lost close the deal; lost requires a lost_reason.
string
string
string
string
string
string
string
string
integer
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
Alias for contact_id. Either is accepted; sending both with different values returns 400.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DEAL_LINE_ITEMUpdate a deal line item (quantity, price, discount, name/description). Amount auto-recomputed. If sync_deal_amount defaults true, the deal’s total is also refreshed.

Input Parameters

string
required
string
number
string
integer
number
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
number
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DEAL_TEMPLATEUpdate a deal template. Providing line_items replaces the entire line-item list.

Input Parameters

string
required
string
string
string
string
boolean
array
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
object
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Slug: AMBIGUOUS_MCP_UPDATE_DECK_SETTINGSUpdate deck-level settings: theme, aspect ratio, default background. Changing aspect ratio rescales every slide’s elements proportionally; changing default background updates slides currently using the old default.

Input Parameters

string
required
string
string ("16:9" | "4:3")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
Camel-case alias accepted by the SDK (AMB-6729).
string
Camel-case alias accepted by the SDK.
string
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DOCUMENTEdit an existing document inline. Read the document first (get_document), modify the content, then pass the full updated text — content replaces the entire body. Do NOT create a new document to edit; version history preserves prior states. Accepts Markdown or ProseMirror JSON (HTML tolerated but lossy — drops listed in import_warnings). Provide only the fields you want to change.

Input Parameters

string
required
string
array
string
Replacement document body. For type=doc, accepts Markdown (recommended) or a ProseMirror JSON string. HTML is tolerated best-effort: a mapped tag becomes its node or mark, an unmapped tag is kept as literal text, and styling and decorative wrappers are dropped and listed in import_warnings on the response. To insert a native smart chip (the live-status chip the editor inserts), write @{task:<task-uuid>} in Markdown; doc, sheet, slide, canvas and wiki_page ids work the same way, and the chip takes the entity’s title when you can read it. Wrap a token in backticks to keep it as text. Mutually exclusive with operations.
array
Block-id-targeted edits as an alternative to content replacement. content field on each op is Markdown that is converted to PM JSON and applied at the matched blockId; @{task:<task-uuid>} becomes a native smart chip.
object
boolean
Commenter-relaxed write: content changes must carry track-change marks (auto-wrapped for agents).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DOCUMENT_PAGE_STYLESet page-level formatting for a document: margins (PT), page size (letter/A4/legal or {width, height} in PT), orientation (portrait/landscape). 72 PT = 1 inch. These settings control export output (.docx, .pdf). Pass an empty object to reset to defaults.

Input Parameters

string
required
object
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_DRAFT_EMAILUpdate an existing draft email. Only works on drafts (not sent messages). Use this to refine recipients, subject, or body of a draft across multiple iterations before sending.

Input Parameters

array
string
required
array
Empty drafts allowed; required when sending.
array
string
array
string
string
string
string
HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text.
string
Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent.
string
Attach the message to an existing thread.
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
array
array
string
string
Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send.
array
Drive file IDs to attach.
string
Optional retry key. Reusing the same key with the same send request returns the original send.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_EVENTUpdate an existing calendar event. Provide only the fields you want to change. Use this to reschedule, change attendees, update the description, or cancel an event. If the user is currently viewing an event, use the event ID from the page context.

Input Parameters

string
required
string
boolean
string
string
array
The event’s outside guests by email. On create it adds them; on update it replaces the outside-guest list (members are unaffected). An address a workspace member owns becomes a member guest instead.
string ("confirmed" | "tentative" | "cancelled" | "outofoffice")
Event status. outofoffice is used by the OOO responder.
boolean
string
string
string
array
Everyone on the event. Each entry is a string (UUID or email) or an iCal-natural object naming the attendee via email, id, or user_id; any other object key is ignored. An object with none of those three returns 400. An email no workspace member owns becomes an outside guest (returned in guests); it never creates a workspace invitation.
string
string
string ("default" | "outOfOffice" | "focusTime")
Calendar event type — a display/filter category. It does not change event behavior: OOO auto-decline keys on status: "outofoffice", and free/busy keys on transparency (independent inputs). The one behavioral value is agentDispatch, which routes a confirmation task to the assignee on create.
string ("default" | "public" | "private")
Visibility scope for the event.
string
string ("all" | "external_only" | "none")
Who gets an email about this change (CALENDAR P20). all — every guest; external_only — outside guests only; none — nobody. Omitted means none: sending is a deliberate choice, never a side effect.
string ("opaque" | "transparent")
Free/busy classification (RFC 5545 TRANSP). opaque = Busy (default; blocks availability). transparent = Free (e.g. focus time).
string
Video-call URL. Accepts explicit http(s) or a schemeless hostname/path, which is stored as absolute HTTPS. Any other scheme is rejected 400. Empty string or null clears the link and provider.
array
Existing-event ids the new_and_existing bulk-decline should leave untouched.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
boolean
string ("new_only" | "new_and_existing")
OOO auto-decline granularity (only meaningful when status=outofoffice). new_only declines invitations arriving during the window; new_and_existing also bulk-declines events already attended.
string
string
Auto-reply note sent with an OOO decline.
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
boolean
boolean
Slug: AMBIGUOUS_MCP_UPDATE_FORMUpdate an existing form’s title, description, fields, settings, or publish status. Use this when the user asks to edit a form, add/remove fields, publish/unpublish, or change form settings. If the user is currently viewing a form, use the resource ID from page context.

Input Parameters

string
required
string
string
array
object
object
string
string
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_FORM_VARIANTUpdate an A/B test variant’s name, traffic weight, or active status. Use when the user asks to rename a variant, adjust the traffic split, or pause/resume an experiment.

Input Parameters

string
required
string
required
string
boolean
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_IDENTITY_API_KEYUpdate name, scopes, or rate_limit on the calling user’s own API key. Returns the updated key. 404 if the key doesn’t belong to the calling user.

Input Parameters

string
required
string
array
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_MAIL_LABELUpdate a mail label’s name, color or sidebar order.

Input Parameters

string
string ("red" | "orange" | "yellow" | "green" | "blue" | "purple" | "pink" | "cyan" | "gray")
Built-in label palette.
string
string
string
required
string
string
Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don’t hold it.
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_MAIL_RULEUpdate a mail rule’s conditions or actions.

Input Parameters

string
array
boolean
string
required
array
string ("all" | "any")
integer
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_MAIL_TEMPLATEUpdate a saved mail template’s subject or body.

Input Parameters

string
string
string
string
HTML import normalized to Markdown when body_markdown is absent; wins over body_text.
string
Literal plain-text body normalized to Markdown when Markdown/HTML are absent.
integer
string
required
string
Canonical Markdown body; wins over HTML/text even when explicitly empty.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_NAMED_RANGEUpdate a named range or named expression with either an A1 range or an exact literal Excel expression; optionally rename it with newName. Names are matched case-insensitively. External-workbook expressions are preserved verbatim and remain unresolved.

Input Parameters

string
required
string
required
string
string
string
string ("fixed" | "caller-relative-a1")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_PIPELINEUpdate a pipeline’s name or stages. Providing stages replaces the entire stage list — include every stage you want to keep. Reordering is done by the order in the array.

Input Parameters

string
required
string
array
boolean
string ("workspace" | "private")
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_PIVOT_TABLEPatch a pivot table’s config — source range, row/column/value fields, totals toggles, source-tab name. Only the fields you send are updated; the rest of the pivot config is preserved. Pass a tab field to move the pivot to a different tab.

Input Parameters

string
required
string
string
string
required
array
boolean
string
array
array
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_PRODUCTUpdate a CRM product’s name, price or other fields.

Input Parameters

string
required
string
string
string
boolean
number
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("one_time" | "monthly" | "quarterly" | "yearly")
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_PROJECTUpdate a project’s name, description, icon, or color. Provide only the fields you want to change.

Input Parameters

string
required
string
string
string
string ("private" | "team" | "workspace")
string
string ("commenter" | "editor")
Role every workspace member holds while the project is workspace-visible. Stored as the workspace-wide share itself, so this is how a comment-only project is expressed. Defaults to editor on the FIRST switch to workspace — projects are open to the workspace by default — and a re-set naming no role keeps the stored role.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("fibonacci" | "linear" | "t-shirt")
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Slug: AMBIGUOUS_MCP_UPDATE_QUOTEUpdate a CRM quote. Providing line_items replaces the entire line-item list. Totals are auto-recomputed.

Input Parameters

string
required
string
string
string
string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired")
Quote lifecycle. accepted/rejected are terminal; viewed is recorded by the open-tracking pixel.
string
string
string
number
string
string
array
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_RESOURCE_COMMENTUpdate an existing task, wiki, mail-thread or Code comment by its comment ID. content edits text; expected_content checks the original text and rejects stale edits with 409; resolved changes thread resolution. Code content and resolution changes are separate updates. Existing author and resource permissions apply.

Input Parameters

string
required
string
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_ROLEUpdate a custom role’s name or permissions. Requires admin role.

Input Parameters

string
required
Resource ID.
string
string
array
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SCHEDULED_MESSAGEEdit the content or scheduled send time of a pending scheduled message before it’s sent. Fails if the message has already been sent or cancelled. Use this when the user wants to fix a typo in a scheduled message or reschedule it.

Input Parameters

string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SCORING_RULEUpdate a lead scoring rule (name, field, operator, value, points, is_active).

Input Parameters

string
required
string
string
string
integer
string
PATCH preserves unknown operator values for forward compatibility.
boolean
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SECURITY_SETTINGSUpdate workspace security settings. Emits a security.updated audit event. Requires admin role. session_timeout_hours takes effect on next login; require_2fa stores the policy flag (enforcement is gated on 2FA implementation).

Input Parameters

boolean
array
string ("on" | "off" | "domains")
Whether members may share items with people outside the workspace: on (anyone), off (never), or domains (only addresses at outside_sharing_domains). Inviting someone to join as a member is not outside sharing.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
integer
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
integer
array
Domains outside sharing is allowed with when outside_sharing is domains, e.g. [“acme.com”].
string ("enforced" | "coming_soon")
string ("enforced" | "coming_soon")
Slug: AMBIGUOUS_MCP_UPDATE_SEQUENCEUpdate a sequence (rename, description, toggle active, replace step list). Providing steps replaces the entire step list.

Input Parameters

string
required
string
array
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SETTINGSUpdate workspace settings (name, logo, timezone, etc.). Requires admin role. Pass a flat key-value object.

Input Parameters

string
string
Defaults for new task cycles, e.g. { duration_days, auto_rollover }.
string
Per-priority response and resolution SLA minutes: { urgent: { response, resolution }, … }; null clears.
string
Workspace default email signature (Markdown), used by members without a personal one.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
IANA timezone new members and workspace-wide schedules default to.
string
Up to six emoji strings offered as one-click reactions in chat; null clears.
string
Per-member Drive quota in bytes; takes precedence over default_storage_quota.
string
Boolean; null clears.
string
Non-negative integer days between task cycles by default; null clears.
string
Per-member Drive quota in gigabytes for members with no override.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
string
Positive integer days after which done tasks auto-close; null disables.
string
Positive integer days after which closed tasks auto-archive; null disables.
string
Boolean; null clears.
string
Positive integer days a new task cycle spans by default; null clears.
Slug: AMBIGUOUS_MCP_UPDATE_SHARED_DRIVEUpdate a shared drive (manager-only).

Input Parameters

string
string
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHARED_DRIVE_MEMBERUpdate a member role (manager-only).

Input Parameters

string ("manager" | "content_manager" | "contributor" | "commenter" | "viewer")
required
Membership role on a shared drive.
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHEET_IMAGEUpdate editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

Input Parameters

string
required
string
integer
integer
string
number
number
number
number
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHEET_MERGESReplace the complete merged-cell range collection for a sheet tab using zero-based inclusive startRow, startCol, endRow and endCol coordinates. Read the current sheet and retain unrelated entries when changing one merge. An empty merges array clears all merges on that tab.

Input Parameters

string
required
string
Target tab name. Omit to use the first tab.
array
Complete merge collection for the target tab, replacing all existing entries. Retain unrelated entries when changing one merge; an empty array clears all merges on that tab.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHEET_PICTURE_GROUPUpdate editable picture groups with cell anchors and CSS pixel geometry. Every leaf references an image asset owned by this sheet; native group transforms use EMU coordinates.

Input Parameters

string
required
string
integer
integer
string
number
number
number
number
string
required
number
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHEET_SHAPEUpdate editable floating shapes with editable text, cell anchors and CSS pixel geometry.

Input Parameters

string
required
integer
integer
string
string
string ("rect" | "ellipse")
number
number
string
number
number
number
number
string
required
string ("left" | "center" | "right")
string
string
string
string ("standard" | "excel")
number
number
number
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SHEET_VALIDATION_SETTINGSSet worksheet validation prompt suppression without replacing cells, rules, or presentation. Send disablePrompts=null to restore the absent default setting.

Input Parameters

string
required
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SIGN_DOCUMENTUpdate a draft signing document.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("parallel" | "sequential")
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SLICERPatch a slicer’s config — source range, target column, selected values, overlay position, or title. Only the fields you send are updated; the rest of the slicer config is preserved.

Input Parameters

number
number
string
required
string
string
number
number
string
string
required
boolean
object
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SLIDEUpdate an existing slide in a presentation. Specify the slide by its 0-based index. You can update the slide properties (background, notes) and/or replace its elements. If the user is currently viewing a presentation, use the presentation ID from the page context.

Input Parameters

string
required
string
required
string
object
Alternative envelope — fields merged with top-level keys.
object
array
Full-replace element list for the slide.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_SLIDE_MASTERUpdate a master slide’s name, background, or elements. Slides using the master resolve the updated elements by reference.

Input Parameters

string
required
string
object
array
string
required
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_TASKUpdate a task. Status changes to ‘done’ auto-spawn the next recurrence (when set), trigger CRM activity logging, and emit task.completed events.

Input Parameters

string
required
string
string ("todo" | "in_progress" | "done" | "cancelled" | "blocked")
System task status category. Drives the built-in board columns.
string
string
string
string
string
string ("urgent" | "high" | "medium" | "low")
Task priority. Determines SLA timer and sort weight.
string
string
number
string
string
string
string
array
Users to subscribe to this task so they receive update notifications. Additive — existing subscribers are untouched. Each must be a workspace member; IDs outside the workspace are silently skipped. Use to backfill a bug reporter onto an existing task.
string
string ("manual" | "sla")
Defaults to manual when due_date changes through this update. Set explicitly to sla to mark a system-set due date.
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
Manual override; usually auto-managed by time entries.
object
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_TEAMUpdate a team’s settings (name, slug, description, email, parent, visibility, join policy, posting policy, icon, color). Only team admins or workspace admins can update. If changing parent, validates no cycle in hierarchy. Use this when the user asks to rename a team, move a team under a different parent, or change team settings.

Input Parameters

string
string
string
string
string
required
string ("public" | "private")
string
string ("open" | "request" | "invite")
string
string ("open" | "members_only" | "admins_only")
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
array
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_USERUpdate a member’s role, status, or storage quota. Requires admin or owner; the last owner cannot lose ownership.

Input Parameters

string
required
string ("human" | "agent")
User identity. Humans authenticate with passwords / SSO; agents with API keys.
array
string
string
string
string
Per-user weekly Workload capacity in hours. Null clears the override back to the workspace default.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_WIKI_PAGEUpdate an existing wiki page’s content, title, icon, or parent. Use this when the user asks to edit a wiki page, update documentation, or move a page to a different parent. If the user is currently viewing a wiki page, use the resource ID from page context.

Input Parameters

string
required
string
string
string
string
Page content as Markdown string or ProseMirror JSON object.
string
Target space ID for cross-space move.
number
string
boolean
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
Legacy alias for content.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_WIKI_SYNCED_BLOCKUpdate a synced block’s content. All pages embedding this block will reflect the new content. Use this when the user asks to edit shared content or update a reusable snippet.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_UPDATE_WORKSPACEUpdate workspace name or slug. Requires admin role.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_USE_MAIL_TEMPLATERecord template use.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_USERS_LISTList users in the active workspace. Powers @mention pickers, assignee dropdowns, etc. Filterable by q (matches display_name + username, case-insensitive). Limit defaults to 50, hard cap 100. Member-accessible — use this to resolve a name to a user_id when assigning tasks or @mentioning people; the admin list_users tool is admin-gated and 403s for members/coworkers.

Input Parameters

string
Substring filter against display_name and username (case-insensitive).
string ("human" | "agent")
Restrict to one principal kind. Omitted, both are listed.
string
Max rows to return. Default 50, hard cap 100.
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string ("true" | "false")
Pass ‘true’ to drop suspended memberships. Omitted, they are listed.
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_USE_SIGN_TEMPLATECreate a new draft document from a template, populating fields with placeholder signer roles.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_VERIFY_DOMAINTrigger DNS verification for a workspace domain. Requires admin role.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_VERIFY_DOMAIN_OWNERSHIPVerify custom domain ownership via DNS TXT record. On success, auto-registers with SES to retrieve DKIM/SPF records. Requires admin role.

Input Parameters

string
required
Resource ID.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_CREATERegister a new webhook. Body shape matches CreateWebhookInput (url + events + optional description + optional headers, e.g. an Authorization: Bearer … a receiver requires). Returns the webhook record plus the HMAC signing secret (one-time visibility — store it; subsequent reads omit secret). Custom header values are likewise write-only — reads carry only header_names.

Input Parameters

string
string
array
object
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_DELETEDelete one webhook subscription by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_DELIVERIES_LISTList recent delivery attempts (status, response, retries). Paginated via ?limit= (default 25) and ?offset= (default 0).

Input Parameters

string
required
integer
Page size (default 25, max 500).
string
string
integer
Offset for pagination (must be ≥ 0).
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_EVENT_TYPESList event types an agent can subscribe to. Includes the * wildcard.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_GETGet one webhook subscription’s config by id.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_LISTList webhook registrations owned by the caller.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_TESTSend a test ping payload to the webhook URL.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WEBHOOKS_UPDATEUpdate a webhook (url, events, description, active, headers). Body shape matches UpdateWebhookInput. headers replaces the whole custom-header map; null or {} clears it.

Input Parameters

string
required
string
string
string
array
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_CREATECreate an inline database on a wiki page. Requires editor role on the host page.

Input Parameters

string
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_GETGet an inline database with its full row set.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_ROW_CREATEAppend a row to an inline database. Requires editor role on the host page.

Input Parameters

string
required
string
string
required
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_ROW_DELETEDelete a database row.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_ROW_UPDATEUpdate properties or sort order on a database row.

Input Parameters

string
required
string
required
string
number
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_DATABASE_UPDATEUpdate an inline database’s name, schema, or views. Requires editor role on the host page.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_NATIVE_BACKUPExport a separately labeled, digest-bound native Wiki backup containing the complete workspace Wiki graph. This is not DOCX.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_NATIVE_RESTORERestore a native Wiki backup into its empty source workspace. Preserves spaces, hierarchy, page content, databases, backlinks, synced blocks, permissions, versions, and comments.

Input Parameters

string
required
string
required
number
required
string
required
string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_ASSET_CREATEAdd an image to a wiki page (its body or its cover) as one of its own assets and get back the URL its body should store (/api/assets/{id}/content). Send the bytes as content_base64, source_file_id to copy a Drive file the caller can view, or source_url to import a public HTTPS image through the SSRF guard; neither source is referenced afterwards. The type is decided from the bytes and only images are accepted (415 otherwise); SVG uploads are sanitized before storage and refused with 415 when malformed. Stored SVG is sanitized on every read and served inline as image/svg+xml under a restrictive Content-Security-Policy; malformed stored SVG is refused with 404. Drive SVG downloads remain attachments. The bytes count against the container owner’s storage (413 past it). The same image added to the same container again returns the asset already held. The asset is never visible in Drive and is readable exactly when the container is.

Input Parameters

string
required
string
File name to keep with the image; defaults to image.
string
Declared type. The stored type is decided from the bytes.
string
Fetch a public HTTPS image into this container. Private network addresses and redirects to them are refused; the source URL is not stored in the body.
string
The image bytes, base64-encoded (no data: prefix).
string
Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_CHILDREN_LISTList the immediate child pages of a wiki page. Use this to traverse the page tree one level at a time, or to count children before a destructive delete.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_DATABASE_CREATECreate an inline database on a specific wiki page.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_DUPLICATEDuplicate a wiki page (and optionally its descendants) into a target space + parent. Returns the new top-level page.

Input Parameters

string
required
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
boolean
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_EXPORTExport a wiki page to docx, pdf, html, or md. Streams the file with a Content-Disposition attachment header.

Input Parameters

string
required
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_PERMANENT_DELETEPermanently delete a trashed wiki page. Irreversible.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_PAGE_RESTORERestore a trashed wiki page and its children.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_DELETEDelete a wiki space and all of its pages.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_GETGet a wiki space by slug, with its full page tree. Supports cursor pagination on pages.

Input Parameters

string
required
string
string
string
string
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_MEMBER_ADDAdd a user as a direct member of a wiki space with a given role.

Input Parameters

string
required
string ("viewer" | "commenter" | "editor")
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_MEMBER_REMOVERemove a direct member from a wiki space.

Input Parameters

string
required
string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_MEMBERS_LISTList distinct members of a space — the owner plus everyone with a page-level permission inside it.

Input Parameters

string
required
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_SPACE_UPDATEUpdate a wiki space. Only the space owner may change settings.

Input Parameters

string
required
string
string
string
boolean
string ("restricted" | "workspace" | "link" | "public")
Space/page visibility. restricted = invitees only. workspace = any workspace member. link = anyone with the link. public = indexable.
string
string ("viewer" | "commenter" | "editor")
Role the Everyone-team row grants when visibility is workspace.
string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.
Slug: AMBIGUOUS_MCP_WIKI_TRASH_LISTList trashed (soft-deleted) wiki pages in the workspace.

Input Parameters

string
required
Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.”
string
If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work.