---
canonical_url: "https://docs.composio.dev/toolkits/ambiguous_mcp"
markdown_url: "https://docs.composio.dev/toolkits/ambiguous_mcp.md"
product: "platform"
version: null
last_updated: null
---

# Ambiguous MCP

Operate an Ambiguous workspace through its provider-hosted MCP server, including documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration. Uses the connected account’s workspace-scoped API key. Some tools send external messages, delete data, change access, or consume the workspace action allowance.

- **Category:** model context protocol
- **Auth:** API_KEY
- **Composio-managed OAuth available?** N/A
- **Tools:** 945
- **Triggers:** 0
- **Slug:** `AMBIGUOUS_MCP`
- **Version:** 00000000_00

## Tools

### Ack mentions activity

**Slug:** `AMBIGUOUS_MCP_ACK_MENTIONS_ACTIVITY`

Acknowledge 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

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

### Ack thread activity

**Slug:** `AMBIGUOUS_MCP_ACK_THREAD_ACTIVITY`

Acknowledge readable Threads inbox activity on entry without advancing personal read cursors or clearing explicit manual unread intent.

#### Input Parameters

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

### Add conditional format

**Slug:** `AMBIGUOUS_MCP_ADD_CONDITIONAL_FORMAT`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `ranges` | array | No |  |
| `booleanRule` | object | No |  |
| `dataBarRule` | object | No |  |
| `iconSetRule` | object | No |  |
| `gradientRule` | object | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Add connected element

**Slug:** `AMBIGUOUS_MCP_ADD_CONNECTED_ELEMENT`

Extend 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

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

### Add deal line item

**Slug:** `AMBIGUOUS_MCP_ADD_DEAL_LINE_ITEM`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `quantity` | number | Yes |  |
| `product_id` | string | No |  |
| `sort_order` | integer | No |  |
| `unit_price` | number | Yes |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `billing_interval` | string | No |  |
| `discount_percent` | number | No |  |
| `sync_deal_amount` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Add forwarding address

**Slug:** `AMBIGUOUS_MCP_ADD_FORWARDING_ADDRESS`

Add a forwarding address (sends verification email).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `label` | string | No |  |
| `scope` | string ("all" | "matching") | No | `all` forwards every inbound message; `matching` only those matched by a forwarding rule. |
| `address` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Add pipeline member

**Slug:** `AMBIGUOUS_MCP_ADD_PIPELINE_MEMBER`

Add (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

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

### Add shared drive member

**Slug:** `AMBIGUOUS_MCP_ADD_SHARED_DRIVE_MEMBER`

Add a member (manager-only).

#### Input Parameters

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

### Add sheet column

**Slug:** `AMBIGUOUS_MCP_ADD_SHEET_COLUMN`

Add a column to a sheet tab.

#### Input Parameters

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

### Add sheet rows

**Slug:** `AMBIGUOUS_MCP_ADD_SHEET_ROWS`

Append rows to a sheet tab. Each row is an object keyed by column ID. Example: [{"A": "Widget", "B": 9.99}].

#### Input Parameters

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

### Add sheet tab

**Slug:** `AMBIGUOUS_MCP_ADD_SHEET_TAB`

Add a new tab to a sheet. Auto-generates the name if not provided.

#### Input Parameters

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

### Add slide

**Slug:** `AMBIGUOUS_MCP_ADD_SLIDE`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `notes` | string | No |  |
| `slide` | object | No | Slide body (full or partial — service merges). |
| `layout` | object | No |  |
| `elements` | array | No | Element list. Convenience for callers that don't wrap in `slide`. |
| `background` | string | No | Slide background color, for example "#0F1B33". |
| `after_index` | integer | No | Insert position. Omit to append. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Add task attachment

**Slug:** `AMBIGUOUS_MCP_ADD_TASK_ATTACHMENT`

Attach 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

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

### Add team member

**Slug:** `AMBIGUOUS_MCP_ADD_TEAM_MEMBER`

Add 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

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

### Admin integration delete

**Slug:** `AMBIGUOUS_MCP_ADMIN_INTEGRATION_DELETE`

disconnect an integration

#### Input Parameters

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

### Admin integrations list

**Slug:** `AMBIGUOUS_MCP_ADMIN_INTEGRATIONS_LIST`

list all integrations for workspace

#### Input Parameters

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

### Admin integrations slack channels

**Slug:** `AMBIGUOUS_MCP_ADMIN_INTEGRATIONS_SLACK_CHANNELS`

list Slack channels via bot token

#### Input Parameters

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

### Admin integration update

**Slug:** `AMBIGUOUS_MCP_ADMIN_INTEGRATION_UPDATE`

update integration config

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Resource ID. |
| `config` | object | No |  |
| `status` | string ("active" | "inactive" | "error") | No |  |
| `enabled` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Admin invite delete

**Slug:** `AMBIGUOUS_MCP_ADMIN_INVITE_DELETE`

Revoke (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

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

### Admin invite resend

**Slug:** `AMBIGUOUS_MCP_ADMIN_INVITE_RESEND`

Resend 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

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

### Admin invites list

**Slug:** `AMBIGUOUS_MCP_ADMIN_INVITES_LIST`

List 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

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

### Admin mail suppression create

**Slug:** `AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSION_CREATE`

manually add a suppression

#### Input Parameters

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

### Admin mail suppression delete

**Slug:** `AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSION_DELETE`

remove a suppression

#### Input Parameters

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

### Admin mail suppressions list

**Slug:** `AMBIGUOUS_MCP_ADMIN_MAIL_SUPPRESSIONS_LIST`

list suppressed addresses

#### Input Parameters

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

### Admin notification defaults get

**Slug:** `AMBIGUOUS_MCP_ADMIN_NOTIFICATION_DEFAULTS_GET`

Read workspace-default email notification prefs. Returns sensible defaults (all enabled) when never configured.

#### Input Parameters

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

### Admin notification defaults update

**Slug:** `AMBIGUOUS_MCP_ADMIN_NOTIFICATION_DEFAULTS_UPDATE`

Partially update workspace-default email notification prefs. Emits settings.updated audit event.

#### Input Parameters

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

### Admin usage export

**Slug:** `AMBIGUOUS_MCP_ADMIN_USAGE_EXPORT`

Export usage stats as CSV

#### Input Parameters

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

### Admin usage timeseries

**Slug:** `AMBIGUOUS_MCP_ADMIN_USAGE_TIMESERIES`

Daily 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

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

### Admin user get

**Slug:** `AMBIGUOUS_MCP_ADMIN_USER_GET`

Get one workspace user's full admin record by id.

#### Input Parameters

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

### Admin user reset password

**Slug:** `AMBIGUOUS_MCP_ADMIN_USER_RESET_PASSWORD`

Create and email a one-hour password-reset link. On delivery failure, returns `sent: false` with `reset_url`.

#### Input Parameters

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

### Admin user suspend

**Slug:** `AMBIGUOUS_MCP_ADMIN_USER_SUSPEND`

Suspend a user account. Suspended accounts return 403 on all API calls.

#### Input Parameters

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

### Admin user unsuspend

**Slug:** `AMBIGUOUS_MCP_ADMIN_USER_UNSUSPEND`

Unsuspend a user account. Restores access to all API calls.

#### Input Parameters

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

### Admin workspace logo delete

**Slug:** `AMBIGUOUS_MCP_ADMIN_WORKSPACE_LOGO_DELETE`

Remove workspace logo (admin only)

#### Input Parameters

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

### Analytics annotations list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_ANNOTATIONS_LIST`

List 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

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

### Analytics catalog overrides list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_CATALOG_OVERRIDES_LIST`

List catalog metadata overrides for the workspace.

#### Input Parameters

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

### Analytics catalog stats

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_CATALOG_STATS`

Per-event last_seen_at and 30-day volume for the workspace's tracked events.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `management` | string ("true" | "false") | No | Use the workspace-wide management catalog (workspace admin only), instead of a project view. |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics cohorts get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_COHORTS_GET`

Read 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

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

### Analytics cohorts list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_COHORTS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project to list. Omitted, the workspace's default project is used while clients migrate. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics dashboards get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_DASHBOARDS_GET`

Read 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

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

### Analytics dashboards list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_DASHBOARDS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project to list. Omitted, the workspace's default project is used while clients migrate. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics events get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_EVENTS_GET`

Read one Analytics evidence event owned by the caller's source workspace. Foreign and missing IDs return 404.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics events list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_EVENTS_LIST`

List source-owned Analytics evidence with bounded filters and stable pagination. Measured group IDs never grant access.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `type` | string ("track" | "identify" | "page" | "group" | "alias") | No |  |
| `event` | string | No |  |
| `limit` | integer | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `date_to` | string | No | 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. |
| `cursor_id` | integer | No |  |
| `date_from` | string | No | 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. |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `anonymous_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `cursor_timestamp` | string | No |  |
| `analytics_user_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics funnels get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_FUNNELS_GET`

Read 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

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

### Analytics funnels list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_FUNNELS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project to list. Omitted, the workspace's default project is used while clients migrate. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics insights get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_INSIGHTS_GET`

Read 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

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

### Analytics insights list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_INSIGHTS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project to list. Omitted, the workspace's default project is used while clients migrate. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics metric definitions list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_METRIC_DEFINITIONS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `management` | string ("true" | "false") | No | Use the workspace-wide management catalog (workspace admin only), instead of a project view. |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics metrics upsert

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_METRICS_UPSERT`

Upsert 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

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

### Analytics metric value

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_METRIC_VALUE`

Read 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

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

### Analytics mv metadata

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_MV_METADATA`

Get materialized view name and last refresh time.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics projects access request create

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_CREATE`

Ask 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

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

### Analytics projects access request current

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_CURRENT`

Return whether the caller has an open access request for the project.

#### Input Parameters

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

### Analytics projects access request decide

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_ACCESS_REQUEST_DECIDE`

Approve at viewer or editor, or decline, an open access request. Project owners only. Returns 409 once decided.

#### Input Parameters

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

### Analytics projects get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_GET`

Read one Analytics project, its view and the caller's role. `404` when the caller holds no role on it.

#### Input Parameters

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

### Analytics projects list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_LIST`

List 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

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

### Analytics projects permissions list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_PROJECTS_PERMISSIONS_LIST`

List the project's members: users and teams with their roles. The Everyone team row is the workspace tier.

#### Input Parameters

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

### Analytics query execute

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_QUERY_EXECUTE`

Execute 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `type` | string | Yes |  |
| `event` | string | No | type insights only. |
| `limit` | integer | No | type events, drilldown only. |
| `match` | string ("all" | "any") | No | type cohort only. |
| `slice` | string | No | type drilldown only. |
| `steps` | array | No | type funnel only. |
| `cursor` | object | No | type events only. |
| `dateTo` | string | No | 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. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `source` | string ("event" | "metric") | No | type insights only. |
| `filters` | string | No | type events, insights only. |
| `horizon` | integer | No | type retention only. |
| `userIds` | array | No | type insights, funnel, retention only. |
| `criteria` | array | No | type cohort only. |
| `dateFrom` | string | No | 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. |
| `interval` | string | No | type insights, funnel, retention only. |
| `breakdown` | string | No | type insights, funnel only. |
| `project_id` | string | No | The Analytics project the read runs in. Omitted, the workspace's default project is used. |
| `ratioEvent` | string | No | type insights only. |
| `aggregation` | string ("count" | "sum" | "unique" | "ratio") | No | type insights only. |
| `ratioSource` | string ("event" | "metric") | No | type insights only. |
| `returnEvent` | string | No | type retention only. |
| `triggerEvent` | string | No | type retention only. |
| `breakdownBins` | array | No | type insights only. |
| `identityChain` | boolean | No | type funnel only. |
| `returnFilters` | array | No | type retention only. |
| `triggerFilters` | array | No | type retention only. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `conversionWindow` | object | No | type funnel only. |
| `aggregationProperty` | string | No | type insights only. |
| `breakdownAttribution` | string | No | 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. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics restricted marks list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_RESTRICTED_MARKS_LIST`

List the workspace's restricted event names, trait keys and metric keys. Workspace admin only.

#### Input Parameters

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

### Analytics retentions get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_RETENTIONS_GET`

Read 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

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

### Analytics retentions list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_RETENTIONS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No | The Analytics project to list. Omitted, the workspace's default project is used while clients migrate. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Analytics settings get

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_SETTINGS_GET`

Get the workspace's analytics settings — the timezone calendar windows such as today-7d and day/week/month buckets resolve in.

#### Input Parameters

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

### Analytics users aggregates

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_USERS_AGGREGATES`

List analytics user profiles from the materialized view (faster at high volume, nightly refresh). Falls back to direct read when MV is unavailable.

#### Input Parameters

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

### Analytics users list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_USERS_LIST`

List analytics user profiles (paginated, searchable). Returns traits, first_seen, last_identified.

#### Input Parameters

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

### Analytics user timeline

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_USER_TIMELINE`

Get 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

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

### Analytics write key list

**Slug:** `AMBIGUOUS_MCP_ANALYTICS_WRITE_KEY_LIST`

List all writeKeys for the workspace (plaintext never returned on list).

#### Input Parameters

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

### Append sheet values

**Slug:** `AMBIGUOUS_MCP_APPEND_SHEET_VALUES`

Append 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `range` | string | No | A1-style range — `Sheet1!A1:D10` or `A1:D10`. |
| `values` | array | No | 2-D array of row × column values. Capped at 1000 rows per call. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Apply deal template

**Slug:** `AMBIGUOUS_MCP_APPLY_DEAL_TEMPLATE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | No |  |
| `stage_id` | string | No |  |
| `close_date` | string | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `amount_override` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `include_line_items` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Apply master to slide

**Slug:** `AMBIGUOUS_MCP_APPLY_MASTER_TO_SLIDE`

Link 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

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

### Apply task template

**Slug:** `AMBIGUOUS_MCP_APPLY_TASK_TEMPLATE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | Yes |  |
| `status` | string ("todo" | "in_progress" | "done" | "cancelled" | "blocked") | No | System task status category. Drives the built-in board columns. |
| `due_date` | string | No |  |
| `estimate` | integer | No |  |
| `priority` | string ("urgent" | "high" | "medium" | "low") | No | Task priority. Determines SLA timer and sort weight. |
| `project_id` | string | No |  |
| `assignee_id` | string | No |  |
| `description` | string | No |  |
| `template_id` | string | Yes |  |
| `parent_task_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_field_values` | object | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Apply transition to all

**Slug:** `AMBIGUOUS_MCP_APPLY_TRANSITION_TO_ALL`

Apply 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

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

### Archive mail thread

**Slug:** `AMBIGUOUS_MCP_ARCHIVE_MAIL_THREAD`

Archive every inbox-folder message in a thread

#### Input Parameters

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

### Asset get content

**Slug:** `AMBIGUOUS_MCP_ASSET_GET_CONTENT`

An 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

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

### Assign role

**Slug:** `AMBIGUOUS_MCP_ASSIGN_ROLE`

Assign a role to a user. Requires admin role.

#### Input Parameters

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

### Auth whoami

**Slug:** `AMBIGUOUS_MCP_AUTH_WHOAMI`

Return 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

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

### Automations enqueue

**Slug:** `AMBIGUOUS_MCP_AUTOMATIONS_ENQUEUE`

Queue 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `payload` | object | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Batch archive emails

**Slug:** `AMBIGUOUS_MCP_BATCH_ARCHIVE_EMAILS`

Archive 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

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

### Batch clear sheet values

**Slug:** `AMBIGUOUS_MCP_BATCH_CLEAR_SHEET_VALUES`

Clear 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

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

### Batch file permissions

**Slug:** `AMBIGUOUS_MCP_BATCH_FILE_PERMISSIONS`

Batch-fetch permissions for up to 50 files by ID. Returns a map of file_id → permissions array.

#### Input Parameters

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

### Batch get contacts

**Slug:** `AMBIGUOUS_MCP_BATCH_GET_CONTACTS`

Fetch multiple CRM contacts by their IDs in a single request (max 100). Missing or inaccessible IDs are silently omitted from the result.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ids` | string | No | Comma-separated list of contact UUIDs (max 100). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Batch get deals

**Slug:** `AMBIGUOUS_MCP_BATCH_GET_DEALS`

Fetch multiple CRM deals by their IDs in a single request (max 100). Missing or inaccessible IDs are silently omitted from the result.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ids` | string | No | Comma-separated list of deal UUIDs (max 100). |
| `embed` | string | No | Comma-separated embed fields. Supported: line_items. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Batch get files

**Slug:** `AMBIGUOUS_MCP_BATCH_GET_FILES`

Batch-fetch up to 50 files by ID. Powers drive:// embed hydration in Chat/Docs/Wiki/CRM.

#### Input Parameters

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

### Batch get sheet values

**Slug:** `AMBIGUOUS_MCP_BATCH_GET_SHEET_VALUES`

Fetch multiple disjoint ranges from a spreadsheet in a single request. Avoids N sequential round-trips when reading KPIs from different regions.

#### Input Parameters

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

### Batch modify emails

**Slug:** `AMBIGUOUS_MCP_BATCH_MODIFY_EMAILS`

Batch 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ids` | array | No | Explicit email IDs. Omit when using `search_query`. |
| `read` | boolean | No | Alias for `mark_read`. |
| `star` | boolean | No |  |
| `trash` | boolean | No | 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. |
| `fields` | string | No |  |
| `folder` | string | No | Explicit folder destination. It must agree with archive/trash flags; conflicting directives are rejected before any update. |
| `notify` | string | No |  |
| `archive` | boolean | No | true archives; false returns archived messages to inbox when no other destination is supplied. Folder directives must agree; contradictions return 400 without writes. |
| `mark_read` | boolean | No |  |
| `add_labels` | array | No | Label IDs or label names. |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `search_query` | string | No | Gmail-style search query — applies the action to every matching email (capped at 500), not just a visible page. |
| `remove_labels` | array | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Batch trash emails

**Slug:** `AMBIGUOUS_MCP_BATCH_TRASH_EMAILS`

Trash 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

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

### Block sender

**Slug:** `AMBIGUOUS_MCP_BLOCK_SENDER`

Block a sender (address or domain).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `kind` | string ("address" | "domain") | No | `address` matches a single email; `domain` matches any sender at that domain. |
| `reason` | string | No |  |
| `pattern` | string | Yes |  |
| `trash_existing` | boolean | No | Default true; retroactively trashes matching inbox/archive mail. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Book event resources

**Slug:** `AMBIGUOUS_MCP_BOOK_EVENT_RESOURCES`

Book one or more resources (rooms, equipment) for an existing event. Returns a conflict error if a resource is already booked.

#### Input Parameters

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

### Browse public channels

**Slug:** `AMBIGUOUS_MCP_BROWSE_PUBLIC_CHANNELS`

Browse 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

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

### Bulk archive tasks

**Slug:** `AMBIGUOUS_MCP_BULK_ARCHIVE_TASKS`

Archive up to 100 tasks at once. Only archives tasks the caller created or is assigned to.

#### Input Parameters

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

### Bulk copy files

**Slug:** `AMBIGUOUS_MCP_BULK_COPY_FILES`

Copy 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

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

### Bulk delete contacts

**Slug:** `AMBIGUOUS_MCP_BULK_DELETE_CONTACTS`

Delete many CRM contacts in a single operation. Returns counts of deleted/skipped/failed items.

#### Input Parameters

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

### Bulk delete deals

**Slug:** `AMBIGUOUS_MCP_BULK_DELETE_DEALS`

Delete many CRM deals at once by their ids.

#### Input Parameters

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

### Bulk delete messages

**Slug:** `AMBIGUOUS_MCP_BULK_DELETE_MESSAGES`

Soft-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

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

### Bulk delete tasks

**Slug:** `AMBIGUOUS_MCP_BULK_DELETE_TASKS`

Soft-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

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

### Bulk export contacts

**Slug:** `AMBIGUOUS_MCP_BULK_EXPORT_CONTACTS`

Export selected contacts as CSV or vCard. CSV includes core fields and custom properties; vCard preserves imported RFC 6350 properties and parameters.

#### Input Parameters

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

### Bulk export deals

**Slug:** `AMBIGUOUS_MCP_BULK_EXPORT_DEALS`

Export selected deals as CSV

#### Input Parameters

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

### Bulk move files

**Slug:** `AMBIGUOUS_MCP_BULK_MOVE_FILES`

Move 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

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

### Bulk update contacts

**Slug:** `AMBIGUOUS_MCP_BULK_UPDATE_CONTACTS`

Update 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

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

### Bulk update deals

**Slug:** `AMBIGUOUS_MCP_BULK_UPDATE_DEALS`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ids` | array | Yes |  |
| `status` | string ("open" | "won" | "lost") | No | Lifecycle of a deal. `won` and `lost` close the deal; `lost` requires a `lost_reason`. |
| `owner_id` | string | No |  |
| `stage_id` | string | No |  |
| `lost_reason` | string | No |  |
| `pipeline_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Bulk update tasks

**Slug:** `AMBIGUOUS_MCP_BULK_UPDATE_TASKS`

Update 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

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

### Calendar conflicts

**Slug:** `AMBIGUOUS_MCP_CALENDAR_CONFLICTS`

Detect attendee scheduling conflicts.

#### Input Parameters

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

### Calendar event export ics

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_EXPORT_ICS`

Export single event as .ics.

#### Input Parameters

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

### Calendar event meeting notes create

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_MEETING_NOTES_CREATE`

Create a meeting-notes doc for an event, or — when `document_id` is given — link that existing doc and grant attendees access.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | No |  |
| `template` | string | No |  |
| `document_id` | string | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Calendar event meeting notes unlink

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_MEETING_NOTES_UNLINK`

Unlink meeting-notes doc.

#### Input Parameters

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

### Calendar event reminders create

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_CREATE`

Add a reminder to a calendar event.

#### Input Parameters

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

### Calendar event reminders list

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_LIST`

List event reminders.

#### Input Parameters

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

### Calendar event reminders set

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_REMINDERS_SET`

Replace reminder list.

#### Input Parameters

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

### Calendar event unbook resources

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EVENT_UNBOOK_RESOURCES`

Release every resource booked for a calendar event.

#### Input Parameters

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

### Calendar export ics

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXPORT_ICS`

Export entire calendar as .ics.

#### Input Parameters

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

### Calendar external auth url

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_AUTH_URL`

Start external provider OAuth.

#### Input Parameters

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

### Calendar external calendars enable sync

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CALENDARS_ENABLE_SYNC`

Enable two-way sync.

#### Input Parameters

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

### Calendar external calendars list

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CALENDARS_LIST`

List calendars on connection.

#### Input Parameters

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

### Calendar external connection delete

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CONNECTION_DELETE`

Disconnect external account.

#### Input Parameters

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

### Calendar external connections list

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_CONNECTIONS_LIST`

List connected external accounts.

#### Input Parameters

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

### Calendar external force sync

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_FORCE_SYNC`

Schedule 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

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

### Calendar external synced disable

**Slug:** `AMBIGUOUS_MCP_CALENDAR_EXTERNAL_SYNCED_DISABLE`

Disable sync for one calendar.

#### Input Parameters

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

### Calendar import ics url

**Slug:** `AMBIGUOUS_MCP_CALENDAR_IMPORT_ICS_URL`

Import an .ics feed by URL. Fetches the URL server-side and imports its events into the calendar.

#### Input Parameters

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

### Calendar reminder delete

**Slug:** `AMBIGUOUS_MCP_CALENDAR_REMINDER_DELETE`

Delete one calendar event reminder by id.

#### Input Parameters

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

### Calendar resource delete

**Slug:** `AMBIGUOUS_MCP_CALENDAR_RESOURCE_DELETE`

Delete a bookable calendar resource by id.

#### Input Parameters

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

### Calendar resource get

**Slug:** `AMBIGUOUS_MCP_CALENDAR_RESOURCE_GET`

Get one bookable calendar resource by id.

#### Input Parameters

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

### Calendar resources create

**Slug:** `AMBIGUOUS_MCP_CALENDAR_RESOURCES_CREATE`

Create a bookable resource.

#### Input Parameters

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

### Calendar resource update

**Slug:** `AMBIGUOUS_MCP_CALENDAR_RESOURCE_UPDATE`

Update a bookable calendar resource's details.

#### Input Parameters

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

### Calendars create

**Slug:** `AMBIGUOUS_MCP_CALENDARS_CREATE`

Create a calendar in the current workspace.

#### Input Parameters

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

### Calendars delete

**Slug:** `AMBIGUOUS_MCP_CALENDARS_DELETE`

Delete a calendar and every event on it.

#### Input Parameters

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

### Calendars permissions get

**Slug:** `AMBIGUOUS_MCP_CALENDARS_PERMISSIONS_GET`

Get 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

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

### Calendars update

**Slug:** `AMBIGUOUS_MCP_CALENDARS_UPDATE`

Update calendar fields.

#### Input Parameters

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

### Calendar upcoming reminders

**Slug:** `AMBIGUOUS_MCP_CALENDAR_UPCOMING_REMINDERS`

Reminders 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

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

### Cancel scheduled email

**Slug:** `AMBIGUOUS_MCP_CANCEL_SCHEDULED_EMAIL`

Cancel a scheduled email

#### Input Parameters

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

### Cancel scheduled message

**Slug:** `AMBIGUOUS_MCP_CANCEL_SCHEDULED_MESSAGE`

Cancel 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

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

### Cancel scheduler booking

**Slug:** `AMBIGUOUS_MCP_CANCEL_SCHEDULER_BOOKING`

Cancel a booking as its host. The booked event is cancelled and the booker is always emailed the cancellation, with the optional message.

#### Input Parameters

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

### Change coworker manager

**Slug:** `AMBIGUOUS_MCP_CHANGE_COWORKER_MANAGER`

Reassign 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

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

### Chat channel create

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_CREATE`

Create a chat channel in the workspace.

#### Input Parameters

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

### Chat channel delete

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_DELETE`

Delete a chat channel and its messages.

#### Input Parameters

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

### Chat channel get

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_GET`

Get a specific channel by UUID, with members.

#### Input Parameters

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

### Chat channel group remove

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_GROUP_REMOVE`

Remove a group from channel (clean up fan-out rows)

#### Input Parameters

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

### Chat channel join

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_JOIN`

Self-join a public channel (no body required)

#### Input Parameters

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

### Chat channel last messages

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_LAST_MESSAGES`

Batch-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

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

### Chat channel leave

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_LEAVE`

Leave a chat channel you belong to.

#### Input Parameters

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

### Chat channel member remove

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_MEMBER_REMOVE`

Remove a member from a chat channel.

#### Input Parameters

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

### Chat channel members add

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_MEMBERS_ADD`

Add member(s) or a group

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `team_id` | string | No |  |
| `user_id` | string | No | Singular convenience alias — add one member (handler folds it into `user_ids`). |
| `user_ids` | array | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Chat channel notification preference

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_NOTIFICATION_PREFERENCE`

Choose 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

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

### Chat channel notification prefs

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_NOTIFICATION_PREFS`

Update the caller's per-channel notification preferences (unread_display: count | dot | since_visit).

#### Input Parameters

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

### Chat channel update

**Slug:** `AMBIGUOUS_MCP_CHAT_CHANNEL_UPDATE`

Update a chat channel's name, topic or settings.

#### Input Parameters

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

### Chat draft create saved

**Slug:** `AMBIGUOUS_MCP_CHAT_DRAFT_CREATE_SAVED`

Create a saved (named) draft for the caller.

#### Input Parameters

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

### Chat draft delete

**Slug:** `AMBIGUOUS_MCP_CHAT_DRAFT_DELETE`

Delete a draft owned by the caller.

#### Input Parameters

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

### Chat drafts list

**Slug:** `AMBIGUOUS_MCP_CHAT_DRAFTS_LIST`

The caller's chat drafts (inflight + saved), newest first.

#### Input Parameters

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

### Chat draft update

**Slug:** `AMBIGUOUS_MCP_CHAT_DRAFT_UPDATE`

Update a saved draft owned by the caller.

#### Input Parameters

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

### Chat emoji image

**Slug:** `AMBIGUOUS_MCP_CHAT_EMOJI_IMAGE`

Serve custom emoji image from GCS

#### Input Parameters

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

### Chat mentions inbox

**Slug:** `AMBIGUOUS_MCP_CHAT_MENTIONS_INBOX`

Messages from other users that @-mention the caller. Powers the Mentions tab.

#### Input Parameters

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

### Chat message delete

**Slug:** `AMBIGUOUS_MCP_CHAT_MESSAGE_DELETE`

Delete one message from a chat channel.

#### Input Parameters

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

### Chat message update

**Slug:** `AMBIGUOUS_MCP_CHAT_MESSAGE_UPDATE`

Edit message or pin/unpin

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `pinned` | boolean | No |  |
| `content` | string | No |  |
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `starts_new_block` | boolean | No | Author correction of the block override after sending. |
| `broadcast_to_channel` | boolean | No | Author toggle of the thread-reply channel reshare after sending; true→false un-shares, false→true reshares late. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Chat preferences

**Slug:** `AMBIGUOUS_MCP_CHAT_PREFERENCES`

Workspace-level chat preferences readable by any authenticated member (default_reactions).

#### Input Parameters

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

### Chat reactions inbox

**Slug:** `AMBIGUOUS_MCP_CHAT_REACTIONS_INBOX`

Messages authored by the caller that carry reactions from other users. Powers the Mentions & Reactions inbox.

#### Input Parameters

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

### Chat saved ids list

**Slug:** `AMBIGUOUS_MCP_CHAT_SAVED_IDS_LIST`

Get saved message IDs for a channel (for UI bookmarked state)

#### Input Parameters

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

### Chat sidebar create section

**Slug:** `AMBIGUOUS_MCP_CHAT_SIDEBAR_CREATE_SECTION`

Create a custom chat-sidebar section for the caller.

#### Input Parameters

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

### Chat sidebar delete section

**Slug:** `AMBIGUOUS_MCP_CHAT_SIDEBAR_DELETE_SECTION`

Delete a chat-sidebar section owned by the caller.

#### Input Parameters

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

### Chat sidebar list sections

**Slug:** `AMBIGUOUS_MCP_CHAT_SIDEBAR_LIST_SECTIONS`

The caller's custom chat-sidebar sections, ordered by position.

#### Input Parameters

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

### Chat sidebar reorder sections

**Slug:** `AMBIGUOUS_MCP_CHAT_SIDEBAR_REORDER_SECTIONS`

Reorder the caller's chat-sidebar sections.

#### Input Parameters

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

### Chat sidebar update section

**Slug:** `AMBIGUOUS_MCP_CHAT_SIDEBAR_UPDATE_SECTION`

Rename a chat-sidebar section or set its channels.

#### Input Parameters

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

### Chat thread activity list

**Slug:** `AMBIGUOUS_MCP_CHAT_THREAD_ACTIVITY_LIST`

List 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

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

### Chat thread get

**Slug:** `AMBIGUOUS_MCP_CHAT_THREAD_GET`

Get the replies in a chat message's thread.

#### Input Parameters

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

### Check availability

**Slug:** `AMBIGUOUS_MCP_CHECK_AVAILABILITY`

Check 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

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

### Check resource availability

**Slug:** `AMBIGUOUS_MCP_CHECK_RESOURCE_AVAILABILITY`

Check if a specific resource (room, equipment) is free in a time range. Call before booking to avoid conflicts.

#### Input Parameters

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

### Check workspace slug

**Slug:** `AMBIGUOUS_MCP_CHECK_WORKSPACE_SLUG`

Check whether a workspace slug is available.

#### Input Parameters

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

### Claim document

**Slug:** `AMBIGUOUS_MCP_CLAIM_DOCUMENT`

Make 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `claim_key` | string | Yes | The claim key returned when the document was created without an account. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Clear calendar

**Slug:** `AMBIGUOUS_MCP_CLEAR_CALENDAR`

Delete 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

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

### Clear reminder

**Slug:** `AMBIGUOUS_MCP_CLEAR_REMINDER`

Clear a pending reminder on a saved message. The message stays saved; only the reminder is removed.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Clear sheet validation

**Slug:** `AMBIGUOUS_MCP_CLEAR_SHEET_VALIDATION`

Remove 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

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

### Clear user status

**Slug:** `AMBIGUOUS_MCP_CLEAR_USER_STATUS`

Clear 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

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

### Code comment update

**Slug:** `AMBIGUOUS_MCP_CODE_COMMENT_UPDATE`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `body` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `deleted` | boolean | No |  |
| `reaction` | object | No |  |
| `commentId` | string | Yes |  |
| `expectedBody` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code connections list

**Slug:** `AMBIGUOUS_MCP_CODE_CONNECTIONS_LIST`

List repositories offered by the workspace GitHub installation. Workspace administrators only.

#### Input Parameters

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

### Code pull auto merge

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_AUTO_MERGE`

Enable 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `method` | string ("squash" | "merge" | "rebase") | No |  |
| `notify` | string | No |  |
| `enabled` | boolean | Yes |  |
| `version` | integer | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code pull changes since review

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_CHANGES_SINCE_REVIEW`

Compare the caller's last reviewed head with the current head. Historical or truncated source is explicitly reported.

#### Input Parameters

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

### Code pull comment

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_COMMENT`

Start 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `body` | string | Yes |  |
| `anchor` | object | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `pending` | boolean | No |  |
| `reviewId` | string | No |  |
| `threadId` | string | No |  |
| `idempotencyKey` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code pull commit

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_COMMIT`

Read the diff for one commit in this pull request.

#### Input Parameters

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

### Code pull create

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_CREATE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `base` | string | No |  |
| `body` | string | No |  |
| `head` | string | No |  |
| `draft` | boolean | No |  |
| `title` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `number` | integer | No |  |
| `autoMerge` | object | No |  |
| `repositoryId` | string | Yes |  |
| `idempotencyKey` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code pull export

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_EXPORT`

Export the complete review record with original anchors and attribution as versioned JSON or Markdown.

#### Input Parameters

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

### Code pull get

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_GET`

Read 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

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

### Code pull merge

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_MERGE`

Merge 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `method` | string ("squash" | "merge" | "rebase") | No |  |
| `notify` | string | No |  |
| `baseSha` | string | Yes |  |
| `headSha` | string | Yes |  |
| `version` | integer | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code pull refresh

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_REFRESH`

Reconcile 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

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

### Code pull review

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_REVIEW`

Submit 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

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

### Code pulls list

**Slug:** `AMBIGUOUS_MCP_CODE_PULLS_LIST`

Permission-filtered pull request inbox.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `view` | string ("all" | "needs_review" | "mine" | "following" | "assigned" | "involves") | No |  |
| `state` | string ("open" | "closed" | "merged" | "all") | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `repositoryId` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Code pull update

**Slug:** `AMBIGUOUS_MCP_CODE_PULL_UPDATE`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `base` | string | No |  |
| `body` | string | No |  |
| `draft` | boolean | No |  |
| `state` | string ("open" | "closed") | No |  |
| `title` | string | No |  |
| `fields` | string | No |  |
| `labels` | array | No |  |
| `locked` | boolean | No |  |
| `notify` | string | No |  |
| `version` | integer | Yes |  |
| `following` | boolean | No |  |
| `milestone` | string | No |  |
| `viewedFile` | object | No |  |
| `assigneeIds` | array | No |  |
| `reviewerIds` | array | No |  |
| `reviewPolicy` | string ("approved" | "approved_or_resolved") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reviewerRerequest` | object | No |  |
| `reviewerRequirement` | object | No |  |
| `discardPendingReview` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `acceptProviderMetadata` | boolean | No |  |

### Code repositories list

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORIES_LIST`

List repositories the caller can read, with their Code role.

#### Input Parameters

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

### Code repository compare

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_COMPARE`

Compare two repository refs before opening a pull request.

#### Input Parameters

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

### Code repository connect

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_CONNECT`

Connect a repository from this workspace's existing GitHub installation. Workspace admin only; grants the connector repository ownership.

#### Input Parameters

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

### Code repository grant

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_GRANT`

Grant or revoke a workspace user or team. Null role revokes. Repository owner only.

#### Input Parameters

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

### Code repository grants

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_GRANTS`

Read repository access grants. Repository owner only.

#### Input Parameters

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

### Code repository metadata

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_METADATA`

Read the repository labels and milestones available for pull requests.

#### Input Parameters

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

### Code repository principals

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_PRINCIPALS`

List workspace users and teams available for an explicit repository grant. Repository owner only.

#### Input Parameters

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

### Code repository reviewers

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_REVIEWERS`

List currently eligible Ambiguous reviewers, including agents.

#### Input Parameters

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

### Code repository update

**Slug:** `AMBIGUOUS_MCP_CODE_REPOSITORY_UPDATE`

Update the default target branch, review policy or connection. A null target resets to GitHub's default branch. Repository owner only.

#### Input Parameters

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

### Code review dismiss

**Slug:** `AMBIGUOUS_MCP_CODE_REVIEW_DISMISS`

Dismiss 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

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

### Code review resolve

**Slug:** `AMBIGUOUS_MCP_CODE_REVIEW_RESOLVE`

Resolve 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

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

### Compute pivot table

**Slug:** `AMBIGUOUS_MCP_COMPUTE_PIVOT_TABLE`

Compute 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

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

### Compute wiki rollups

**Slug:** `AMBIGUOUS_MCP_COMPUTE_WIKI_ROLLUPS`

Compute and return rollup values for all rows in the database. Each rollup aggregates a property across related rows.

#### Input Parameters

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

### Copy sheet to

**Slug:** `AMBIGUOUS_MCP_COPY_SHEET_TO`

Copy 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

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

### Coworkers conversation get

**Slug:** `AMBIGUOUS_MCP_COWORKERS_CONVERSATION_GET`

Proxy (workspace-isolated): get a single conversation thread.

#### Input Parameters

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

### Coworkers conversations list

**Slug:** `AMBIGUOUS_MCP_COWORKERS_CONVERSATIONS_LIST`

Proxy (workspace-isolated): list conversations for the coworker in the active workspace.

#### Input Parameters

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

### Coworkers execution cancel

**Slug:** `AMBIGUOUS_MCP_COWORKERS_EXECUTION_CANCEL`

Kill 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

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

### Coworkers execution get

**Slug:** `AMBIGUOUS_MCP_COWORKERS_EXECUTION_GET`

Get 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

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

### Coworkers executions list

**Slug:** `AMBIGUOUS_MCP_COWORKERS_EXECUTIONS_LIST`

Proxy: list coworker execution history (paginated).

#### Input Parameters

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

### Coworkers monitored channels add

**Slug:** `AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_ADD`

Proxy (workspace-isolated): start monitoring a channel.

#### Input Parameters

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

### Coworkers monitored channels list

**Slug:** `AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_LIST`

Proxy (workspace-isolated): list channels the coworker is monitoring.

#### Input Parameters

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

### Coworkers monitored channels remove

**Slug:** `AMBIGUOUS_MCP_COWORKERS_MONITORED_CHANNELS_REMOVE`

Proxy (workspace-isolated): stop monitoring a channel.

#### Input Parameters

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

### Coworkers playbooks archive

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_ARCHIVE`

Archive a playbook. Archived playbooks are hidden from lists and cannot be selected during dispatch, but remain linked to historical executions for audit.

#### Input Parameters

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

### Coworkers playbooks create

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_CREATE`

Create a playbook and its initial version. `instructions` and `subtasks` seed version 1, which becomes the current version.

#### Input Parameters

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

### Coworkers playbooks delete

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_DELETE`

Delete 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

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

### Coworkers playbooks get

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_GET`

Get one playbook with its current version's instructions and subtasks.

#### Input Parameters

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

### Coworkers playbooks list

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_LIST`

List the coworker's playbooks (metadata + current version pointer).

#### Input Parameters

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

### Coworkers playbooks update

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOKS_UPDATE`

Edit playbook metadata in place (title, objective). Instructions and subtasks are immutable — create a new version instead.

#### Input Parameters

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

### Coworkers playbook versions create

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_CREATE`

Append a new version. Auto-increments the version number and marks the new version current. Prior versions stay readable for audit.

#### Input Parameters

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

### Coworkers playbook versions get

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_GET`

Get one historical version's instructions and subtasks.

#### Input Parameters

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

### Coworkers playbook versions list

**Slug:** `AMBIGUOUS_MCP_COWORKERS_PLAYBOOK_VERSIONS_LIST`

List all versions of a playbook, newest first.

#### Input Parameters

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

### Coworkers rotate token

**Slug:** `AMBIGUOUS_MCP_COWORKERS_ROTATE_TOKEN`

Rotate the management token used to talk to the coworker service.

#### Input Parameters

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

### Create canvas

**Slug:** `AMBIGUOUS_MCP_CREATE_CANVAS`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No | Board title. Defaults to 'Untitled'. |
| `visibility` | string ("restricted" | "workspace" | "link" | "public") | No | Initial visibility. Defaults to 'restricted'. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create canvas element

**Slug:** `AMBIGUOUS_MCP_CREATE_CANVAS_ELEMENT`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `h` | number | Yes | Height in board units. |
| `w` | number | Yes | Width in board units. |
| `x` | number | Yes | Board x (top-left). +x right. |
| `y` | number | Yes | Board y (top-left). +y down. |
| `z` | number | No | Paint order (Arrange front/back): higher paints on top, undefined = 0. |
| `id` | string | Yes | Canvas board id. |
| `to` | object | No | type connector only. |
| `src` | string | No | The image's container asset URL (/api/assets/<asset-id>/content); older boards may carry a Drive reference (drive://<file-id>). type image only. |
| `code` | string | No | Plain source text on the wire. type codeBlock only. |
| `from` | object | No | type connector only. |
| `link` | string | No | Navigational target (Link to…): same-board element ref or a URL. |
| `name` | string | No | type frame only. |
| `step` | integer | No | type metric only. |
| `type` | string | Yes |  |
| `label` | object | No | type connector only. |
| `lanes` | array | No | type swimlane only. |
| `route` | string ("straight" | "elbow" | "curved") | No | type connector only. |
| `shape` | string ("rect" | "roundedRect" | "ellipse" | "diamond" | "parallelogram" | "cylinder") | No | type shape only. |
| `style` | object | No |  |
| `title` | string | No | type metric only. |
| `locked` | boolean | No | A locked element rejects geometry/content mutation until unlocked. |
| `report` | string | No | The saved analytics report the tile reads, as insights:<id> or funnels:<id>. type metric only. |
| `window` | object | No | type metric only. |
| `content` | string | No | The element's text: a plain string ("Ship the beta"), or ProseMirror document JSON for formatting. type shape, sticky, text only. |
| `frameId` | string | No | Owning frame id when the element lives inside a frame. |
| `groupId` | string | No | Group membership; elements sharing a groupId move/rotate/delete as a unit. |
| `clipRect` | object | No | type image only. |
| `endArrow` | string ("none" | "arrow") | No | type connector only. |
| `language` | string | No | type codeBlock only. |
| `rotation` | number | No | Degrees about the element's center. |
| `hideChart` | boolean | No | type metric only. |
| `hideChange` | boolean | No | type metric only. |
| `startArrow` | string ("none" | "arrow") | No | type connector only. |
| `orientation` | string ("horizontal" | "vertical") | No | type swimlane only. |
| `metricWindow` | object | No | type frame only. |
| `sequenceIndex` | number | No | type frame only. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create chart

**Slug:** `AMBIGUOUS_MCP_CREATE_CHART`

Embed 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `x` | number | No |  |
| `y` | number | No |  |
| `id` | string | Yes |  |
| `tab` | string | No | Tab name where the chart lives. Defaults to the first tab. |
| `plot` | object | No |  |
| `type` | string ("bar" | "stackedBar" | "line" | "area" | "pie" | "donut" | "scatter" | "combo") | Yes |  |
| `title` | string | Yes |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `series` | object | No |  |
| `dataRange` | object | Yes |  |
| `useHeaders` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create contact

**Slug:** `AMBIGUOUS_MCP_CREATE_CONTACT`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No |  |
| `type` | string ("person" | "company") | No | `person` is a human contact; `company` is the organisation entity. |
| `email` | string | No |  |
| `phone` | string | No |  |
| `title` | string | No |  |
| `website` | string | No |  |
| `industry` | string | No |  |
| `last_name` | string | No |  |
| `company_id` | string | No |  |
| `first_name` | string | No |  |
| `lifecycle_stage` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | object | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create contact group

**Slug:** `AMBIGUOUS_MCP_CREATE_CONTACT_GROUP`

Create a named contact group for organizing contacts. Groups allow overlapping membership — a contact can be in multiple groups.

#### Input Parameters

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

### Create crm property definition

**Slug:** `AMBIGUOUS_MCP_CREATE_CRM_PROPERTY_DEFINITION`

Define 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `key` | string | Yes |  |
| `label` | string | Yes |  |
| `options` | array | No |  |
| `required` | boolean | No |  |
| `field_type` | string ("text" | "number" | "select" | "multi_select" | "date" | "checkbox" | "url" | "email" | "phone" | "relation") | Yes |  |
| `sort_order` | number | No |  |
| `entity_type` | string ("contact" | "company" | "deal") | Yes |  |
| `relation_target` | string ("contact" | "company" | "deal") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create crm view

**Slug:** `AMBIGUOUS_MCP_CREATE_CRM_VIEW`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `filters` | object | No |  |
| `is_shared` | boolean | No |  |
| `is_default` | boolean | No |  |
| `sort_field` | string | No |  |
| `entity_type` | string ("contacts" | "companies" | "deals") | Yes | Which list page the saved view applies to. |
| `sort_direction` | string ("asc" | "desc") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create data connector

**Slug:** `AMBIGUOUS_MCP_CREATE_DATA_CONNECTOR`

Create a new data connector that fetches data into specific cells of a sheet. After creating, call run_data_connector to execute it.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `type` | string | No |  |
| `config` | object | No |  |
| `targetCol` | string | No |  |
| `targetRow` | string | No |  |
| `target_col` | number | No |  |
| `target_row` | number | No |  |
| `targetSheet` | string | No |  |
| `target_sheet` | string | No |  |
| `refreshSchedule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `refresh_schedule` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create deal

**Slug:** `AMBIGUOUS_MCP_CREATE_DEAL`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | Yes |  |
| `amount` | string | No |  |
| `status` | string ("open" | "won" | "lost") | No | Lifecycle of a deal. `won` and `lost` close the deal; `lost` requires a `lost_reason`. |
| `currency` | string | No |  |
| `owner_id` | string | No |  |
| `stage_id` | string | No |  |
| `close_date` | string | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `lost_reason` | string | No |  |
| `pipeline_id` | string | No |  |
| `probability` | integer | No |  |
| `confirm_zero` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | object | No |  |
| `primary_contact_id` | string | No | Alias for `contact_id`. Either is accepted; sending both with different values returns 400. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create deal template

**Slug:** `AMBIGUOUS_MCP_CREATE_DEAL_TEMPLATE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `amount` | string | No |  |
| `currency` | string | No |  |
| `stage_id` | string | No |  |
| `is_active` | boolean | No |  |
| `line_items` | array | No |  |
| `description` | string | No |  |
| `pipeline_id` | string | No |  |
| `probability` | string | No |  |
| `title_template` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | object | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `close_date_offset_days` | string | No |  |

### Create doc

**Slug:** `AMBIGUOUS_MCP_CREATE_DOC`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No |  |
| `labels` | array | No |  |
| `content` | string | No | 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. |
| `page_style` | object | No |  |
| `visibility` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `shared_drive_id` | string | No | Shared drive to create the doc in; omit for My Drive. |
| `parent_folder_id` | string | No | Drive folder to create the doc in. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create draft email

**Slug:** `AMBIGUOUS_MCP_CREATE_DRAFT_EMAIL`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cc` | array | No |  |
| `to` | array | No | Empty drafts allowed; required when sending. |
| `bcc` | array | No |  |
| `fields` | string | No |  |
| `labels` | array | No |  |
| `notify` | string | No |  |
| `deal_id` | string | No |  |
| `subject` | string | No |  |
| `body_html` | string | No | HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text. |
| `body_text` | string | No | Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent. |
| `thread_id` | string | No | Attach the message to an existing thread. |
| `contact_id` | string | No |  |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `references` | array | No |  |
| `attachments` | array | No |  |
| `in_reply_to` | string | No |  |
| `body_markdown` | string | No | Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send. |
| `attachment_ids` | array | No | Drive file IDs to attach. |
| `idempotency_key` | string | No | Optional retry key. Reusing the same key with the same send request returns the original send. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `request_read_receipt` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create event

**Slug:** `AMBIGUOUS_MCP_CREATE_EVENT`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `color` | string | No |  |
| `force` | boolean | No | Allow creating an event in the past. |
| `title` | string | Yes |  |
| `end_at` | string | Yes |  |
| `guests` | array | No | 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. |
| `status` | string ("confirmed" | "tentative" | "cancelled" | "outofoffice") | No | Event status. `outofoffice` is used by the OOO responder. |
| `all_day` | boolean | No |  |
| `deal_id` | string | No |  |
| `location` | string | No |  |
| `start_at` | string | Yes |  |
| `attendees` | array | No | 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. |
| `event_url` | string | No |  |
| `contact_id` | string | No |  |
| `event_type` | string ("default" | "outOfOffice" | "focusTime") | No | 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. |
| `visibility` | string ("default" | "public" | "private") | No | Visibility scope for the event. |
| `calendar_id` | string | Yes |  |
| `description` | string | No |  |
| `resource_ids` | array | No | Resources (rooms/equipment) to book for the new event; booked server-side after insert. |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `transparency` | string ("opaque" | "transparent") | No | Free/busy classification (RFC 5545 TRANSP). `opaque` = Busy (default; blocks availability). `transparent` = Free (e.g. focus time). |
| `conference_url` | string | No | 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. |
| `skip_event_ids` | array | No | Existing-event ids the `new_and_existing` bulk-decline should leave untouched. |
| `auto_conference` | boolean | No |  |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `recurrence_dates` | array | No |  |
| `guests_can_modify` | boolean | No |  |
| `auto_decline_scope` | string ("new_only" | "new_and_existing") | No | 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. |
| `auto_meeting_notes` | boolean | No |  |
| `conference_provider` | string | No |  |
| `auto_decline_message` | string | No | Auto-reply note sent with an OOO decline. |
| `meeting_notes_doc_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `guests_can_invite_others` | boolean | No |  |
| `guests_can_see_other_guests` | boolean | No |  |

### Create folder

**Slug:** `AMBIGUOUS_MCP_CREATE_FOLDER`

Create 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

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

### Create form

**Slug:** `AMBIGUOUS_MCP_CREATE_FORM`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `slug` | string | No |  |
| `title` | string | No |  |
| `fields` | array | No |  |
| `schema` | object | No | Alternative to `fields` — pass `{fields: [...]}` instead. |
| `settings` | object | No |  |
| `description` | string | No |  |
| `is_published` | boolean | No | Publish the form immediately on create. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create form variant

**Slug:** `AMBIGUOUS_MCP_CREATE_FORM_VARIANT`

Create 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

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

### Create mail label

**Slug:** `AMBIGUOUS_MCP_CREATE_MAIL_LABEL`

Create a mail label for organizing threads.

#### Input Parameters

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

### Create mail rule

**Slug:** `AMBIGUOUS_MCP_CREATE_MAIL_RULE`

Create a mail rule that acts on matching messages.

#### Input Parameters

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

### Create mail template

**Slug:** `AMBIGUOUS_MCP_CREATE_MAIL_TEMPLATE`

Create a reusable mail template for composing.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `subject` | string | Yes |  |
| `category` | string | No |  |
| `body_html` | string | No | HTML import normalized to Markdown when body_markdown is absent; wins over body_text. |
| `body_text` | string | No | Literal plain-text body normalized to Markdown when Markdown/HTML are absent. |
| `body_markdown` | string | No | Canonical Markdown body; wins over HTML/text even when explicitly empty. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create named range

**Slug:** `AMBIGUOUS_MCP_CREATE_NAMED_RANGE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | Yes |  |
| `range` | string | No |  |
| `expression` | string | No |  |
| `referenceStyle` | string ("fixed" | "caller-relative-a1") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create pipeline

**Slug:** `AMBIGUOUS_MCP_CREATE_PIPELINE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `stages` | array | No | 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}] |
| `is_default` | boolean | No |  |
| `visibility` | string ("workspace" | "private") | No | workspace (default) shares the pipeline's deals with the whole workspace via the Everyone team; private scopes deals to explicit pipeline members. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create pivot table

**Slug:** `AMBIGUOUS_MCP_CREATE_PIVOT_TABLE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `filters` | string | No |  |
| `rowFields` | array | No |  |
| `sourceRange` | string | No |  |
| `valueFields` | array | No |  |
| `columnFields` | array | No |  |
| `showRowTotals` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `showColumnTotals` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create presentation

**Slug:** `AMBIGUOUS_MCP_CREATE_PRESENTATION`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No | Title for the new deck. Defaults to 'Untitled' if omitted. |
| `content` | string | No | 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. |
| `visibility` | string ("restricted" | "workspace") | No | Initial visibility. Defaults to 'restricted'. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `shared_drive_id` | string | No | Shared drive to create the deck in; omit for My Drive. |
| `parent_folder_id` | string | No | Drive folder to create the deck in. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create product

**Slug:** `AMBIGUOUS_MCP_CREATE_PRODUCT`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sku` | string | No |  |
| `name` | string | Yes |  |
| `currency` | string | No |  |
| `is_active` | boolean | No |  |
| `unit_price` | number | Yes |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `billing_interval` | string ("one_time" | "monthly" | "quarterly" | "yearly") | No |  |
| `contract_term_months` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create project

**Slug:** `AMBIGUOUS_MCP_CREATE_PROJECT`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | Yes |  |
| `color` | string | No |  |
| `visibility` | string ("private" | "team" | "workspace") | No |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `estimation_scale` | string ("fibonacci" | "linear" | "t-shirt") | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create project update

**Slug:** `AMBIGUOUS_MCP_CREATE_PROJECT_UPDATE`

Post 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | string | No |  |
| `status` | string ("on_track" | "at_risk" | "off_track" | "paused" | "completed" | "cancelled") | Yes | Latest status update on the project. `null` when no updates have been posted. |
| `project_id` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create quote

**Slug:** `AMBIGUOUS_MCP_CREATE_QUOTE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `notes` | string | No |  |
| `terms` | string | No |  |
| `title` | string | Yes |  |
| `status` | string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired") | No | Quote lifecycle. `accepted`/`rejected` are terminal; `viewed` is recorded by the open-tracking pixel. |
| `deal_id` | string | No |  |
| `currency` | string | No |  |
| `owner_id` | string | No |  |
| `tax_rate` | number | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `line_items` | array | No |  |
| `valid_until` | string | No |  |
| `quote_number` | string | No |  |
| `discount_type` | string | No |  |
| `discount_value` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create resource comment

**Slug:** `AMBIGUOUS_MCP_CREATE_RESOURCE_COMMENT`

Create 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

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

### Create role

**Slug:** `AMBIGUOUS_MCP_CREATE_ROLE`

Create a custom role with specific permissions. Requires admin role.

#### Input Parameters

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

### Create scheduler link

**Slug:** `AMBIGUOUS_MCP_CREATE_SCHEDULER_LINK`

Create a scheduler link (booking page). Returns the public URL slug and availability settings. If auto_create_contact is true, every booking auto-creates a CRM contact + deal.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `slug` | string | No |  |
| `title` | string | Yes |  |
| `location` | string | No |  |
| `stage_id` | string | No |  |
| `timezone` | string | No |  |
| `is_active` | boolean | No |  |
| `brand_color` | string | No |  |
| `description` | string | No |  |
| `pipeline_id` | string | No |  |
| `member_user_ids` | array | No | Round-robin roster: workspace user ids that share this link's bookings. Empty/omitted = solo (owner only). When set, a slot is offered while any member is free and each booking is assigned to the least-loaded free member. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `duration_minutes` | integer | No |  |
| `max_advance_days` | integer | No |  |
| `availability_hours` | string | No |  |
| `min_notice_minutes` | integer | No |  |
| `auto_create_contact` | boolean | No |  |
| `buffer_after_minutes` | integer | No |  |
| `buffer_before_minutes` | integer | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create scoring rule

**Slug:** `AMBIGUOUS_MCP_CREATE_SCORING_RULE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `field` | string | Yes |  |
| `value` | string | No |  |
| `points` | integer | Yes |  |
| `operator` | string ("equals" | "not_equals" | "contains" | "not_contains" | "is_set" | "is_not_set" | "greater_than" | "less_than") | Yes | Comparison operator for a lead-scoring rule. |
| `is_active` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sequence

**Slug:** `AMBIGUOUS_MCP_CREATE_SEQUENCE`

Create 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

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

### Create shared drive

**Slug:** `AMBIGUOUS_MCP_CREATE_SHARED_DRIVE`

Create a shared drive. Creator becomes a manager.

#### Input Parameters

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

### Create sheet

**Slug:** `AMBIGUOUS_MCP_CREATE_SHEET`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No | Optional title. Defaults to 'Untitled' when omitted. |
| `labels` | array | No |  |
| `content` | string | No | Optional initial SheetData (JSON canvas). String is parsed as JSON server-side; object is stringified. |
| `visibility` | string ("restricted" | "workspace" | "link" | "public") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `shared_drive_id` | string | No | Shared drive to create the sheet in; omit for My Drive. |
| `parent_folder_id` | string | No | Drive folder to create the sheet in. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sheet image

**Slug:** `AMBIGUOUS_MCP_CREATE_SHEET_IMAGE`

Create editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `alt` | string | No |  |
| `col` | integer | Yes |  |
| `row` | integer | Yes |  |
| `src` | string | Yes |  |
| `tab` | string | No |  |
| `width` | number | Yes |  |
| `height` | number | Yes |  |
| `offsetX` | number | Yes |  |
| `offsetY` | number | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sheet picture group

**Slug:** `AMBIGUOUS_MCP_CREATE_SHEET_PICTURE_GROUP`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `alt` | string | No |  |
| `col` | integer | Yes |  |
| `row` | integer | Yes |  |
| `tab` | string | No |  |
| `root` | string | Yes |  |
| `width` | number | Yes |  |
| `height` | number | Yes |  |
| `offsetX` | number | Yes |  |
| `offsetY` | number | Yes |  |
| `intrinsicWidth` | number | Yes |  |
| `intrinsicHeight` | number | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sheet shape

**Slug:** `AMBIGUOUS_MCP_CREATE_SHEET_SHAPE`

Create editable floating shapes with editable text, cell anchors and CSS pixel geometry.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `col` | integer | Yes |  |
| `row` | integer | Yes |  |
| `tab` | string | No |  |
| `fill` | string | Yes |  |
| `text` | string | No |  |
| `type` | string ("rect" | "ellipse") | Yes |  |
| `width` | number | Yes |  |
| `height` | number | Yes |  |
| `stroke` | string | No |  |
| `offsetX` | number | Yes |  |
| `offsetY` | number | Yes |  |
| `padding` | number | No |  |
| `fontSize` | number | No |  |
| `textAlign` | string ("left" | "center" | "right") | No |  |
| `textColor` | string | No |  |
| `textFrame` | string | No |  |
| `fontFamily` | string | No |  |
| `textLayout` | string ("standard" | "excel") | No |  |
| `textScaleX` | number | No |  |
| `textScaleY` | number | No |  |
| `strokeWidth` | number | No |  |
| `drawingFrame` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sign document

**Slug:** `AMBIGUOUS_MCP_CREATE_SIGN_DOCUMENT`

Create a draft signing document.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No |  |
| `message` | string | No |  |
| `expires_at` | string | No |  |
| `source_type` | string ("pdf" | "doc") | No |  |
| `source_doc_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `signer_ordering` | string ("parallel" | "sequential") | No |  |
| `source_pdf_file_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create sign template

**Slug:** `AMBIGUOUS_MCP_CREATE_SIGN_TEMPLATE`

Create a reusable signing template from field layout and signer roles.

#### Input Parameters

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

### Create slicer

**Slug:** `AMBIGUOUS_MCP_CREATE_SLICER`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `x` | number | No |  |
| `y` | number | No |  |
| `id` | string | Yes |  |
| `tab` | string | No | Tab name where the slicer lives. Defaults to the first tab. |
| `title` | string | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `columnId` | string | Yes |  |
| `useHeaders` | boolean | No |  |
| `sourceRange` | object | Yes |  |
| `selectedValues` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create slide master

**Slug:** `AMBIGUOUS_MCP_CREATE_SLIDE_MASTER`

Create a new master slide for a deck. If no elements are provided, a default Title + Subtitle layout is used.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `elements` | array | No |  |
| `background` | string | No | Slide background color, for example "#0F1B33". |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create subtask

**Slug:** `AMBIGUOUS_MCP_CREATE_SUBTASK`

Create a subtask under the given parent task. Equivalent to `POST /api/tasks` with `parent_task_id` pre-filled from the URL parameter.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | Yes | Task title. Required. Max 255 chars; trimmed before insert. |
| `status` | string ("todo" | "in_progress" | "done" | "cancelled" | "blocked") | No | 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. |
| `deal_id` | string | No | Link the task to a CRM deal. |
| `goal_id` | string | No | Link the task to an OKR-style goal. |
| `cycle_id` | string | No | Sprint/cycle this task is scheduled in. |
| `due_date` | string | No | 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'`. |
| `estimate` | integer | No | Story-point estimate (typically 1, 2, 3, 5, 8, 13). |
| `priority` | string ("urgent" | "high" | "medium" | "low") | No | Defaults to `medium`. |
| `label_ids` | array | No | Labels to assign at create time. Each ID must reference a label in the caller's workspace (404 otherwise). |
| `contact_id` | string | No | Link the task to a CRM contact; auto-logs a CRM activity row. |
| `project_id` | string | No |  |
| `sort_order` | number | No | Drag-reorder weight. Lower sorts first. |
| `start_date` | string | No | ISO 8601 date (YYYY-MM-DD); with `due_date` defines a date range. |
| `assignee_id` | string | No | User to assign the task to. Must be in the caller's workspace (403 otherwise). Omit for unassigned. |
| `description` | string | No | Stringified ProseMirror JSON for the rich description. Legacy plain text and Markdown remain readable. |
| `parent_task_id` | string | No | Parent task for subtasks. Omit for top-level tasks. |
| `subscriber_ids` | array | No | 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. |
| `task_status_id` | string | No | Custom status ID; overrides `status` category. |
| `idempotency_key` | string | No | Stable caller key for one creation request. Matching retries return the same task; different content with the same key is rejected. |
| `recurrence_rule` | string | No | RFC 5545 RRULE string. When set, completing the task spawns the next occurrence. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `estimated_minutes` | integer | No | Time-budget estimate in minutes. |
| `custom_field_values` | object | No | Per-task custom-field values keyed by `task_custom_fields.id`. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create task

**Slug:** `AMBIGUOUS_MCP_CREATE_TASK`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | Yes | Task title. Required. Max 255 chars; trimmed before insert. |
| `status` | string ("todo" | "in_progress" | "done" | "cancelled" | "blocked") | No | 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. |
| `deal_id` | string | No | Link the task to a CRM deal. |
| `goal_id` | string | No | Link the task to an OKR-style goal. |
| `cycle_id` | string | No | Sprint/cycle this task is scheduled in. |
| `due_date` | string | No | 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'`. |
| `estimate` | integer | No | Story-point estimate (typically 1, 2, 3, 5, 8, 13). |
| `priority` | string ("urgent" | "high" | "medium" | "low") | No | Defaults to `medium`. |
| `label_ids` | array | No | Labels to assign at create time. Each ID must reference a label in the caller's workspace (404 otherwise). |
| `contact_id` | string | No | Link the task to a CRM contact; auto-logs a CRM activity row. |
| `project_id` | string | No |  |
| `sort_order` | number | No | Drag-reorder weight. Lower sorts first. |
| `start_date` | string | No | ISO 8601 date (YYYY-MM-DD); with `due_date` defines a date range. |
| `assignee_id` | string | No | User to assign the task to. Must be in the caller's workspace (403 otherwise). Omit for unassigned. |
| `description` | string | No | Stringified ProseMirror JSON for the rich description. Legacy plain text and Markdown remain readable. |
| `parent_task_id` | string | No | Parent task for subtasks. Omit for top-level tasks. |
| `subscriber_ids` | array | No | 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. |
| `task_status_id` | string | No | Custom status ID; overrides `status` category. |
| `idempotency_key` | string | No | Stable caller key for one creation request. Matching retries return the same task; different content with the same key is rejected. |
| `recurrence_rule` | string | No | RFC 5545 RRULE string. When set, completing the task spawns the next occurrence. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `estimated_minutes` | integer | No | Time-budget estimate in minutes. |
| `custom_field_values` | object | No | Per-task custom-field values keyed by `task_custom_fields.id`. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create team

**Slug:** `AMBIGUOUS_MCP_CREATE_TEAM`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | Yes |  |
| `slug` | string | No |  |
| `color` | string | No |  |
| `visibility` | string ("public" | "private") | No |  |
| `description` | string | No |  |
| `join_policy` | string ("open" | "request" | "invite") | No |  |
| `parent_team_id` | string | No |  |
| `posting_policy` | string ("open" | "members_only" | "admins_only") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_channels` | array | No |  |
| `email_local_part` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create wiki page

**Slug:** `AMBIGUOUS_MCP_CREATE_WIKI_PAGE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `icon` | string | No |  |
| `slug` | string | No |  |
| `title` | string | Yes |  |
| `content` | string | No | Page content as Markdown string or ProseMirror JSON object. |
| `sort_order` | number | No |  |
| `cover_image` | string | No |  |
| `is_template` | boolean | No |  |
| `parent_page_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `content_markdown` | string | No | Legacy alias for `content`. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create wiki page version

**Slug:** `AMBIGUOUS_MCP_CREATE_WIKI_PAGE_VERSION`

Create 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

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

### Create wiki space

**Slug:** `AMBIGUOUS_MCP_CREATE_WIKI_SPACE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | Yes |  |
| `slug` | string | No |  |
| `is_private` | boolean | No |  |
| `visibility` | string ("restricted" | "workspace" | "link" | "public") | No | Space/page visibility. `restricted` = invitees only. `workspace` = any workspace member. `link` = anyone with the link. `public` = indexable. |
| `description` | string | No |  |
| `workspaceRole` | string ("viewer" | "commenter" | "editor") | No | Role the Everyone-team row grants when visibility is `workspace`. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Create wiki synced block

**Slug:** `AMBIGUOUS_MCP_CREATE_WIKI_SYNCED_BLOCK`

Create 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

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

### Create workspace invite

**Slug:** `AMBIGUOUS_MCP_CREATE_WORKSPACE_INVITE`

Create 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `role` | string | No | `admin` or `member`. Defaults to `member`; any other value becomes `member`. |
| `email` | string | No | One recipient to invite by email. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Crm contact file attach

**Slug:** `AMBIGUOUS_MCP_CRM_CONTACT_FILE_ATTACH`

Attach 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

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

### Crm contact file detach

**Slug:** `AMBIGUOUS_MCP_CRM_CONTACT_FILE_DETACH`

Detach a file from a contact

#### Input Parameters

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

### Crm contact files list

**Slug:** `AMBIGUOUS_MCP_CRM_CONTACT_FILES_LIST`

List files attached to a contact

#### Input Parameters

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

### Crm contact photo get

**Slug:** `AMBIGUOUS_MCP_CRM_CONTACT_PHOTO_GET`

Serve the photo image stored for a CRM contact.

#### Input Parameters

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

### Crm deal activities

**Slug:** `AMBIGUOUS_MCP_CRM_DEAL_ACTIVITIES`

List activities for deal (owner-scoped)

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `type` | string ("note" | "call" | "email" | "meeting" | "task" | "chat") | No | Activity timeline event type. Used for filtering and badges in the UI. |
| `limit` | integer | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Crm deal file attach

**Slug:** `AMBIGUOUS_MCP_CRM_DEAL_FILE_ATTACH`

Attach 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

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

### Crm deal file detach

**Slug:** `AMBIGUOUS_MCP_CRM_DEAL_FILE_DETACH`

Detach a file from a deal

#### Input Parameters

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

### Crm deal files list

**Slug:** `AMBIGUOUS_MCP_CRM_DEAL_FILES_LIST`

List files attached to a deal

#### Input Parameters

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

### Crm quote pdf

**Slug:** `AMBIGUOUS_MCP_CRM_QUOTE_PDF`

Export quote as PDF (or printable HTML with ?format=html)

#### Input Parameters

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

### Cycles add tasks

**Slug:** `AMBIGUOUS_MCP_CYCLES_ADD_TASKS`

Add tasks to the cycle. Body `{task_ids: [...]}`.

#### Input Parameters

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

### Cycles analytics

**Slug:** `AMBIGUOUS_MCP_CYCLES_ANALYTICS`

Burndown + summary analytics for the cycle.

#### Input Parameters

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

### Cycles complete

**Slug:** `AMBIGUOUS_MCP_CYCLES_COMPLETE`

Complete a cycle. If `auto_rollover` is set, incomplete tasks are moved to the next cycle.

#### Input Parameters

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

### Cycles create

**Slug:** `AMBIGUOUS_MCP_CYCLES_CREATE`

Create a new cycle. Body fields: name, start_date, end_date, status?, cooldown_days?, auto_rollover?.

#### Input Parameters

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

### Cycles delete

**Slug:** `AMBIGUOUS_MCP_CYCLES_DELETE`

Delete a cycle. Tasks attached to the cycle are unlinked, not deleted.

#### Input Parameters

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

### Cycles get

**Slug:** `AMBIGUOUS_MCP_CYCLES_GET`

Get one task cycle and its dates by id.

#### Input Parameters

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

### Cycles list

**Slug:** `AMBIGUOUS_MCP_CYCLES_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No |  |
| `status` | string ("planned" | "active" | "completed" | "cancelled") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Cycles remove tasks

**Slug:** `AMBIGUOUS_MCP_CYCLES_REMOVE_TASKS`

Remove tasks from the cycle. Body `{task_ids: [...]}`.

#### Input Parameters

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

### Cycles update

**Slug:** `AMBIGUOUS_MCP_CYCLES_UPDATE`

Update cycle fields.

#### Input Parameters

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

### Cycles velocity

**Slug:** `AMBIGUOUS_MCP_CYCLES_VELOCITY`

Cross-cycle velocity (last N closed cycles). Default `limit=10`.

#### Input Parameters

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

### Decide access request

**Slug:** `AMBIGUOUS_MCP_DECIDE_ACCESS_REQUEST`

Approve 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

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

### Decide mail approval

**Slug:** `AMBIGUOUS_MCP_DECIDE_MAIL_APPROVAL`

Approve 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `note` | string | No | Surfaced to the sender — the reason on Request changes or Reject. |
| `decision` | string ("approved" | "changes_requested" | "rejected" | "withdrawn") | Yes | The outcome asked for. `withdrawn` is the SENDER's retraction; the other three are the reviewer's. |
| `revision` | integer | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Delete activity

**Slug:** `AMBIGUOUS_MCP_DELETE_ACTIVITY`

Delete one logged CRM activity by id.

#### Input Parameters

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

### Delete canvas element

**Slug:** `AMBIGUOUS_MCP_DELETE_CANVAS_ELEMENT`

Delete 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

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

### Delete chart

**Slug:** `AMBIGUOUS_MCP_DELETE_CHART`

Remove a chart from the sheet. Returns `{ deleted: true }` on success.

#### Input Parameters

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

### Delete conditional format

**Slug:** `AMBIGUOUS_MCP_DELETE_CONDITIONAL_FORMAT`

Delete a conditional formatting rule from a spreadsheet by its ID. Returns 200 on success, 404 if the rule does not exist.

#### Input Parameters

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

### Delete contact

**Slug:** `AMBIGUOUS_MCP_DELETE_CONTACT`

Delete 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

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

### Delete contact group

**Slug:** `AMBIGUOUS_MCP_DELETE_CONTACT_GROUP`

Delete a contact group. Memberships are removed but contacts themselves are preserved.

#### Input Parameters

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

### Delete contact photo

**Slug:** `AMBIGUOUS_MCP_DELETE_CONTACT_PHOTO`

Delete a CRM contact's profile photo. Clears the avatar_url and removes the stored image.

#### Input Parameters

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

### Delete coworker

**Slug:** `AMBIGUOUS_MCP_DELETE_COWORKER`

Delete a coworker (revokes API key + tears down config).

#### Input Parameters

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

### Delete crm property definition

**Slug:** `AMBIGUOUS_MCP_DELETE_CRM_PROPERTY_DEFINITION`

Delete a custom-property definition. Existing custom_properties values are left in place; they simply stop being typed.

#### Input Parameters

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

### Delete crm view

**Slug:** `AMBIGUOUS_MCP_DELETE_CRM_VIEW`

Delete a saved CRM view.

#### Input Parameters

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

### Delete custom emoji

**Slug:** `AMBIGUOUS_MCP_DELETE_CUSTOM_EMOJI`

Delete 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

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

### Delete data connector

**Slug:** `AMBIGUOUS_MCP_DELETE_DATA_CONNECTOR`

Delete a data connector. Does not affect the cells it previously wrote to.

#### Input Parameters

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

### Delete deal

**Slug:** `AMBIGUOUS_MCP_DELETE_DEAL`

Delete 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

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

### Delete deal line item

**Slug:** `AMBIGUOUS_MCP_DELETE_DEAL_LINE_ITEM`

Delete a deal line item. By default the deal's total amount is re-synced after deletion.

#### Input Parameters

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

### Delete deal template

**Slug:** `AMBIGUOUS_MCP_DELETE_DEAL_TEMPLATE`

Delete a deal template (does not affect deals previously created from it).

#### Input Parameters

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

### Delete document version

**Slug:** `AMBIGUOUS_MCP_DELETE_DOCUMENT_VERSION`

Delete 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

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

### Delete email

**Slug:** `AMBIGUOUS_MCP_DELETE_EMAIL`

Delete one email message by id.

#### Input Parameters

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

### Delete event

**Slug:** `AMBIGUOUS_MCP_DELETE_EVENT`

Delete 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Delete file

**Slug:** `AMBIGUOUS_MCP_DELETE_FILE`

Delete 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

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

### Delete form

**Slug:** `AMBIGUOUS_MCP_DELETE_FORM`

Delete 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

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

### Delete form response

**Slug:** `AMBIGUOUS_MCP_DELETE_FORM_RESPONSE`

Delete 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

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

### Delete form variant

**Slug:** `AMBIGUOUS_MCP_DELETE_FORM_VARIANT`

Delete 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

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

### Delete mail label

**Slug:** `AMBIGUOUS_MCP_DELETE_MAIL_LABEL`

Delete one mail label from this mailbox.

#### Input Parameters

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

### Delete mail rule

**Slug:** `AMBIGUOUS_MCP_DELETE_MAIL_RULE`

Delete one mail rule by id.

#### Input Parameters

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

### Delete mail template

**Slug:** `AMBIGUOUS_MCP_DELETE_MAIL_TEMPLATE`

Delete one saved mail template by id.

#### Input Parameters

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

### Delete named range

**Slug:** `AMBIGUOUS_MCP_DELETE_NAMED_RANGE`

Delete a named range from a spreadsheet by name. Names are matched case-insensitively.

#### Input Parameters

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

### Delete pipeline

**Slug:** `AMBIGUOUS_MCP_DELETE_PIPELINE`

Delete a CRM pipeline and all of its stages. Deals in the pipeline must be moved or deleted first.

#### Input Parameters

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

### Delete pivot table

**Slug:** `AMBIGUOUS_MCP_DELETE_PIVOT_TABLE`

Remove 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

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

### Delete product

**Slug:** `AMBIGUOUS_MCP_DELETE_PRODUCT`

Delete a product from the workspace catalog. Existing deal/quote line items referencing it are NOT deleted, but their product_id is nulled.

#### Input Parameters

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

### Delete project

**Slug:** `AMBIGUOUS_MCP_DELETE_PROJECT`

Delete 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

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

### Delete quote

**Slug:** `AMBIGUOUS_MCP_DELETE_QUOTE`

Delete a CRM quote and its line items.

#### Input Parameters

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

### Delete recurring event future

**Slug:** `AMBIGUOUS_MCP_DELETE_RECURRING_EVENT_FUTURE`

Delete 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `split_date` | string | Yes |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Delete recurring event single

**Slug:** `AMBIGUOUS_MCP_DELETE_RECURRING_EVENT_SINGLE`

Delete 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `occurrence_date` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Delete resource comment

**Slug:** `AMBIGUOUS_MCP_DELETE_RESOURCE_COMMENT`

Delete 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

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

### Delete role

**Slug:** `AMBIGUOUS_MCP_DELETE_ROLE`

Delete a custom role. System roles cannot be deleted. Requires admin role.

#### Input Parameters

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

### Delete scheduler link

**Slug:** `AMBIGUOUS_MCP_DELETE_SCHEDULER_LINK`

Delete a scheduler link. Existing confirmed bookings remain but the public booking page stops accepting new bookings.

#### Input Parameters

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

### Delete scoring rule

**Slug:** `AMBIGUOUS_MCP_DELETE_SCORING_RULE`

Delete a lead scoring rule.

#### Input Parameters

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

### Delete sequence

**Slug:** `AMBIGUOUS_MCP_DELETE_SEQUENCE`

Delete a sequence (and all its enrollments).

#### Input Parameters

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

### Delete shared drive

**Slug:** `AMBIGUOUS_MCP_DELETE_SHARED_DRIVE`

Delete a shared drive (destructive, manager-only).

#### Input Parameters

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

### Delete sheet columns

**Slug:** `AMBIGUOUS_MCP_DELETE_SHEET_COLUMNS`

Delete columns atomically and return the bounded change receipt for undo or redo.

#### Input Parameters

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

### Delete sheet image

**Slug:** `AMBIGUOUS_MCP_DELETE_SHEET_IMAGE`

Delete editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

#### Input Parameters

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

### Delete sheet picture group

**Slug:** `AMBIGUOUS_MCP_DELETE_SHEET_PICTURE_GROUP`

Delete 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

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

### Delete sheet rows

**Slug:** `AMBIGUOUS_MCP_DELETE_SHEET_ROWS`

Delete rows from a sheet tab by 0-based index.

#### Input Parameters

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

### Delete sheet shape

**Slug:** `AMBIGUOUS_MCP_DELETE_SHEET_SHAPE`

Delete editable floating shapes with editable text, cell anchors and CSS pixel geometry.

#### Input Parameters

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

### Delete slicer

**Slug:** `AMBIGUOUS_MCP_DELETE_SLICER`

Remove a slicer from the sheet. Returns `{ deleted: true }` on success.

#### Input Parameters

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

### Delete slide master

**Slug:** `AMBIGUOUS_MCP_DELETE_SLIDE_MASTER`

Delete an unused master slide. Returns 409 with the referencing slide count while the master is in use.

#### Input Parameters

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

### Delete team

**Slug:** `AMBIGUOUS_MCP_DELETE_TEAM`

Permanently 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

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

### Delete user

**Slug:** `AMBIGUOUS_MCP_DELETE_USER`

Irreversibly 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `successor_user_id` | string | No | 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. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Delete wiki page

**Slug:** `AMBIGUOUS_MCP_DELETE_WIKI_PAGE`

Move 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

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

### Delete wiki synced block

**Slug:** `AMBIGUOUS_MCP_DELETE_WIKI_SYNCED_BLOCK`

Soft-delete a synced block. Embedded references will show error chips until restored. Use restore_wiki_synced_block to undo.

#### Input Parameters

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

### Detach master from slide

**Slug:** `AMBIGUOUS_MCP_DETACH_MASTER_FROM_SLIDE`

Detach a slide from its master. The slide keeps its current rendered elements but no longer inherits from the master.

#### Input Parameters

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

### Docs create named range

**Slug:** `AMBIGUOUS_MCP_DOCS_CREATE_NAMED_RANGE`

Create 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

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

### Docs delete named range

**Slug:** `AMBIGUOUS_MCP_DOCS_DELETE_NAMED_RANGE`

Delete a named range (template placeholder) from a document by name. Names are unique per document.

#### Input Parameters

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

### Docs list named ranges

**Slug:** `AMBIGUOUS_MCP_DOCS_LIST_NAMED_RANGES`

List all named ranges (template placeholders) defined on a document. Returns each range's name and its anchored node positions.

#### Input Parameters

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

### Documents asset create

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_ASSET_CREATE`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No | File name to keep with the image; defaults to `image`. |
| `mime_type` | string | No | Declared type. The stored type is decided from the bytes. |
| `source_url` | string | No | 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. |
| `content_base64` | string | No | The image bytes, base64-encoded (no `data:` prefix). |
| `source_file_id` | string | No | Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Documents comment delete

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_DELETE`

Delete a comment. Author or document owner only.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `commentId` | string | Yes |  |

### Documents comment reaction add

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_REACTION_ADD`

Add an emoji reaction to a comment. Idempotent per (user, emoji). Returns the comment's updated reaction aggregate.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `emoji` | string | Yes |  |
| `commentId` | string | Yes |  |

### Documents comment reaction remove

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_REACTION_REMOVE`

Remove the caller's emoji reaction from a comment. Returns the comment's updated reaction aggregate.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `emoji` | string | Yes |  |
| `commentId` | string | Yes |  |

### Documents comment resolve

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_RESOLVE`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `content` | string | No |  |
| `resolved` | boolean | No |  |
| `commentId` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `expected_content` | string | No | Original content captured when editing began. A changed comment returns 409. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Documents comments create

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_CREATE`

Add a threaded comment. Commenter permission required. `parent_id` makes it a reply; `anchor` carries CRDT-stable position info.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `anchor` | object | No |  |
| `content` | string | Yes |  |
| `parent_id` | string | No |  |
| `idempotency_key` | string | No |  |

### Documents comments list

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_LIST`

List threaded comments. Response includes per-user `unread_count` (comments by other users since the requester's last `mark-read`, not resolved).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |

### Documents comments mark read

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENTS_MARK_READ`

Advance the requester's last-seen marker so the unread badge clears. Idempotent.

#### Input Parameters

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

### Documents comment thread mark read

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_THREAD_MARK_READ`

Mark 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

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

### Documents comment thread mark unread

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_COMMENT_THREAD_MARK_UNREAD`

Mark 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

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

### Documents delete

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_DELETE`

Soft-delete a document (move to trash). Owner only.

#### Input Parameters

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

### Documents duplicate

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_DUPLICATE`

Make 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

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

### Documents permanent delete

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_PERMANENT_DELETE`

Permanently delete a trashed document. Irreversible.

#### Input Parameters

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

### Documents pin

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_PIN`

Toggle pinned state. Editor permission required (workspace-wide pin, not per-user).

#### Input Parameters

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

### Documents restore

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_RESTORE`

Restore a trashed document.

#### Input Parameters

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

### Documents shared with me

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_SHARED_WITH_ME`

Documents 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `type` | string ("doc" | "sheet" | "slide" | "canvas") | No | Filter by document type. |
| `limit` | integer | No |  |
| `scope` | string ("account" | "workspace") | No | Account-wide by default. `workspace` lists only resources in the authenticated current workspace; grants and resource access remain unchanged. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Documents star

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_STAR`

Toggle starred state. Viewer permission is sufficient. Body `{starred: bool}` is optional — omit to toggle.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `starred` | boolean | No | Omit to toggle the current state. |

### Documents thumbnail

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_THUMBNAIL`

Content-derived thumbnail for doc/sheet/slide cards. Returns SVG by default or PNG for Accept: image/png; cached privately for 60 seconds.

#### Input Parameters

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

### Documents trash list

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_TRASH_LIST`

Find 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

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

### Documents version get

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_VERSION_GET`

Get a version's metadata + serialized content snapshot.

#### Input Parameters

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

### Documents version revert

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_VERSION_REVERT`

Revert the document to a prior version. Force-snapshots current state first.

#### Input Parameters

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

### Documents versions create

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_VERSIONS_CREATE`

Create a manual snapshot (forces past the 5-minute throttle).

#### Input Parameters

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

### Documents versions list

**Slug:** `AMBIGUOUS_MCP_DOCUMENTS_VERSIONS_LIST`

List version snapshots, newest-first, cursor-paginated (default 50 per page). Walk via `next_cursor` until `has_more` is false.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `limit` | integer | No |  |
| `cursor` | string | No | Opaque cursor from a prior `next_cursor`. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Drive file confirm upload

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_CONFIRM_UPLOAD`

Confirm 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

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

### Drive file content

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_CONTENT`

A 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `download` | string | No |  |

### Drive file import

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_IMPORT`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `url` | string | No | 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. |
| `name` | string | Yes | File name to store, including its extension. |
| `mime_type` | string | No | 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. |
| `content_base64` | string | No | The file's bytes, base64-encoded, up to 25 MB once decoded. Send this or `url`, not both. |
| `idempotency_key` | string | No | Reuse this key only to retry the same import. A changed request returns 409. Use a new key for each new import. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `parent_folder_id` | string | No | Folder to place the file in. Omit for the Drive root. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Drive file request create

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_CREATE`

Create a revocable, write-only public file request for a folder. The capability token is returned only in this response.

#### Input Parameters

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

### Drive file request remint

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_REMINT`

Replace 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

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

### Drive file request revoke

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_REQUEST_REVOKE`

Revoke a folder's public file request immediately.

#### Input Parameters

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

### Drive file requests list

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_REQUESTS_LIST`

List the caller's file requests for one owned Drive folder.

#### Input Parameters

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

### Drive files recent

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILES_RECENT`

Recently 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

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

### Drive files shared with me

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILES_SHARED_WITH_ME`

Files 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

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

### Drive files starred

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILES_STARRED`

Files the current user has starred.

#### Input Parameters

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

### Drive files suggested

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILES_SUGGESTED`

Files 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No | How many to return, 1 to 10. Defaults to 3. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Drive file tag attach

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_TAG_ATTACH`

Attach 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

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

### Drive file tag detach

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_TAG_DETACH`

Detach 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

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

### Drive file update

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_UPDATE`

Rename, 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

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

### Drive file upload init

**Slug:** `AMBIGUOUS_MCP_DRIVE_FILE_UPLOAD_INIT`

Initiate 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `source` | string ("chat" | "mail") | No | 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://<file_id>)` 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. |
| `mime_type` | string | Yes |  |
| `size_bytes` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `parent_folder_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Drive folder ancestors

**Slug:** `AMBIGUOUS_MCP_DRIVE_FOLDER_ANCESTORS`

Breadcrumb chain (root → leaf) for a folder. Powers breadcrumb hydration on deep-link reloads. Viewer permission is sufficient.

#### Input Parameters

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

### Drive publish gallery

**Slug:** `AMBIGUOUS_MCP_DRIVE_PUBLISH_GALLERY`

Publish a folder as an anyone-with-link gallery: stamp link visibility plus the given password/expiry onto the folder and its direct-child non-folder files, skipping legal records (reported as skipped_legal). An omitted password or expires_at keeps the folder's current value, so re-publishing to admit new files keeps the gallery's protection; an explicit null (or empty password) clears it. Owner-only. Materialized, not a cascade — files added after publishing stay restricted until republished.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `password` | string | No | Password gating the gallery. Omit to keep the folder's current password; null or empty clears it. |
| `expires_at` | string | No | ISO 8601 expiry for the gallery link. Omit to keep the folder's current expiry; null clears it. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Drive revoke gallery

**Slug:** `AMBIGUOUS_MCP_DRIVE_REVOKE_GALLERY`

Revoke a folder gallery: restore the folder and its direct-child files to restricted and clear link settings. Owner-only. Legal-record children are left untouched.

#### Input Parameters

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

### Drive shared drive folder create

**Slug:** `AMBIGUOUS_MCP_DRIVE_SHARED_DRIVE_FOLDER_CREATE`

Create a folder inside a shared drive. Requires contributor+ on the drive. Pass `parent_folder_id` to nest.

#### Input Parameters

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

### Drive tag create

**Slug:** `AMBIGUOUS_MCP_DRIVE_TAG_CREATE`

Create a new tag in the user's catalog.

#### Input Parameters

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

### Drive tag delete

**Slug:** `AMBIGUOUS_MCP_DRIVE_TAG_DELETE`

Delete a tag (cascades to all file assignments).

#### Input Parameters

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

### Drive tag files list

**Slug:** `AMBIGUOUS_MCP_DRIVE_TAG_FILES_LIST`

List 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

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

### Drive tags list

**Slug:** `AMBIGUOUS_MCP_DRIVE_TAGS_LIST`

Current user's tag catalog. Each tag carries name, color, and sort order.

#### Input Parameters

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

### Drive tag update

**Slug:** `AMBIGUOUS_MCP_DRIVE_TAG_UPDATE`

Rename, recolor, or reorder a tag.

#### Input Parameters

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

### Duplicate slide

**Slug:** `AMBIGUOUS_MCP_DUPLICATE_SLIDE`

Deep-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

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

### Duplicate task

**Slug:** `AMBIGUOUS_MCP_DUPLICATE_TASK`

Clone 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

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

### Edit recurring event all

**Slug:** `AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_ALL`

Edit all occurrences in a recurring series. Updates the master event.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `color` | string | No |  |
| `force` | boolean | No |  |
| `title` | string | No |  |
| `end_at` | string | No |  |
| `guests` | array | No | 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. |
| `status` | string ("confirmed" | "tentative" | "cancelled" | "outofoffice") | No | Event status. `outofoffice` is used by the OOO responder. |
| `all_day` | boolean | No |  |
| `deal_id` | string | No |  |
| `location` | string | No |  |
| `start_at` | string | No |  |
| `attendees` | array | No | 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. |
| `event_url` | string | No |  |
| `contact_id` | string | No |  |
| `event_type` | string ("default" | "outOfOffice" | "focusTime") | No | 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. |
| `visibility` | string ("default" | "public" | "private") | No | Visibility scope for the event. |
| `description` | string | No |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `transparency` | string ("opaque" | "transparent") | No | Free/busy classification (RFC 5545 TRANSP). `opaque` = Busy (default; blocks availability). `transparent` = Free (e.g. focus time). |
| `conference_url` | string | No | 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. |
| `skip_event_ids` | array | No | Existing-event ids the `new_and_existing` bulk-decline should leave untouched. |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `recurrence_dates` | array | No |  |
| `guests_can_modify` | boolean | No |  |
| `auto_decline_scope` | string ("new_only" | "new_and_existing") | No | 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. |
| `conference_provider` | string | No |  |
| `auto_decline_message` | string | No | Auto-reply note sent with an OOO decline. |
| `meeting_notes_doc_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `guests_can_invite_others` | boolean | No |  |
| `guests_can_see_other_guests` | boolean | No |  |

### Edit recurring event future

**Slug:** `AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_FUTURE`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `color` | string | No |  |
| `force` | boolean | No |  |
| `title` | string | No |  |
| `end_at` | string | No |  |
| `guests` | array | No | 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. |
| `status` | string ("confirmed" | "tentative" | "cancelled" | "outofoffice") | No | Event status. `outofoffice` is used by the OOO responder. |
| `all_day` | boolean | No |  |
| `deal_id` | string | No |  |
| `location` | string | No |  |
| `start_at` | string | No |  |
| `attendees` | array | No | 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. |
| `event_url` | string | No |  |
| `contact_id` | string | No |  |
| `event_type` | string ("default" | "outOfOffice" | "focusTime") | No | 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. |
| `split_date` | string | Yes | Date at which to split the series; the master ends the day before. |
| `visibility` | string ("default" | "public" | "private") | No | Visibility scope for the event. |
| `description` | string | No |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `transparency` | string ("opaque" | "transparent") | No | Free/busy classification (RFC 5545 TRANSP). `opaque` = Busy (default; blocks availability). `transparent` = Free (e.g. focus time). |
| `conference_url` | string | No | 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. |
| `skip_event_ids` | array | No | Existing-event ids the `new_and_existing` bulk-decline should leave untouched. |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `recurrence_dates` | array | No |  |
| `guests_can_modify` | boolean | No |  |
| `auto_decline_scope` | string ("new_only" | "new_and_existing") | No | 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. |
| `conference_provider` | string | No |  |
| `auto_decline_message` | string | No | Auto-reply note sent with an OOO decline. |
| `meeting_notes_doc_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `guests_can_invite_others` | boolean | No |  |
| `guests_can_see_other_guests` | boolean | No |  |

### Edit recurring event single

**Slug:** `AMBIGUOUS_MCP_EDIT_RECURRING_EVENT_SINGLE`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `color` | string | No |  |
| `force` | boolean | No |  |
| `title` | string | No |  |
| `end_at` | string | No |  |
| `guests` | array | No | 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. |
| `status` | string ("confirmed" | "tentative" | "cancelled" | "outofoffice") | No | Event status. `outofoffice` is used by the OOO responder. |
| `all_day` | boolean | No |  |
| `deal_id` | string | No |  |
| `location` | string | No |  |
| `start_at` | string | No |  |
| `attendees` | array | No | 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. |
| `event_url` | string | No |  |
| `contact_id` | string | No |  |
| `event_type` | string ("default" | "outOfOffice" | "focusTime") | No | 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. |
| `visibility` | string ("default" | "public" | "private") | No | Visibility scope for the event. |
| `description` | string | No |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `transparency` | string ("opaque" | "transparent") | No | Free/busy classification (RFC 5545 TRANSP). `opaque` = Busy (default; blocks availability). `transparent` = Free (e.g. focus time). |
| `conference_url` | string | No | 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. |
| `skip_event_ids` | array | No | Existing-event ids the `new_and_existing` bulk-decline should leave untouched. |
| `occurrence_date` | string | Yes | RECURRENCE-ID of the occurrence to split out as an exception. |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `recurrence_dates` | array | No |  |
| `guests_can_modify` | boolean | No |  |
| `auto_decline_scope` | string ("new_only" | "new_and_existing") | No | 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. |
| `conference_provider` | string | No |  |
| `auto_decline_message` | string | No | Auto-reply note sent with an OOO decline. |
| `meeting_notes_doc_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `guests_can_invite_others` | boolean | No |  |
| `guests_can_see_other_guests` | boolean | No |  |

### Empty trash

**Slug:** `AMBIGUOUS_MCP_EMPTY_TRASH`

Permanently 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

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

### Enroll contact in sequence

**Slug:** `AMBIGUOUS_MCP_ENROLL_CONTACT_IN_SEQUENCE`

Enroll 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

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

### Ensure wiki reverse relation

**Slug:** `AMBIGUOUS_MCP_ENSURE_WIKI_REVERSE_RELATION`

Auto-create the reverse relation property on the target database if missing. Idempotent — returns the existing or newly-created reverse property id.

#### Input Parameters

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

### Export document

**Slug:** `AMBIGUOUS_MCP_EXPORT_DOCUMENT`

Export 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

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

### Export drive file

**Slug:** `AMBIGUOUS_MCP_EXPORT_DRIVE_FILE`

Export 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `format` | string | No | Target export format (e.g., docx, pdf, xlsx, csv, pptx). Validated by the handler. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Export form responses

**Slug:** `AMBIGUOUS_MCP_EXPORT_FORM_RESPONSES`

Download 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `value` | string | No | Required when `field_id` is set (legacy single-filter). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `filters` | string | No | URL-encoded JSON array of {field_id, op, value} objects. Operators: contains, equals, is_empty, is_not_empty. Multiple filters AND together. |
| `field_id` | string | No | Filter by exact value of a specific field (legacy single-filter). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `submitted_after` | string | No | ISO 8601 timestamp; only responses submitted after this. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Find and replace in deck

**Slug:** `AMBIGUOUS_MCP_FIND_AND_REPLACE_IN_DECK`

Find 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

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

### Formatter set

**Slug:** `AMBIGUOUS_MCP_FORMATTER_SET`

Set 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `values` | object | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get account erasure outcome

**Slug:** `AMBIGUOUS_MCP_GET_ACCOUNT_ERASURE_OUTCOME`

Read a deleted member's durable erasure outcome and notice-delivery state. Requires admin or owner.

#### Input Parameters

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

### Get activity

**Slug:** `AMBIGUOUS_MCP_GET_ACTIVITY`

Get 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

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

### Get billing bonuses

**Slug:** `AMBIGUOUS_MCP_GET_BILLING_BONUSES`

Return 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.

### Get billing quota

**Slug:** `AMBIGUOUS_MCP_GET_BILLING_QUOTA`

Return 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.

### Get calendar

**Slug:** `AMBIGUOUS_MCP_GET_CALENDAR`

Get 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

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

### Get calendar colors

**Slug:** `AMBIGUOUS_MCP_GET_CALENDAR_COLORS`

Get 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

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

### Get canvas

**Slug:** `AMBIGUOUS_MCP_GET_CANVAS`

Get 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

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

### Get canvas elements

**Slug:** `AMBIGUOUS_MCP_GET_CANVAS_ELEMENTS`

Batch-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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Canvas board id. |
| `ids` | string | Yes | Comma-separated element ids to fetch (max 500). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get canvas frame

**Slug:** `AMBIGUOUS_MCP_GET_CANVAS_FRAME`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Canvas board id. |
| `frameId` | string | Yes | Frame (or swimlane) element id within the board. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get canvas manifest

**Slug:** `AMBIGUOUS_MCP_GET_CANVAS_MANIFEST`

Get 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

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

### Get channel messages

**Slug:** `AMBIGUOUS_MCP_GET_CHANNEL_MESSAGES`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | 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. |
| `limit` | string | No | Max messages to return (default 50, cap 100). |
| `around` | string | No | 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. |
| `before` | string | No | Message ID — return messages older than this message. |
| `cursor` | string | No | Opaque cursor from a prior `next_cursor`. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Offset for legacy pagination. |
| `channel_id` | string | Yes |  |
| `before_date` | string | No | ISO timestamp — return messages created before this instant. |
| `show_deleted` | string ("true" | "false") | No | Pass 'true' to include soft-deleted messages (rendered as tombstones). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get channel read receipts

**Slug:** `AMBIGUOUS_MCP_GET_CHANNEL_READ_RECEIPTS`

Get 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

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

### Get contact

**Slug:** `AMBIGUOUS_MCP_GET_CONTACT`

Get 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

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

### Get contact score

**Slug:** `AMBIGUOUS_MCP_GET_CONTACT_SCORE`

Get 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

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

### Get cover thumbnail

**Slug:** `AMBIGUOUS_MCP_GET_COVER_THUMBNAIL`

Get 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

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

### Get coworker

**Slug:** `AMBIGUOUS_MCP_GET_COWORKER`

Get one AI coworker's configuration by id.

#### Input Parameters

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

### Get coworker status

**Slug:** `AMBIGUOUS_MCP_GET_COWORKER_STATUS`

Get a coworker's runtime status (proxied from coworker service).

#### Input Parameters

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

### Get crm analytics

**Slug:** `AMBIGUOUS_MCP_GET_CRM_ANALYTICS`

Get 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

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

### Get crm metrics

**Slug:** `AMBIGUOUS_MCP_GET_CRM_METRICS`

Get 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

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

### Get crm reports

**Slug:** `AMBIGUOUS_MCP_GET_CRM_REPORTS`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `period` | string ("ytd" | "this_quarter" | "this_month" | "all_time") | No |  |
| `pipeline_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get current workspace

**Slug:** `AMBIGUOUS_MCP_GET_CURRENT_WORKSPACE`

Get the active workspace (name, slug, logo). Accessible to any authenticated user.

#### Input Parameters

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

### Get data connector

**Slug:** `AMBIGUOUS_MCP_GET_DATA_CONNECTOR`

Get a single data connector by ID, including its config and last-run status.

#### Input Parameters

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

### Get deal

**Slug:** `AMBIGUOUS_MCP_GET_DEAL`

Get 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

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

### Get deal template

**Slug:** `AMBIGUOUS_MCP_GET_DEAL_TEMPLATE`

Get a single deal template with its line items and resolved pipeline/stage names.

#### Input Parameters

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

### Get detailed user presence

**Slug:** `AMBIGUOUS_MCP_GET_DETAILED_USER_PRESENCE`

Get 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

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

### Get docs page layout default

**Slug:** `AMBIGUOUS_MCP_GET_DOCS_PAGE_LAYOUT_DEFAULT`

Get 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

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

### Get document

**Slug:** `AMBIGUOUS_MCP_GET_DOCUMENT`

Get 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

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

### Get document footnotes

**Slug:** `AMBIGUOUS_MCP_GET_DOCUMENT_FOOTNOTES`

Get 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

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

### Get document headers footers

**Slug:** `AMBIGUOUS_MCP_GET_DOCUMENT_HEADERS_FOOTERS`

Get the default, first-page, and even-page headers and footers from a document as ProseMirror JSON nodes (or null if not set).

#### Input Parameters

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

### Get document page style

**Slug:** `AMBIGUOUS_MCP_GET_DOCUMENT_PAGE_STYLE`

Get 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

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

### Get drive storage

**Slug:** `AMBIGUOUS_MCP_GET_DRIVE_STORAGE`

Get Drive storage usage.

#### Input Parameters

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

### Get drive storage breakdown

**Slug:** `AMBIGUOUS_MCP_GET_DRIVE_STORAGE_BREAKDOWN`

Storage breakdown by file type.

#### Input Parameters

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

### Get email

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `detail` | string ("full" | "headers" | "minimal") | No | Response shape: `full` (default), `headers` (envelope only), `minimal` (id + labels). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `mark_read` | string ("true" | "false") | No | Set to false to read without marking the message read. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get email attachment url

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL_ATTACHMENT_URL`

Get an attachment download URL: signed in cloud storage, authenticated API content in local storage.

#### Input Parameters

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

### Get email calendar invite

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL_CALENDAR_INVITE`

Get calendar invite embedded in an email.

#### Input Parameters

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

### Get email deliverability

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL_DELIVERABILITY`

Get email deliverability statistics (sent/bounced/complained/opened rates) for the past 30 days. Requires admin role.

#### Input Parameters

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

### Get email opens

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL_OPENS`

Fetch 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

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

### Get email signature

**Slug:** `AMBIGUOUS_MCP_GET_EMAIL_SIGNATURE`

Get the workspace default email signature (Markdown). Requires admin role.

#### Input Parameters

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

### Get entity preview

**Slug:** `AMBIGUOUS_MCP_GET_ENTITY_PREVIEW`

Look 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

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

### Get event

**Slug:** `AMBIGUOUS_MCP_GET_EVENT`

Get 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

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

### Get event instances

**Slug:** `AMBIGUOUS_MCP_GET_EVENT_INSTANCES`

List 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

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

### Get feedback

**Slug:** `AMBIGUOUS_MCP_GET_FEEDBACK`

Read 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

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

### Get file info

**Slug:** `AMBIGUOUS_MCP_GET_FILE_INFO`

Get 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

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

### Get form

**Slug:** `AMBIGUOUS_MCP_GET_FORM`

Get 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

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

### Get form ab analytics

**Slug:** `AMBIGUOUS_MCP_GET_FORM_AB_ANALYTICS`

Get 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

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

### Get form analytics

**Slug:** `AMBIGUOUS_MCP_GET_FORM_ANALYTICS`

Get 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

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

### Get form response

**Slug:** `AMBIGUOUS_MCP_GET_FORM_RESPONSE`

Get 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

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

### Get mail approval

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_APPROVAL`

Read 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

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

### Get mail approval attachment url

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_APPROVAL_ATTACHMENT_URL`

Presigned 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

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

### Get mail rule

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_RULE`

Get one mail rule's conditions and actions by id.

#### Input Parameters

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

### Get mail signature

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_SIGNATURE`

Get the effective email signature.

#### Input Parameters

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

### Get mail template

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_TEMPLATE`

Get one saved mail template by id.

#### Input Parameters

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

### Get mail thread

**Slug:** `AMBIGUOUS_MCP_GET_MAIL_THREAD`

Get all emails in a thread + muted flag.

#### Input Parameters

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

### Get message readers

**Slug:** `AMBIGUOUS_MCP_GET_MESSAGE_READERS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Get module availability

**Slug:** `AMBIGUOUS_MCP_GET_MODULE_AVAILABILITY`

Which productivity modules are enabled for the caller's workspace: module key → boolean. Bootstrap gate for nav + routes.

### Get my access request

**Slug:** `AMBIGUOUS_MCP_GET_MY_ACCESS_REQUEST`

Whether 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

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

### Get notification keywords

**Slug:** `AMBIGUOUS_MCP_GET_NOTIFICATION_KEYWORDS`

Get 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

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

### Get ooo status

**Slug:** `AMBIGUOUS_MCP_GET_OOO_STATUS`

Check 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

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

### Get pipeline

**Slug:** `AMBIGUOUS_MCP_GET_PIPELINE`

Get 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

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

### Get presentation

**Slug:** `AMBIGUOUS_MCP_GET_PRESENTATION`

Get 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

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

### Get product

**Slug:** `AMBIGUOUS_MCP_GET_PRODUCT`

Get one CRM product from the catalog by id.

#### Input Parameters

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

### Get project

**Slug:** `AMBIGUOUS_MCP_GET_PROJECT`

Get a single project by ID, including task count, visibility, and metadata.

#### Input Parameters

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

### Get quote

**Slug:** `AMBIGUOUS_MCP_GET_QUOTE`

Get a single CRM quote with its line items and linked deal/contact/company/owner.

#### Input Parameters

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

### Get read receipts default

**Slug:** `AMBIGUOUS_MCP_GET_READ_RECEIPTS_DEFAULT`

Get read-receipts default for new compose.

#### Input Parameters

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

### Get resolved presence

**Slug:** `AMBIGUOUS_MCP_GET_RESOLVED_PRESENCE`

Cold-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

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

### Get scheduler link

**Slug:** `AMBIGUOUS_MCP_GET_SCHEDULER_LINK`

Get a single scheduler link (owner-scoped) with its settings and booking count.

#### Input Parameters

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

### Get security settings

**Slug:** `AMBIGUOUS_MCP_GET_SECURITY_SETTINGS`

Get workspace security settings (require_2fa, session_timeout_hours, password_min_length, ip_allowlist). Requires admin role.

#### Input Parameters

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

### Get sequence

**Slug:** `AMBIGUOUS_MCP_GET_SEQUENCE`

Get a single sequence with its full step list and current enrollment count.

#### Input Parameters

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

### Get settings

**Slug:** `AMBIGUOUS_MCP_GET_SETTINGS`

Get all workspace settings. Requires admin role.

#### Input Parameters

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

### Get shared drive

**Slug:** `AMBIGUOUS_MCP_GET_SHARED_DRIVE`

Get shared drive details.

#### Input Parameters

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

### Get sheet

**Slug:** `AMBIGUOUS_MCP_GET_SHEET`

Get 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

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

### Get sheet range

**Slug:** `AMBIGUOUS_MCP_GET_SHEET_RANGE`

Get 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

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

### Get sign audit

**Slug:** `AMBIGUOUS_MCP_GET_SIGN_AUDIT`

Get the append-only audit trail for a visible signing document.

#### Input Parameters

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

### Get sign document

**Slug:** `AMBIGUOUS_MCP_GET_SIGN_DOCUMENT`

Get a signing document with signers and fields.

#### Input Parameters

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

### Get slide thumbnail

**Slug:** `AMBIGUOUS_MCP_GET_SLIDE_THUMBNAIL`

Get the PNG thumbnail bytes for a specific slide. Sizes: small (200px), medium (800px, default), large (1600px).

#### Input Parameters

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

### Get snooze presets

**Slug:** `AMBIGUOUS_MCP_GET_SNOOZE_PRESETS`

Get the user's custom snooze quick-presets. Returns defaults when no custom presets are saved.

#### Input Parameters

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

### Get swipe actions

**Slug:** `AMBIGUOUS_MCP_GET_SWIPE_ACTIONS`

Get the caller's own mail-row swipe actions. Returns the defaults (right archive, left trash) when nothing is saved.

#### Input Parameters

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

### Get task

**Slug:** `AMBIGUOUS_MCP_GET_TASK`

Get a single task by ID, including full details: title, description, status, priority, assignee, due date, labels, and subtask count.

#### Input Parameters

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

### Get team

**Slug:** `AMBIGUOUS_MCP_GET_TEAM`

Get 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

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

### Get undo send setting

**Slug:** `AMBIGUOUS_MCP_GET_UNDO_SEND_SETTING`

Get undo-send duration preference.

#### Input Parameters

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

### Get unread counts

**Slug:** `AMBIGUOUS_MCP_GET_UNREAD_COUNTS`

Get 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

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

### Get usage stats

**Slug:** `AMBIGUOUS_MCP_GET_USAGE_STATS`

Get 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

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

### Get user presence

**Slug:** `AMBIGUOUS_MCP_GET_USER_PRESENCE`

Get 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

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

### Get users notification preferences

**Slug:** `AMBIGUOUS_MCP_GET_USERS_NOTIFICATION_PREFERENCES`

Return the user's notification preferences, merged with defaults so newly-added keys always render.

### Get user status

**Slug:** `AMBIGUOUS_MCP_GET_USER_STATUS`

Get 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

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

### Get vacation settings

**Slug:** `AMBIGUOUS_MCP_GET_VACATION_SETTINGS`

Get vacation auto-reply settings.

#### Input Parameters

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

### Get wiki database row

**Slug:** `AMBIGUOUS_MCP_GET_WIKI_DATABASE_ROW`

Get a single database row by id.

#### Input Parameters

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

### Get wiki page

**Slug:** `AMBIGUOUS_MCP_GET_WIKI_PAGE`

Get 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

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

### Get wiki page version

**Slug:** `AMBIGUOUS_MCP_GET_WIKI_PAGE_VERSION`

Get 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

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

### Get wiki space graph

**Slug:** `AMBIGUOUS_MCP_GET_WIKI_SPACE_GRAPH`

Get 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

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

### Get wiki synced block

**Slug:** `AMBIGUOUS_MCP_GET_WIKI_SYNCED_BLOCK`

Get 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

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

### Get workspace

**Slug:** `AMBIGUOUS_MCP_GET_WORKSPACE`

Get the current workspace details (id, name, slug). Requires admin role.

#### Input Parameters

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

### Grant access

**Slug:** `AMBIGUOUS_MCP_GRANT_ACCESS`

Share 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | 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. |
| `role` | string ("viewer" | "commenter" | "editor") | Yes |  |
| `email` | string | No |  |
| `message` | string | No |  |
| `team_id` | string | No | 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. |
| `user_id` | string | No | The specific person's ID, separate from the resource id. On update/removal, use the user ID from that resource's permission entry. |
| `expires_at` | string | No | ISO 8601 deadline for the grant, or null for no expiry. Bounded by the shareExpiryMaxDays platform limit. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `invite_to_workspace` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Group slide elements

**Slug:** `AMBIGUOUS_MCP_GROUP_SLIDE_ELEMENTS`

Group 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `index` | string | Yes |  |
| `element_ids` | array | Yes | Element IDs to group on the slide. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Home digest

**Slug:** `AMBIGUOUS_MCP_HOME_DIGEST`

Workspace-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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `window` | string ("7d" | "1d") | No | Trailing window for the velocity counts and the digest: '7d' (default) or '1d' (Today). |

### Insert page break

**Slug:** `AMBIGUOUS_MCP_INSERT_PAGE_BREAK`

Insert 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

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

### Insert page number

**Slug:** `AMBIGUOUS_MCP_INSERT_PAGE_NUMBER`

Insert 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

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

### Insert section break

**Slug:** `AMBIGUOUS_MCP_INSERT_SECTION_BREAK`

Insert 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

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

### Invite user

**Slug:** `AMBIGUOUS_MCP_INVITE_USER`

Invite a human by email with a member or admin role. Requires admin.

#### Input Parameters

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

### Leave resource

**Slug:** `AMBIGUOUS_MCP_LEAVE_RESOURCE`

Remove 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

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

### List access

**Slug:** `AMBIGUOUS_MCP_LIST_ACCESS`

List 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

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

### List activity

**Slug:** `AMBIGUOUS_MCP_LIST_ACTIVITY`

List recent workspace activity (last 30 days). Scoped to the current user's workspace. Filterable by resource type, resource ID, and acting user.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No | Max entries to return (capped at 100, default 50). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Pagination offset. |
| `user_id` | string | No | Filter to actions performed by a specific user (UUID). |
| `resource_id` | string | No | Filter to a specific resource (UUID). |
| `resource_type` | string | No | Filter to a single resource type (e.g. 'document', 'task'). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List address book

**Slug:** `AMBIGUOUS_MCP_LIST_ADDRESS_BOOK`

List 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

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

### List archived threads

**Slug:** `AMBIGUOUS_MCP_LIST_ARCHIVED_THREADS`

List archived threads (one per thread)

#### Input Parameters

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

### List blocked senders

**Slug:** `AMBIGUOUS_MCP_LIST_BLOCKED_SENDERS`

List all blocked senders for current user's mailbox

#### Input Parameters

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

### List calendar events

**Slug:** `AMBIGUOUS_MCP_LIST_CALENDAR_EVENTS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No |  |
| `end` | string | No |  |
| `limit` | integer | No |  |
| `start` | string | No |  |
| `cursor` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `orderBy` | string | No |  |
| `timeZone` | string | No |  |
| `eventTypes` | string | No |  |
| `updatedMin` | string | No |  |
| `calendar_id` | string | Yes |  |
| `showDeleted` | string | No |  |
| `maxAttendees` | string | No |  |
| `singleEvents` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List calendars

**Slug:** `AMBIGUOUS_MCP_LIST_CALENDARS`

List 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

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

### List channels

**Slug:** `AMBIGUOUS_MCP_LIST_CHANNELS`

List 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

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

### List charts

**Slug:** `AMBIGUOUS_MCP_LIST_CHARTS`

List every chart across every tab of the sheet. Each entry is annotated with the `tab` name it lives in.

#### Input Parameters

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

### List conditional formats

**Slug:** `AMBIGUOUS_MCP_LIST_CONDITIONAL_FORMATS`

List all conditional formatting rules on a spreadsheet. Returns each rule's ID, ranges (A1 notation), and one canonical rule payload.

#### Input Parameters

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

### List contact activities

**Slug:** `AMBIGUOUS_MCP_LIST_CONTACT_ACTIVITIES`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `type` | string ("note" | "call" | "email" | "meeting" | "task" | "chat") | No | Activity timeline event type. Used for filtering and badges in the UI. |
| `limit` | integer | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List contact group members

**Slug:** `AMBIGUOUS_MCP_LIST_CONTACT_GROUP_MEMBERS`

List all contacts that are members of a contact group. Returns the contact id, name, email, and type for each member.

#### Input Parameters

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

### List contact groups

**Slug:** `AMBIGUOUS_MCP_LIST_CONTACT_GROUPS`

List all contact groups in the workspace with their member counts. Groups are named collections for organizing contacts (e.g., 'Conference leads 2026').

#### Input Parameters

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

### List contacts

**Slug:** `AMBIGUOUS_MCP_LIST_CONTACTS`

List 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

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

### List crm activities

**Slug:** `AMBIGUOUS_MCP_LIST_CRM_ACTIVITIES`

List recent CRM activity visible to the current user across contact and deal timelines.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `type` | string ("note" | "call" | "email" | "meeting" | "task" | "chat") | No | Activity timeline event type. Used for filtering and badges in the UI. |
| `limit` | integer | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List crm property definitions

**Slug:** `AMBIGUOUS_MCP_LIST_CRM_PROPERTY_DEFINITIONS`

List 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

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

### List crm views

**Slug:** `AMBIGUOUS_MCP_LIST_CRM_VIEWS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `entity_type` | string ("contacts" | "companies" | "deals") | No | Which list page the saved view applies to. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List crm workspace users

**Slug:** `AMBIGUOUS_MCP_LIST_CRM_WORKSPACE_USERS`

List 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

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

### List custom emojis

**Slug:** `AMBIGUOUS_MCP_LIST_CUSTOM_EMOJIS`

List 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

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

### List data connector run history

**Slug:** `AMBIGUOUS_MCP_LIST_DATA_CONNECTOR_RUN_HISTORY`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `limit` | string | No | Page size, integer 1–100 (default 20). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `connector_id` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List data connectors

**Slug:** `AMBIGUOUS_MCP_LIST_DATA_CONNECTORS`

List data connectors registered on a sheet. Connectors fetch data from external sources (URL, CSV, etc.) into specific cells.

#### Input Parameters

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

### List deal line items

**Slug:** `AMBIGUOUS_MCP_LIST_DEAL_LINE_ITEMS`

List all line items for a deal, plus the computed total.

#### Input Parameters

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

### List deals

**Slug:** `AMBIGUOUS_MCP_LIST_DEALS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Free-text search across deal titles. |
| `embed` | string | No | Comma-separated embed fields. Supported: line_items. |
| `limit` | integer | No |  |
| `cursor` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `status` | string ("open" | "won" | "lost") | No | Lifecycle of a deal. `won` and `lost` close the deal; `lost` requires a `lost_reason`. |
| `owner_id` | string | No |  |
| `stage_id` | string | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `pipeline_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List deal templates

**Slug:** `AMBIGUOUS_MCP_LIST_DEAL_TEMPLATES`

List deal templates in the workspace (reusable deal presets: default pipeline, stage, amount, probability, and line items).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search by name or SKU. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `active_only` | boolean | No | Hide products where `active=false` when true. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List documents

**Slug:** `AMBIGUOUS_MCP_LIST_DOCUMENTS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `type` | string ("doc" | "sheet" | "slide" | "canvas") | No | Filter by document type. |
| `limit` | integer | No | 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. |
| `scope` | string ("account" | "workspace") | No | Account-wide by default. `workspace` lists only resources in the authenticated current workspace; grants and resource access remain unchanged. |
| `cursor` | string | No | Opaque cursor from a prior `next_cursor`. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No | Rows to skip. Clamped server-side to the `paginationOffsetMax` platform limit; page deeper with `cursor`, which walks the whole set at constant cost. |
| `starred` | string ("true" | "false") | No | Pass 'true' to return only starred documents. |
| `max_results` | integer | No | Alias for `limit`; clamped the same way. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List drafts

**Slug:** `AMBIGUOUS_MCP_LIST_DRAFTS`

List the unsent draft emails in this mailbox.

#### Input Parameters

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

### List drive folders

**Slug:** `AMBIGUOUS_MCP_LIST_DRIVE_FOLDERS`

List 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

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

### List email attachments

**Slug:** `AMBIGUOUS_MCP_LIST_EMAIL_ATTACHMENTS`

List attachments for an email

#### Input Parameters

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

### List enrollment events

**Slug:** `AMBIGUOUS_MCP_LIST_ENROLLMENT_EVENTS`

Get 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

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

### List event resources

**Slug:** `AMBIGUOUS_MCP_LIST_EVENT_RESOURCES`

List resources currently booked for an event (rooms, equipment).

#### Input Parameters

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

### List events

**Slug:** `AMBIGUOUS_MCP_LIST_EVENTS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No |  |
| `end` | string | No |  |
| `limit` | integer | No |  |
| `start` | string | No |  |
| `cursor` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `orderBy` | string | No |  |
| `timeZone` | string | No |  |
| `eventTypes` | string | No |  |
| `updatedMin` | string | No |  |
| `calendar_id` | string | No |  |
| `showDeleted` | string | No |  |
| `maxAttendees` | string | No |  |
| `singleEvents` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List feedback

**Slug:** `AMBIGUOUS_MCP_LIST_FEEDBACK`

List the caller's own submissions, newest first, as public projections (see `get_feedback`). Paginated with `limit` (default 50) and `offset`.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No | Page size (default 50, capped at the platform pagination max). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Rows to skip (default 0). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List files

**Slug:** `AMBIGUOUS_MCP_LIST_FILES`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | 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. |
| `kind` | string ("folders" | "documents" | "spreadsheets" | "presentations" | "forms" | "images" | "pdf") | No | 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. |
| `sort` | string ("name" | "owner" | "modified" | "last_opened" | "created" | "size") | No | 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. |
| `type` | string | No | Legacy search-only kind filter: folders, documents, images, videos, audio or archives. Ignored without `q`; prefer `kind`. |
| `limit` | string | No | Page size. |
| `order` | string ("asc" | "desc") | No | Direction of `sort`. Defaults to `desc` for `modified`, otherwise `asc` for `name` and `owner` and `desc` for the rest. |
| `cursor` | string | No | Opaque continuation token from `next_cursor`. Only returned for the default order (`modified`, newest first). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Number of items to skip; use with any order or filter, following `has_more`. |
| `section` | string | No | `trash` lists trashed items instead of a folder. |
| `added_by` | string ("agents") | No | `agents`: only items an agent added (the item's owner is an agent identity). |
| `location` | string ("my_drive" | "shared_with_me" | "shared_drives") | No | 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. |
| `owner_id` | string | No | Only items owned by this user. |
| `in_folder` | string | No | Search only: the folder to search inside, including its subfolders. A folder the caller cannot view answers 404. |
| `parent_id` | string | No |  |
| `folders_first` | string ("true" | "false") | No | `true` (default) lists folders before files. `false` orders folders and files together by `sort`; keyset cursors are then not returned, so page with `offset`. |
| `modified_after` | string | No | Only items modified at or after this instant (ISO 8601). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List folder children

**Slug:** `AMBIGUOUS_MCP_LIST_FOLDER_CHILDREN`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `kind` | string ("folders" | "documents" | "spreadsheets" | "presentations" | "forms" | "images" | "pdf") | No | 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. |
| `sort` | string ("name" | "owner" | "modified" | "last_opened" | "created" | "size") | No | 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. |
| `limit` | string | No | Page size. |
| `order` | string ("asc" | "desc") | No | Direction of `sort`. Defaults to `desc` for `modified`, otherwise `asc` for `name` and `owner` and `desc` for the rest. |
| `cursor` | string | No | Opaque continuation token from `next_cursor`. Only returned for the default order (`modified`, newest first). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Number of items to skip; use with any order or filter, following `has_more`. |
| `added_by` | string ("agents") | No | `agents`: only items an agent added (the item's owner is an agent identity). |
| `owner_id` | string | No | Only items owned by this user. |
| `folders_first` | string ("true" | "false") | No | `true` (default) lists folders before files. `false` orders folders and files together by `sort`; keyset cursors are then not returned, so page with `offset`. |
| `modified_after` | string | No | Only items modified at or after this instant (ISO 8601). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List form responses

**Slug:** `AMBIGUOUS_MCP_LIST_FORM_RESPONSES`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `limit` | string | No |  |
| `value` | string | No | Required when `field_id` is set (legacy single-filter). |
| `cursor` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No |  |
| `filters` | string | No | URL-encoded JSON array of {field_id, op, value} objects. Operators: contains, equals, is_empty, is_not_empty. Multiple filters AND together. |
| `field_id` | string | No | Filter by exact value of a specific field (legacy single-filter). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `submitted_after` | string | No | ISO 8601 timestamp; only responses submitted after this. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List forms

**Slug:** `AMBIGUOUS_MCP_LIST_FORMS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search filter on title/description. |
| `limit` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No |  |
| `starred` | string ("true" | "false") | No | 'true' to list only the forms you starred. |
| `is_published` | string ("true" | "false") | No | 'true' or 'false' to filter by publish state. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List form variants

**Slug:** `AMBIGUOUS_MCP_LIST_FORM_VARIANTS`

List 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

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

### List forwarding addresses

**Slug:** `AMBIGUOUS_MCP_LIST_FORWARDING_ADDRESSES`

List forwarding addresses + recent log.

#### Input Parameters

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

### List identity api keys

**Slug:** `AMBIGUOUS_MCP_LIST_IDENTITY_API_KEYS`

List 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

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

### List inbox

**Slug:** `AMBIGUOUS_MCP_LIST_INBOX`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No |  |
| `cursor` | string | No | Opaque cursor from a prior `next_cursor`. |
| `detail` | string ("full" | "headers" | "minimal") | No | Response shape: `full` (default), `headers` (envelope only), `minimal` (id + labels). |
| `fields` | string | No |  |
| `folder` | string ("inbox" | "sent" | "drafts" | "starred" | "snoozed" | "scheduled") | No | `inbox` (default) &#124; `sent` &#124; `drafts` &#124; `starred` &#124; `snoozed` &#124; `scheduled`. |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `unread` | string | No |  |
| `assigned` | string ("me" | "unassigned") | No | 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`. |
| `threaded` | string | No | Default true; pass `false` to flatten. |
| `label_ids` | string | No | Comma-separated label UUIDs (AND semantics). |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List mail approvals

**Slug:** `AMBIGUOUS_MCP_LIST_MAIL_APPROVALS`

List 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

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

### List mail by label

**Slug:** `AMBIGUOUS_MCP_LIST_MAIL_BY_LABEL`

List emails with a specific label

#### Input Parameters

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

### List mail labels

**Slug:** `AMBIGUOUS_MCP_LIST_MAIL_LABELS`

List every mail label in this mailbox.

#### Input Parameters

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

### List mail rules

**Slug:** `AMBIGUOUS_MCP_LIST_MAIL_RULES`

List mail rules / filters.

#### Input Parameters

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

### List mail templates

**Slug:** `AMBIGUOUS_MCP_LIST_MAIL_TEMPLATES`

List the saved mail templates in this mailbox.

#### Input Parameters

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

### List muted threads

**Slug:** `AMBIGUOUS_MCP_LIST_MUTED_THREADS`

List muted threads (inbox view for muted conversations)

#### Input Parameters

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

### List my teams

**Slug:** `AMBIGUOUS_MCP_LIST_MY_TEAMS`

List 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

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

### List my workspaces

**Slug:** `AMBIGUOUS_MCP_LIST_MY_WORKSPACES`

List workspaces the current user belongs to (human users may have multiple). Returns workspace id, name, slug, role, and which one is active.

#### Input Parameters

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

### List named ranges

**Slug:** `AMBIGUOUS_MCP_LIST_NAMED_RANGES`

List 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

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

### List pinned messages

**Slug:** `AMBIGUOUS_MCP_LIST_PINNED_MESSAGES`

List 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

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

### List pipeline members

**Slug:** `AMBIGUOUS_MCP_LIST_PIPELINE_MEMBERS`

List 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

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

### List pipelines

**Slug:** `AMBIGUOUS_MCP_LIST_PIPELINES`

List 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

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

### List pivot tables

**Slug:** `AMBIGUOUS_MCP_LIST_PIVOT_TABLES`

List every pivot table across every tab of the sheet. Each entry is annotated with the `tab` name it lives in.

#### Input Parameters

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

### List products

**Slug:** `AMBIGUOUS_MCP_LIST_PRODUCTS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search by name or SKU. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `active_only` | boolean | No | Hide products where `active=false` when true. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List projects

**Slug:** `AMBIGUOUS_MCP_LIST_PROJECTS`

List 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

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

### List project updates

**Slug:** `AMBIGUOUS_MCP_LIST_PROJECT_UPDATES`

List status updates for a project, newest first. Returns the health timeline with author and timestamp.

#### Input Parameters

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

### List protected ranges

**Slug:** `AMBIGUOUS_MCP_LIST_PROTECTED_RANGES`

List all protected ranges on a spreadsheet. Returns each range with its ID, A1 range, description, warningOnly flag, and editorUserIds allowlist.

#### Input Parameters

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

### List quotes

**Slug:** `AMBIGUOUS_MCP_LIST_QUOTES`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `status` | string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired") | No | Quote lifecycle. `accepted`/`rejected` are terminal; `viewed` is recorded by the open-tracking pixel. |
| `deal_id` | string | No |  |
| `contact_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List resource comments

**Slug:** `AMBIGUOUS_MCP_LIST_RESOURCE_COMMENTS`

Read 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

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

### List resources

**Slug:** `AMBIGUOUS_MCP_LIST_RESOURCES`

List bookable resources (rooms, equipment) in the workspace. Call before booking a room to see what's available.

#### Input Parameters

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

### List roles

**Slug:** `AMBIGUOUS_MCP_LIST_ROLES`

List all roles in the workspace (system roles + custom roles). Requires admin role.

#### Input Parameters

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

### List running executions

**Slug:** `AMBIGUOUS_MCP_LIST_RUNNING_EXECUTIONS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No |  |
| `since` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `status` | string | No |  |
| `surface` | string ("chat" | "mention" | "mail" | "tasks" | "documents") | No |  |
| `coworker_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### List saved messages

**Slug:** `AMBIGUOUS_MCP_LIST_SAVED_MESSAGES`

List 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

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

### List scheduled mail

**Slug:** `AMBIGUOUS_MCP_LIST_SCHEDULED_MAIL`

List scheduled (unsent) emails

#### Input Parameters

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

### List scheduled messages

**Slug:** `AMBIGUOUS_MCP_LIST_SCHEDULED_MESSAGES`

List 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

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

### List scheduler bookings

**Slug:** `AMBIGUOUS_MCP_LIST_SCHEDULER_BOOKINGS`

List all bookings (across all scheduler links) owned by the current user. Useful for summarizing the user's upcoming meetings.

#### Input Parameters

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

### List scheduler link bookings

**Slug:** `AMBIGUOUS_MCP_LIST_SCHEDULER_LINK_BOOKINGS`

List all bookings for a single scheduler link (owner-scoped).

#### Input Parameters

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

### List scheduler links

**Slug:** `AMBIGUOUS_MCP_LIST_SCHEDULER_LINKS`

List the user's scheduler links (Calendly-style booking pages). Each link has a shareable slug, duration, availability hours, and optionally auto-creates a contact + deal when booked.

#### Input Parameters

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

### List scorable fields

**Slug:** `AMBIGUOUS_MCP_LIST_SCORABLE_FIELDS`

List 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

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

### List scoring rules

**Slug:** `AMBIGUOUS_MCP_LIST_SCORING_RULES`

List all lead scoring rules for the workspace.

#### Input Parameters

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

### List send as addresses

**Slug:** `AMBIGUOUS_MCP_LIST_SEND_AS_ADDRESSES`

List available send-as addresses for current user

#### Input Parameters

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

### List sent mail

**Slug:** `AMBIGUOUS_MCP_LIST_SENT_MAIL`

List the emails sent from this mailbox.

#### Input Parameters

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

### List sequence enrollments

**Slug:** `AMBIGUOUS_MCP_LIST_SEQUENCE_ENROLLMENTS`

List 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

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

### List sequences

**Slug:** `AMBIGUOUS_MCP_LIST_SEQUENCES`

List all CRM email/task sequences (multi-step automated outreach campaigns). Returns sequences with their steps, active status, and current enrollment count.

#### Input Parameters

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

### List shared drive files

**Slug:** `AMBIGUOUS_MCP_LIST_SHARED_DRIVE_FILES`

List files in a shared drive.

#### Input Parameters

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

### List shared drive members

**Slug:** `AMBIGUOUS_MCP_LIST_SHARED_DRIVE_MEMBERS`

List shared drive members.

#### Input Parameters

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

### List shared drives

**Slug:** `AMBIGUOUS_MCP_LIST_SHARED_DRIVES`

List shared drives user is a member of.

#### Input Parameters

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

### List sheet images

**Slug:** `AMBIGUOUS_MCP_LIST_SHEET_IMAGES`

List editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

#### Input Parameters

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

### List sheet picture groups

**Slug:** `AMBIGUOUS_MCP_LIST_SHEET_PICTURE_GROUPS`

List 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

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

### List sheets

**Slug:** `AMBIGUOUS_MCP_LIST_SHEETS`

List 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

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

### List sheet shapes

**Slug:** `AMBIGUOUS_MCP_LIST_SHEET_SHAPES`

List editable floating shapes with editable text, cell anchors and CSS pixel geometry.

#### Input Parameters

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

### List sheet validations

**Slug:** `AMBIGUOUS_MCP_LIST_SHEET_VALIDATIONS`

List all data validation rules on a spreadsheet. Returns each rule's range (A1 notation) and rule definition (type, values, strict, inputMessage).

#### Input Parameters

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

### List sign documents

**Slug:** `AMBIGUOUS_MCP_LIST_SIGN_DOCUMENTS`

List signing documents in the workspace.

#### Input Parameters

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

### List sign templates

**Slug:** `AMBIGUOUS_MCP_LIST_SIGN_TEMPLATES`

List reusable signing templates.

#### Input Parameters

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

### List slicers

**Slug:** `AMBIGUOUS_MCP_LIST_SLICERS`

List 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

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

### List slide masters

**Slug:** `AMBIGUOUS_MCP_LIST_SLIDE_MASTERS`

List 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

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

### List snoozed mail

**Slug:** `AMBIGUOUS_MCP_LIST_SNOOZED_MAIL`

List the snoozed emails in this mailbox.

#### Input Parameters

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

### List starred mail

**Slug:** `AMBIGUOUS_MCP_LIST_STARRED_MAIL`

List the starred emails in this mailbox.

#### Input Parameters

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

### List task attachments

**Slug:** `AMBIGUOUS_MCP_LIST_TASK_ATTACHMENTS`

List Drive files attached to a task.

#### Input Parameters

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

### List tasks

**Slug:** `AMBIGUOUS_MCP_LIST_TASKS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Free-text search across title + description. |
| `sort` | string ("updated_at" | "sort_order" | "created_at" | "due_date" | "priority") | No | 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. |
| `limit` | integer | No | Page size. Values above the platform pagination maximum are clamped server-side. |
| `cursor` | string | No | Opaque cursor from a prior `next_cursor`. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No | Offset-based pagination fallback. |
| `status` | string | No | Filter by system status. Comma-separated for multi-select. |
| `deal_id` | string | No | Filter to tasks linked to this CRM deal. |
| `cycle_id` | string | No | Filter by cycle ID. `none` returns tasks with no cycle. |
| `label_id` | string | No | Filter by a single label ID (must be a UUID). |
| `priority` | string | No |  |
| `coworkers` | string | No | Pass 'true' to filter to tasks assigned to AI coworkers in the caller's workspace. |
| `label_ids` | string | No | Comma-separated label IDs (AND match). |
| `untriaged` | string ("true" | "false") | No | Pass 'true' to filter to tasks with no project_id. |
| `contact_id` | string | No | Filter to tasks linked to this CRM contact. |
| `creator_id` | string | No | Filter by creator user ID. |
| `crm_linked` | string ("true" | "false") | No | Pass 'true' to return tasks linked to a CRM contact or deal. |
| `project_id` | string | No |  |
| `subscribed` | string | No | Pass 'me' to filter to tasks the caller is subscribed to. |
| `assignee_id` | string | No | Filter to tasks assigned to this user. `unassigned` to filter to unassigned. |
| `max_results` | integer | No | Alias for `limit`. |
| `updated_min` | string | No | ISO 8601 lower bound on `updated_at`. |
| `due_date_end` | string | No | YYYY-MM-DD upper bound (inclusive). |
| `has_due_date` | string ("true" | "false") | No | Pass 'true' to filter to tasks with a due date set. |
| `hide_blocked` | string ("true" | "false") | No | Pass 'true' to filter out tasks blocked via task_relations. |
| `any_label_ids` | string | No | Comma-separated label IDs (OR match). |
| `cancelled_max` | string | No | Exclusive ISO 8601 upper bound on `cancelled_at`. |
| `cancelled_min` | string | No | Inclusive ISO 8601 lower bound on `cancelled_at`. |
| `completed_max` | string | No | ISO 8601 upper bound on `completed_at`. |
| `completed_min` | string | No | ISO 8601 lower bound on `completed_at`. |
| `show_archived` | string ("true" | "false") | No | Pass 'true' to include archived tasks (default: hidden). |
| `start_date_to` | string | No |  |
| `due_date_start` | string | No | YYYY-MM-DD lower bound (inclusive). |
| `parent_task_id` | string | No | Filter by parent task ID. Special value `null` (string) returns top-level tasks only. |
| `task_status_id` | string | No | Filter by custom status ID. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `start_date_from` | string | No |  |
| `managed_coworkers` | string | No | Pass 'true' to filter to tasks assigned to AI coworkers managed by the caller. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `exclude_task_status_ids` | string | No | Comma-separated custom status IDs to exclude. |

### List task templates

**Slug:** `AMBIGUOUS_MCP_LIST_TASK_TEMPLATES`

List 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

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

### List teams

**Slug:** `AMBIGUOUS_MCP_LIST_TEAMS`

List 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

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

### List trashed files

**Slug:** `AMBIGUOUS_MCP_LIST_TRASHED_FILES`

Find 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

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

### List users

**Slug:** `AMBIGUOUS_MCP_LIST_USERS`

List workspace members and agents with identity, role, status, storage usage, and timestamps. Requires admin or owner.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Free-text search across display name + email. |
| `role` | string | No | Filter by role name. |
| `type` | string | No | Filter by user type (`human` &#124; `agent`). |
| `limit` | integer | No | Page size (default 50, max 500). |
| `cursor` | string | No | Opaque pagination cursor (preferred over offset). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No | Offset for legacy pagination (must be ≥ 0). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `include_coworker_config` | boolean | No | 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. |

### List user statuses

**Slug:** `AMBIGUOUS_MCP_LIST_USER_STATUSES`

List 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

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

### List wiki page databases

**Slug:** `AMBIGUOUS_MCP_LIST_WIKI_PAGE_DATABASES`

List all inline databases hosted on a wiki page.

#### Input Parameters

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

### List wiki page versions

**Slug:** `AMBIGUOUS_MCP_LIST_WIKI_PAGE_VERSIONS`

List 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

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

### List wiki space pages

**Slug:** `AMBIGUOUS_MCP_LIST_WIKI_SPACE_PAGES`

List 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

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

### List wiki spaces

**Slug:** `AMBIGUOUS_MCP_LIST_WIKI_SPACES`

List 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

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

### List wiki synced blocks by page

**Slug:** `AMBIGUOUS_MCP_LIST_WIKI_SYNCED_BLOCKS_BY_PAGE`

List 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

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

### Log activity

**Slug:** `AMBIGUOUS_MCP_LOG_ACTIVITY`

Log 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

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

### Mail alias create

**Slug:** `AMBIGUOUS_MCP_MAIL_ALIAS_CREATE`

Add a new alias on a verified workspace domain

#### Input Parameters

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

### Mail alias delete

**Slug:** `AMBIGUOUS_MCP_MAIL_ALIAS_DELETE`

Delete a send-from alias address by id.

#### Input Parameters

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

### Mail aliases list

**Slug:** `AMBIGUOUS_MCP_MAIL_ALIASES_LIST`

List all aliases for current user's mailbox

#### Input Parameters

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

### Mail alias set default

**Slug:** `AMBIGUOUS_MCP_MAIL_ALIAS_SET_DEFAULT`

Set alias as default send-as identity

#### Input Parameters

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

### Mail blocklist clear

**Slug:** `AMBIGUOUS_MCP_MAIL_BLOCKLIST_CLEAR`

Unblock by raw pattern (convenience for "Unblock sender" button)

#### Input Parameters

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

### Mail blocklist remove

**Slug:** `AMBIGUOUS_MCP_MAIL_BLOCKLIST_REMOVE`

Unblock a sender by their blocklist entry id.

#### Input Parameters

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

### Mail bulk modify

**Slug:** `AMBIGUOUS_MCP_MAIL_BULK_MODIFY`

Apply one bulk action to emails chosen by id or search query.

#### Input Parameters

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

### Mail export eml

**Slug:** `AMBIGUOUS_MCP_MAIL_EXPORT_EML`

Export a message as RFC 5322 EML, returning retained source octets when available.

#### Input Parameters

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

### Mail external auth url

**Slug:** `AMBIGUOUS_MCP_MAIL_EXTERNAL_AUTH_URL`

Start connected-mailbox (Gmail) OAuth — returns the consent URL.

#### Input Parameters

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

### Mail external connection delete

**Slug:** `AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTION_DELETE`

Disconnect a connected mailbox.

#### Input Parameters

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

### Mail external connections list

**Slug:** `AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTIONS_LIST`

List connected mailboxes.

#### Input Parameters

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

### Mail external connection test

**Slug:** `AMBIGUOUS_MCP_MAIL_EXTERNAL_CONNECTION_TEST`

Verify a connected mailbox by fetching its Gmail profile.

#### Input Parameters

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

### Mail folder counts

**Slug:** `AMBIGUOUS_MCP_MAIL_FOLDER_COUNTS`

Per-folder badge counts for sidebar Returns { inbox: unread_count, drafts, scheduled, snoozed } — Gmail-style.

#### Input Parameters

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

### Mail label counts

**Slug:** `AMBIGUOUS_MCP_MAIL_LABEL_COUNTS`

Per-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

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

### Mail message unsubscribe

**Slug:** `AMBIGUOUS_MCP_MAIL_MESSAGE_UNSUBSCRIBE`

One-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

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

### Mail shared mailbox assignees

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_ASSIGNEES`

The people who can hold a thread in this shared mailbox — team grants flattened to their members.

#### Input Parameters

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

### Mail shared mailbox create

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_CREATE`

Create a shared mailbox and address it on a workspace domain (admin only)

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `local_part` | string | Yes | Local part of the mailbox address, e.g. `support`. |
| `display_name` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `workspace_domain_id` | string | No | Domain to address the mailbox on. Defaults to the workspace domain. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Mail shared mailbox delete

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_DELETE`

Retire a shared mailbox (admin only). Soft: stored mail is retained and the address stays reserved.

#### Input Parameters

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

### Mail shared mailboxes list

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOXES_LIST`

List the shared mailboxes the caller holds, or every one in the workspace with `scope=managed` (admin only)

#### Input Parameters

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

### Mail shared mailbox get

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_GET`

Get one shared mailbox and its members

#### Input Parameters

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

### Mail shared mailbox member add

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_MEMBER_ADD`

Grant a user or a team access to a shared mailbox (admin only)

#### Input Parameters

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

### Mail shared mailbox member remove

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_MEMBER_REMOVE`

Revoke a user's or team's access to a shared mailbox (admin only)

#### Input Parameters

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

### Mail shared mailbox restore

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_RESTORE`

Restore a retired shared mailbox (admin only). Total — delete cascaded nothing.

#### Input Parameters

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

### Mail shared mailbox update

**Slug:** `AMBIGUOUS_MCP_MAIL_SHARED_MAILBOX_UPDATE`

Rename a shared mailbox's display name; its address is unchanged (admin only)

#### Input Parameters

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

### Mail smart compose

**Slug:** `AMBIGUOUS_MCP_MAIL_SMART_COMPOSE`

Suggest 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `prefix` | string | Yes | The draft so far — the email text already typed, which the suggestion continues. |
| `subject` | string | No | The draft's subject line. |
| `thread_context` | string | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Mail thread mute status

**Slug:** `AMBIGUOUS_MCP_MAIL_THREAD_MUTE_STATUS`

Check if a thread is muted

#### Input Parameters

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

### Mail trash list

**Slug:** `AMBIGUOUS_MCP_MAIL_TRASH_LIST`

List trashed (soft-deleted) emails — the caller's own rows in folder='trash'. Restore one with `untrash_email`; nothing is purged automatically.

#### Input Parameters

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

### Mail unread summary

**Slug:** `AMBIGUOUS_MCP_MAIL_UNREAD_SUMMARY`

Unread 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

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

### Mark all channels read

**Slug:** `AMBIGUOUS_MCP_MARK_ALL_CHANNELS_READ`

Mark 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

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

### Mark channel read

**Slug:** `AMBIGUOUS_MCP_MARK_CHANNEL_READ`

Mark 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

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

### Mark channel unread

**Slug:** `AMBIGUOUS_MCP_MARK_CHANNEL_UNREAD`

Mark 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

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

### Mark email read

**Slug:** `AMBIGUOUS_MCP_MARK_EMAIL_READ`

Update email status (read/unread, starred, snoozed)

#### Input Parameters

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

### Mark thread read

**Slug:** `AMBIGUOUS_MCP_MARK_THREAD_READ`

Mark 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Mark thread unread

**Slug:** `AMBIGUOUS_MCP_MARK_THREAD_UNREAD`

Mark 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Merge contacts

**Slug:** `AMBIGUOUS_MCP_MERGE_CONTACTS`

Merge 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

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

### Migrate document source

**Slug:** `AMBIGUOUS_MCP_MIGRATE_DOCUMENT_SOURCE`

Activate 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

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

### Modify contact group members

**Slug:** `AMBIGUOUS_MCP_MODIFY_CONTACT_GROUP_MEMBERS`

Bulk 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

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

### Move sheet column

**Slug:** `AMBIGUOUS_MCP_MOVE_SHEET_COLUMN`

Move 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

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

### Move sheet row

**Slug:** `AMBIGUOUS_MCP_MOVE_SHEET_ROW`

Move a row to a new zero-based position, carrying its values, formatting, geometry and dependent references.

#### Input Parameters

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

### Notifications dismiss

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_DISMISS`

Soft-delete (hide from default feed). Preserved for audit / undismiss.

#### Input Parameters

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

### Notifications list

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | string | No |  |
| `order` | string ("asc" | "desc") | No | Creation order; defaults to newest first. A cursor carries its own order. |
| `cursor` | string | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No |  |
| `event_types` | string | No | Comma-separated event types to include. |
| `unread_only` | string | No |  |
| `resource_types` | string | No | Comma-separated resource types to include. |
| `include_snoozed` | string ("true" | "false") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `include_dismissed` | string ("true" | "false") | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `excluded_resource_types` | string | No | Comma-separated resource types to exclude. |

### Notifications mark all read

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MARK_ALL_READ`

Mark every unread notification in the optional resource/event scope as read.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `fields` | string | No |  |
| `notify` | string | No |  |
| `event_types` | string | No | Comma-separated event types to mark read. |
| `resource_types` | string | No | Comma-separated resource types to mark read. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `excluded_resource_types` | string | No | Comma-separated resource types to exclude. |

### Notifications mark read

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MARK_READ`

Mark 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

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

### Notifications mark unread

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MARK_UNREAD`

Convenience alias for `PATCH /api/notifications/:id` with `{read:false}`.

#### Input Parameters

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

### Notifications mute create

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MUTE_CREATE`

Create 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

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

### Notifications mute delete

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MUTE_DELETE`

Remove a mute rule by id. Scoped to the owning user.

#### Input Parameters

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

### Notifications mutes list

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_MUTES_LIST`

List active mute rules. Pass `?include_expired=true` to also see rules whose `until` has passed (these no longer suppress notifications).

#### Input Parameters

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

### Notifications snooze

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_SNOOZE`

Hide until `{until: ISO8601}`. Pass `{until: null}` to clear snooze.

#### Input Parameters

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

### Notifications undismiss

**Slug:** `AMBIGUOUS_MCP_NOTIFICATIONS_UNDISMISS`

Restore a dismissed notification.

#### Input Parameters

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

### Patch canvas element

**Slug:** `AMBIGUOUS_MCP_PATCH_CANVAS_ELEMENT`

Update 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

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

### Patch users notification preferences

**Slug:** `AMBIGUOUS_MCP_PATCH_USERS_NOTIFICATION_PREFERENCES`

Partial update of notification preferences. Unknown keys → 400. Non-boolean values → 400.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `email_on_mention` | boolean | No | Send email when this user is @mentioned in a comment or message. Default: true. |
| `email_on_deal_won` | boolean | No | Send email when a deal owned by this user is marked won. Default: true. |
| `email_on_deal_lost` | boolean | No | Send email when a deal owned by this user is marked lost. Default: true. |
| `email_on_comment_added` | boolean | No | Send transactional email when someone comments on a doc/task/etc. owned by this user. Default: true. |
| `email_on_task_assigned` | boolean | No | Send email when a task is assigned to this user. Default: true. |
| `tab_title_unread_count` | boolean | No | Client-only UX cue. Update the tab title with `(N) Ambiguous` when the tab has unread notifications. Default: false. |
| `email_on_document_shared` | boolean | No | Send email when a document, sheet, slide, wiki page, file, or calendar is shared with this user. Default: true. |
| `sound_on_new_notification` | boolean | No | Client-only UX cue. Play a chime when a new notification arrives in this browser tab. Default: false. |
| `browser_push_on_new_notification` | boolean | No | Client-only UX cue. Show an OS-level browser push notification. Default: false. |

### Pause coworker

**Slug:** `AMBIGUOUS_MCP_PAUSE_COWORKER`

Pause coworker (stops scheduled executions).

#### Input Parameters

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

### Permanent delete file

**Slug:** `AMBIGUOUS_MCP_PERMANENT_DELETE_FILE`

Permanently 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

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

### Poll close

**Slug:** `AMBIGUOUS_MCP_POLL_CLOSE`

Close a poll to further voting (creator or channel admin).

#### Input Parameters

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

### Poll create

**Slug:** `AMBIGUOUS_MCP_POLL_CREATE`

Create a poll in a channel. Creator must be a channel member.

#### Input Parameters

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

### Poll delete

**Slug:** `AMBIGUOUS_MCP_POLL_DELETE`

Delete a poll (creator or channel admin).

#### Input Parameters

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

### Poll get

**Slug:** `AMBIGUOUS_MCP_POLL_GET`

Poll details (question, options, the caller's votes).

#### Input Parameters

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

### Poll get by message

**Slug:** `AMBIGUOUS_MCP_POLL_GET_BY_MESSAGE`

Poll results for the poll attached to a chat message.

#### Input Parameters

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

### Poll results

**Slug:** `AMBIGUOUS_MCP_POLL_RESULTS`

Tallied poll results (respects anonymity).

#### Input Parameters

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

### Poll unvote

**Slug:** `AMBIGUOUS_MCP_POLL_UNVOTE`

Remove the caller's vote for a poll option.

#### Input Parameters

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

### Poll vote

**Slug:** `AMBIGUOUS_MCP_POLL_VOTE`

Cast a vote for a poll option.

#### Input Parameters

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

### Project members add

**Slug:** `AMBIGUOUS_MCP_PROJECT_MEMBERS_ADD`

Add 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

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

### Project members list

**Slug:** `AMBIGUOUS_MCP_PROJECT_MEMBERS_LIST`

List project members.

#### Input Parameters

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

### Project members remove

**Slug:** `AMBIGUOUS_MCP_PROJECT_MEMBERS_REMOVE`

Remove 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

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

### Project members update role

**Slug:** `AMBIGUOUS_MCP_PROJECT_MEMBERS_UPDATE_ROLE`

Change a member's role.

#### Input Parameters

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

### Project notification pref get

**Slug:** `AMBIGUOUS_MCP_PROJECT_NOTIFICATION_PREF_GET`

Get the caller's notification preference for the project.

#### Input Parameters

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

### Project notification pref set

**Slug:** `AMBIGUOUS_MCP_PROJECT_NOTIFICATION_PREF_SET`

Set the caller's notification preference (`level`) for the project.

#### Input Parameters

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

### Project templates apply

**Slug:** `AMBIGUOUS_MCP_PROJECT_TEMPLATES_APPLY`

Create a new project from a template. Pass `{name, description}` in the body.

#### Input Parameters

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

### Project templates create

**Slug:** `AMBIGUOUS_MCP_PROJECT_TEMPLATES_CREATE`

Create a project template.

#### Input Parameters

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

### Project templates delete

**Slug:** `AMBIGUOUS_MCP_PROJECT_TEMPLATES_DELETE`

Delete a project template.

#### Input Parameters

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

### Project templates get

**Slug:** `AMBIGUOUS_MCP_PROJECT_TEMPLATES_GET`

Get a single project template.

#### Input Parameters

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

### Project templates list

**Slug:** `AMBIGUOUS_MCP_PROJECT_TEMPLATES_LIST`

List project templates in the workspace.

#### Input Parameters

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

### Project updates delete

**Slug:** `AMBIGUOUS_MCP_PROJECT_UPDATES_DELETE`

Delete a status update. Author or admin only.

#### Input Parameters

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

### Project updates edit

**Slug:** `AMBIGUOUS_MCP_PROJECT_UPDATES_EDIT`

Edit a status update. Author or admin only.

#### Input Parameters

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

### Protect range

**Slug:** `AMBIGUOUS_MCP_PROTECT_RANGE`

Protect 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

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

### Publish calendar

**Slug:** `AMBIGUOUS_MCP_PUBLISH_CALENDAR`

Publish 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

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

### Publish form

**Slug:** `AMBIGUOUS_MCP_PUBLISH_FORM`

Publish 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

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

### Query wiki database

**Slug:** `AMBIGUOUS_MCP_QUERY_WIKI_DATABASE`

Query rows from an inline database with optional view, filter, and sort. Returns paginated results.

#### Input Parameters

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

### Realtime exchange connection capability

**Slug:** `AMBIGUOUS_MCP_REALTIME_EXCHANGE_CONNECTION_CAPABILITY`

Exchange 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `x-realtime-session-trace-id` | string | No | Optional random session correlation UUID. Presentation-only: never authority, routing input, or durable identity. |

### Realtime exchange resource capability

**Slug:** `AMBIGUOUS_MCP_REALTIME_EXCHANGE_RESOURCE_CAPABILITY`

Exchange 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | 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. |
| `operations` | array | No | 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. |
| `x-realtime-session-trace-id` | string | No | Optional random session correlation UUID. Presentation-only: never authority, routing input, or durable identity. |

### Recalculate lead scores

**Slug:** `AMBIGUOUS_MCP_RECALCULATE_LEAD_SCORES`

Recalculate 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

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

### Register custom domain

**Slug:** `AMBIGUOUS_MCP_REGISTER_CUSTOM_DOMAIN`

Register a custom email domain as a pending row; ownership must be verified via DNS TXT before sending is enabled. Requires admin role.

#### Input Parameters

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

### Remove access

**Slug:** `AMBIGUOUS_MCP_REMOVE_ACCESS`

Remove 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | 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. |
| `link` | string ("true") | No |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `team_id` | string | No | 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. |
| `user_id` | string | No | The specific person's ID, separate from the resource id. On update/removal, use the user ID from that resource's permission entry. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `pending_share_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Remove forwarding address

**Slug:** `AMBIGUOUS_MCP_REMOVE_FORWARDING_ADDRESS`

Remove a forwarding address

#### Input Parameters

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

### Remove pipeline member

**Slug:** `AMBIGUOUS_MCP_REMOVE_PIPELINE_MEMBER`

Remove a user or team from a CRM pipeline. The principalId is the user_id or team_id of the member to remove.

#### Input Parameters

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

### Remove role

**Slug:** `AMBIGUOUS_MCP_REMOVE_ROLE`

Remove a role from a user. Requires admin role.

#### Input Parameters

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

### Remove shared drive member

**Slug:** `AMBIGUOUS_MCP_REMOVE_SHARED_DRIVE_MEMBER`

Remove a shared drive member (manager-only; cannot remove last manager).

#### Input Parameters

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

### Remove sheet column

**Slug:** `AMBIGUOUS_MCP_REMOVE_SHEET_COLUMN`

Remove a column from a sheet tab by column ID. Use `?sheet=` to target a tab other than the first.

#### Input Parameters

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

### Remove sheet tab

**Slug:** `AMBIGUOUS_MCP_REMOVE_SHEET_TAB`

Remove a sheet tab by name. Cannot remove the last remaining tab.

#### Input Parameters

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

### Remove slide

**Slug:** `AMBIGUOUS_MCP_REMOVE_SLIDE`

Remove the slide at the given zero-based index.

#### Input Parameters

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

### Remove task attachment

**Slug:** `AMBIGUOUS_MCP_REMOVE_TASK_ATTACHMENT`

Remove a file attachment from a task. Does not delete the Drive file.

#### Input Parameters

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

### Rename document version

**Slug:** `AMBIGUOUS_MCP_RENAME_DOCUMENT_VERSION`

Rename a version snapshot of a document. Useful for labeling meaningful versions (e.g., "Pre-launch draft", "Board approved"). Requires editor permission.

#### Input Parameters

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

### Rename sheet tab

**Slug:** `AMBIGUOUS_MCP_RENAME_SHEET_TAB`

Rename an existing sheet tab.

#### Input Parameters

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

### Reorder mail labels

**Slug:** `AMBIGUOUS_MCP_REORDER_MAIL_LABELS`

Reorder the mail labels shown in the sidebar.

#### Input Parameters

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

### Reorder mail rules

**Slug:** `AMBIGUOUS_MCP_REORDER_MAIL_RULES`

Reorder the mail rules to change which runs first.

#### Input Parameters

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

### Reorder slides

**Slug:** `AMBIGUOUS_MCP_REORDER_SLIDES`

Reorder 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `order` | array | Yes | New slide order — array of original indices in the desired sequence. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Replace named range content

**Slug:** `AMBIGUOUS_MCP_REPLACE_NAMED_RANGE_CONTENT`

Replace 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | Yes |  |
| `content` | string | Yes | Markdown string OR ProseMirror node / node array. Server normalizes to PM JSON. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Replace shapes with image

**Slug:** `AMBIGUOUS_MCP_REPLACE_SHAPES_WITH_IMAGE`

Replace 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `find` | string | Yes |  |
| `image_url` | string | Yes |  |
| `match_case` | boolean | No |  |
| `replace_method` | string ("CENTER_INSIDE" | "CENTER_CROP") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Replace sheet tab

**Slug:** `AMBIGUOUS_MCP_REPLACE_SHEET_TAB`

Replace a sheet tab's columns and/or rows wholesale. Use for bulk data replacement. Use update_cells for surgical edits.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `rows` | array | No |  |
| `state` | string ("visible" | "hidden" | "veryHidden") | No |  |
| `columns` | array | No |  |
| `tab_name` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Request access

**Slug:** `AMBIGUOUS_MCP_REQUEST_ACCESS`

Ask 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

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

### Reschedule scheduled email

**Slug:** `AMBIGUOUS_MCP_RESCHEDULE_SCHEDULED_EMAIL`

Change the delivery time of a pending scheduled email without changing its content.

#### Input Parameters

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

### Resend forwarding verification

**Slug:** `AMBIGUOUS_MCP_RESEND_FORWARDING_VERIFICATION`

Resend verification email

#### Input Parameters

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

### Restore file

**Slug:** `AMBIGUOUS_MCP_RESTORE_FILE`

Restore 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

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

### Restore sheet structure

**Slug:** `AMBIGUOUS_MCP_RESTORE_SHEET_STRUCTURE`

Undo or redo a structural change receipt without overwriting unrelated later edits.

#### Input Parameters

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

### Restore task

**Slug:** `AMBIGUOUS_MCP_RESTORE_TASK`

Restore a soft-deleted task when the caller has task editor access.

#### Input Parameters

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

### Restore wiki synced block

**Slug:** `AMBIGUOUS_MCP_RESTORE_WIKI_SYNCED_BLOCK`

Restore a previously deleted synced block. Embedding pages will render the block again instead of showing error chips.

#### Input Parameters

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

### Resume coworker

**Slug:** `AMBIGUOUS_MCP_RESUME_COWORKER`

Resume a paused coworker.

#### Input Parameters

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

### Revert wiki page version

**Slug:** `AMBIGUOUS_MCP_REVERT_WIKI_PAGE_VERSION`

Revert 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

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

### Revoke api key

**Slug:** `AMBIGUOUS_MCP_REVOKE_API_KEY`

Revoke an API key. Immediate — any requests using the key will fail. Requires admin role.

#### Input Parameters

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

### Revoke identity api key

**Slug:** `AMBIGUOUS_MCP_REVOKE_IDENTITY_API_KEY`

Revoke (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

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

### Rotate calendar publish url

**Slug:** `AMBIGUOUS_MCP_ROTATE_CALENDAR_PUBLISH_URL`

Rotate a published calendar's read-only subscription URL. The previous URL is revoked immediately.

#### Input Parameters

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

### Rsvp email invite

**Slug:** `AMBIGUOUS_MCP_RSVP_EMAIL_INVITE`

RSVP to a calendar invite on an email.

#### Input Parameters

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

### Rsvp event

**Slug:** `AMBIGUOUS_MCP_RSVP_EVENT`

RSVP 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `rsvp` | string ("accepted" | "declined" | "tentative" | "needs_action") | Yes | RSVP state for an attendee. |
| `comment` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Run data connector

**Slug:** `AMBIGUOUS_MCP_RUN_DATA_CONNECTOR`

Execute 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

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

### Save message

**Slug:** `AMBIGUOUS_MCP_SAVE_MESSAGE`

Bookmark 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Scan business card

**Slug:** `AMBIGUOUS_MCP_SCAN_BUSINESS_CARD`

OCR 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `image` | string | Yes | Base64-encoded image as a `data:` URL (`data:image/png;base64,...`). Capped at ~6MB of raw image data to protect the upstream OCR call. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Search calendar events

**Slug:** `AMBIGUOUS_MCP_SEARCH_CALENDAR_EVENTS`

Full-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

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

### Search chat messages

**Slug:** `AMBIGUOUS_MCP_SEARCH_CHAT_MESSAGES`

Find 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search text. Empty/missing returns no results. |
| `limit` | string | No | Max results (default 25, cap 50). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `channel_id` | string | No | Restrict the search to one channel. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Search mail

**Slug:** `AMBIGUOUS_MCP_SEARCH_MAIL`

Full-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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Operator-syntax query (Gmail-style). |
| `limit` | integer | No |  |
| `detail` | string ("full" | "headers" | "minimal") | No | Response shape: `full` (default), `headers` (envelope only), `minimal` (id + labels). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No |  |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Search palette

**Slug:** `AMBIGUOUS_MCP_SEARCH_PALETTE`

Cross-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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search query string. |
| `limit` | string | No | Max results (capped at 50, default 30). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Search wiki

**Slug:** `AMBIGUOUS_MCP_SEARCH_WIKI`

Case-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

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

### Search workspace

**Slug:** `AMBIGUOUS_MCP_SEARCH_WORKSPACE`

Search 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `is` | array | No | Chat message state. Honored by `messages` alone; every other active module drops out of the result set. |
| `from` | array | No | 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. |
| `sort` | string ("relevant" | "recent") | No | `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. |
| `after` | string | No | Keep only rows created on or after this date (YYYY-MM-DD, UTC). Same creation axis as `before`. |
| `limit` | integer | No |  |
| `query` | string | No | Search query string. |
| `before` | string | No | 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. |
| `offset` | integer | No |  |
| `modules` | array | No | Restrict to specific modules (docs, sheets, slides, tasks, etc). |
| `channels` | array | No | Chat channel names (no leading `#`). Honored by `messages` alone; every other active module drops out of the result set. |
| `has_link` | boolean | No | Restrict to rows that contain a link. |
| `has_attachment` | boolean | No | Restrict to rows that carry an attachment. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Send draft email

**Slug:** `AMBIGUOUS_MCP_SEND_DRAFT_EMAIL`

Send 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

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

### Send email

**Slug:** `AMBIGUOUS_MCP_SEND_EMAIL`

Send 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cc` | array | No |  |
| `to` | array | No | Empty drafts allowed; required when sending. |
| `bcc` | array | No |  |
| `fields` | string | No |  |
| `labels` | array | No |  |
| `notify` | string | No |  |
| `deal_id` | string | No |  |
| `subject` | string | No |  |
| `verbose` | string | No |  |
| `body_html` | string | No | HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text. |
| `body_text` | string | No | Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent. |
| `thread_id` | string | No | Attach the message to an existing thread. |
| `contact_id` | string | No |  |
| `from_email` | string | No | Send-as address (must be a verified alias/domain). |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `references` | array | No |  |
| `attachments` | array | No |  |
| `in_reply_to` | string | No |  |
| `scheduled_at` | string | No | ISO-8601. Defers send. |
| `body_markdown` | string | No | Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send. |
| `scheduled_for` | string | No | Legacy alias for scheduled_at. |
| `attachment_ids` | array | No | Drive file IDs to attach. |
| `Idempotency-Key` | string | No | 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. |
| `idempotency_key` | string | No | Optional retry key. Reusing the same key with the same send request returns the original send. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `archive_thread_id` | string | No | Archive this thread once the reply succeeds. |
| `include_signature` | boolean | No |  |
| `undo_send_seconds` | integer | No |  |
| `request_read_receipt` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Send message

**Slug:** `AMBIGUOUS_MCP_SEND_MESSAGE`

Post 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://<file_id>) in content.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `content` | string | Yes | Markdown body. To attach a file, upload it first (`POST /api/drive/upload-proxy` with `source=chat`), then include `[name](drive://<file_id>)` 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. |
| `parent_id` | string | No | Legacy alias for `thread_id`. |
| `thread_id` | string | No |  |
| `channel_id` | string | Yes |  |
| `thread_key` | string | No | Per-channel idempotency key that stitches a top-level message into an existing thread by key. |
| `scheduled_at` | string | No | 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. |
| `scheduled_for` | string | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `starts_new_block` | boolean | No | Send this message as its own block — it renders its own header even where author + timestamp would group it under the previous message. |
| `broadcast_to_channel` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Send quote

**Slug:** `AMBIGUOUS_MCP_SEND_QUOTE`

Send 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

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

### Send scheduled message now

**Slug:** `AMBIGUOUS_MCP_SEND_SCHEDULED_MESSAGE_NOW`

Deliver 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

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

### Send test notification email

**Slug:** `AMBIGUOUS_MCP_SEND_TEST_NOTIFICATION_EMAIL`

Send a test notification email (useful for checking email rendering and deliverability). Requires admin role.

#### Input Parameters

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

### Set channel archived

**Slug:** `AMBIGUOUS_MCP_SET_CHANNEL_ARCHIVED`

Archive or unarchive a chat channel. Archiving freezes writes for everyone. Requires the same administrative authority as the individual archive and unarchive actions.

#### Input Parameters

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

### Set channel muted

**Slug:** `AMBIGUOUS_MCP_SET_CHANNEL_MUTED`

Mute 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

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

### Set deck fonts

**Slug:** `AMBIGUOUS_MCP_SET_DECK_FONTS`

Set 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `body` | 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") | No | Font for body text — text below 28px, and every table. |
| `heading` | 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") | No | Font for headings and titles — text at 28px or larger. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set default send as

**Slug:** `AMBIGUOUS_MCP_SET_DEFAULT_SEND_AS`

Set the user's default send-as address.

#### Input Parameters

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

### Set docs page layout default

**Slug:** `AMBIGUOUS_MCP_SET_DOCS_PAGE_LAYOUT_DEFAULT`

Set 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

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

### Set document footnotes

**Slug:** `AMBIGUOUS_MCP_SET_DOCUMENT_FOOTNOTES`

Set 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

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

### Set document headers footers

**Slug:** `AMBIGUOUS_MCP_SET_DOCUMENT_HEADERS_FOOTERS`

Set 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

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

### Set email archived

**Slug:** `AMBIGUOUS_MCP_SET_EMAIL_ARCHIVED`

Archive an email or return it to the inbox. archived=true archives; false unarchives. Existing mailbox access rules apply.

#### Input Parameters

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

### Set email signature

**Slug:** `AMBIGUOUS_MCP_SET_EMAIL_SIGNATURE`

Set the workspace default email signature. Pass null (or omit markdown) to clear. Requires admin role.

#### Input Parameters

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

### Set mail signature

**Slug:** `AMBIGUOUS_MCP_SET_MAIL_SIGNATURE`

Set personal email signature. Pass null to clear.

#### Input Parameters

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

### Set mail thread assignee

**Slug:** `AMBIGUOUS_MCP_SET_MAIL_THREAD_ASSIGNEE`

Assign a shared-mailbox conversation to a member, or clear its assignment with user_id=null. Does not change its folder.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `user_id` | string | Yes | A mailbox member's ID, or null to clear the assignment. |
| `mailbox_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set mail thread muted

**Slug:** `AMBIGUOUS_MCP_SET_MAIL_THREAD_MUTED`

Mute 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

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

### Set notification keywords

**Slug:** `AMBIGUOUS_MCP_SET_NOTIFICATION_KEYWORDS`

Replace 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

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

### Set pinned header rows

**Slug:** `AMBIGUOUS_MCP_SET_PINNED_HEADER_ROWS`

Set 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `table_node_index` | integer | Yes | Top-level content index of the target table. |
| `pinned_header_rows` | integer | Yes | Number of header rows to pin. Set to 0 to clear. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set reaction

**Slug:** `AMBIGUOUS_MCP_SET_REACTION`

Add 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

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

### Set read receipts default

**Slug:** `AMBIGUOUS_MCP_SET_READ_RECEIPTS_DEFAULT`

Toggle the default for new compose windows

#### Input Parameters

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

### Set reminder

**Slug:** `AMBIGUOUS_MCP_SET_REMINDER`

Remind 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `remind_at` | string | Yes | 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. |
| `channel_id` | string | Yes | 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. |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set resource starred

**Slug:** `AMBIGUOUS_MCP_SET_RESOURCE_STARRED`

Add 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

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

### Set sheet validation

**Slug:** `AMBIGUOUS_MCP_SET_SHEET_VALIDATION`

Set 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `rule` | object | No | 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. |
| `range` | string | No | A1-style cell range, optionally qualified by a tab name. An unqualified range uses the first tab. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set snooze presets

**Slug:** `AMBIGUOUS_MCP_SET_SNOOZE_PRESETS`

Set the user's custom snooze quick-presets (up to 10). Pass an empty array to reset to defaults.

#### Input Parameters

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

### Set swipe actions

**Slug:** `AMBIGUOUS_MCP_SET_SWIPE_ACTIONS`

Set the caller's own mail-row swipe actions — one action per direction, chosen from archive, trash, read, star, snooze.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `left` | string ("archive" | "trash" | "read" | "star" | "snooze") | Yes | Action bound to one swipe direction on a mail row. |
| `right` | string ("archive" | "trash" | "read" | "star" | "snooze") | Yes | Action bound to one swipe direction on a mail row. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Set task archived

**Slug:** `AMBIGUOUS_MCP_SET_TASK_ARCHIVED`

Archive 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

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

### Set task subscription

**Slug:** `AMBIGUOUS_MCP_SET_TASK_SUBSCRIPTION`

Subscribe 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

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

### Set undo send setting

**Slug:** `AMBIGUOUS_MCP_SET_UNDO_SEND_SETTING`

Set undo-send duration (seconds).

#### Input Parameters

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

### Set user dnd

**Slug:** `AMBIGUOUS_MCP_SET_USER_DND`

Enable 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

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

### Set user status

**Slug:** `AMBIGUOUS_MCP_SET_USER_STATUS`

Set 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

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

### Set vacation settings

**Slug:** `AMBIGUOUS_MCP_SET_VACATION_SETTINGS`

Update vacation auto-reply settings.

#### Input Parameters

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

### Set visibility

**Slug:** `AMBIGUOUS_MCP_SET_VISIBILITY`

Set 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `visibility` | string | No | 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. |
| `linkPassword` | string | No | Empty string or null clears the password; non-empty hashes + stores. |
| `linkExpiresAt` | string | No | ISO 8601 timestamp, or null to clear. |
| `workspaceRole` | string ("viewer" | "commenter" | "editor") | No | 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`. |
| `linkPermission` | string ("viewer" | "commenter" | "editor") | No | 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. |
| `editorsCanShare` | boolean | No | 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`. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Shared with me hide

**Slug:** `AMBIGUOUS_MCP_SHARED_WITH_ME_HIDE`

Hide 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `resource_type` | string ("document" | "file" | "wiki_page" | "form" | "calendar") | Yes | Which Pat8 surface the row is on. `document` covers docs, sheets and slides — they are one table and one permission model. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Shared with me list

**Slug:** `AMBIGUOUS_MCP_SHARED_WITH_ME_LIST`

Everything 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No |  |
| `scope` | string ("account" | "workspace") | No | Account-wide by default. `workspace` lists only resources in the authenticated current workspace; grants and resource access remain unchanged. |
| `cursor` | string | No | Opaque; from a previous page's `next_cursor`. Absent starts at the newest share. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `document_type` | string ("doc" | "sheet" | "slide") | No | 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. |
| `resource_type` | string ("document" | "file" | "wiki_page" | "form" | "calendar") | No | Narrow to one surface. Absent returns all five — the point of the route. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Shared with me undo leave

**Slug:** `AMBIGUOUS_MCP_SHARED_WITH_ME_UNDO_LEAVE`

Undo 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

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

### Sheet get data

**Slug:** `AMBIGUOUS_MCP_SHEET_GET_DATA`

Get 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

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

### Sheet update cells

**Slug:** `AMBIGUOUS_MCP_SHEET_UPDATE_CELLS`

Update 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

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

### Sign add field

**Slug:** `AMBIGUOUS_MCP_SIGN_ADD_FIELD`

Add a signature field to a signing document.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `h` | number | Yes |  |
| `w` | number | Yes |  |
| `x` | number | Yes |  |
| `y` | number | Yes |  |
| `id` | string | Yes |  |
| `page` | integer | Yes |  |
| `type` | string ("signature" | "initial" | "text" | "date" | "checkbox" | "number" | "file") | Yes |  |
| `required` | boolean | No |  |
| `signer_id` | string | Yes |  |
| `default_value` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Sign add signer

**Slug:** `AMBIGUOUS_MCP_SIGN_ADD_SIGNER`

Add 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

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

### Sign get certificate

**Slug:** `AMBIGUOUS_MCP_SIGN_GET_CERTIFICATE`

Download the Certificate of Completion for a completed document.

#### Input Parameters

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

### Sign get references

**Slug:** `AMBIGUOUS_MCP_SIGN_GET_REFERENCES`

List signing documents that use this document as a source.

#### Input Parameters

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

### Sign prepare send

**Slug:** `AMBIGUOUS_MCP_SIGN_PREPARE_SEND`

Validate signers and render the PDF preview (draft → preview_pending).

#### Input Parameters

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

### Sign remove field

**Slug:** `AMBIGUOUS_MCP_SIGN_REMOVE_FIELD`

Remove a field from a signing document.

#### Input Parameters

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

### Sign remove signer

**Slug:** `AMBIGUOUS_MCP_SIGN_REMOVE_SIGNER`

Remove a signer or CC recipient from a draft signing document.

#### Input Parameters

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

### Sign reorder signers

**Slug:** `AMBIGUOUS_MCP_SIGN_REORDER_SIGNERS`

Atomically set the sequential signing order: the full ordered list of the document's signer-role ids. Draft only.

#### Input Parameters

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

### Sign update field

**Slug:** `AMBIGUOUS_MCP_SIGN_UPDATE_FIELD`

Reassign, 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

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

### Sign verify document

**Slug:** `AMBIGUOUS_MCP_SIGN_VERIFY_DOCUMENT`

Verify the integrity and signature of a completed document.

#### Input Parameters

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

### Slide apply template

**Slug:** `AMBIGUOUS_MCP_SLIDE_APPLY_TEMPLATE`

Apply a slide template — built-in or workspace — to the deck or to a single slide.

#### Input Parameters

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

### Slide layouts list

**Slug:** `AMBIGUOUS_MCP_SLIDE_LAYOUTS_LIST`

List the slide-level layouts the editor knows about.

#### Input Parameters

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

### Slide save as template

**Slug:** `AMBIGUOUS_MCP_SLIDE_SAVE_AS_TEMPLATE`

Save 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

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

### Slide star

**Slug:** `AMBIGUOUS_MCP_SLIDE_STAR`

Star a deck. Idempotent — re-starring is a no-op.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |

### Slide stars list

**Slug:** `AMBIGUOUS_MCP_SLIDE_STARS_LIST`

List IDs of slide decks the current user has starred.

#### Input Parameters

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

### Slide templates list

**Slug:** `AMBIGUOUS_MCP_SLIDE_TEMPLATES_LIST`

List the built-in slide deck templates.

#### Input Parameters

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

### Slide unstar

**Slug:** `AMBIGUOUS_MCP_SLIDE_UNSTAR`

Unstar a deck. Idempotent.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |

### Slide use template

**Slug:** `AMBIGUOUS_MCP_SLIDE_USE_TEMPLATE`

Start 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

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

### Snooze email

**Slug:** `AMBIGUOUS_MCP_SNOOZE_EMAIL`

Snooze an email until a datetime.

#### Input Parameters

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

### Snooze reminder

**Slug:** `AMBIGUOUS_MCP_SNOOZE_REMINDER`

Re-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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `remind_at` | string | Yes | 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. |
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Sort sheet

**Slug:** `AMBIGUOUS_MCP_SORT_SHEET`

Sort 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `sheet` | string | No |  |
| `column_id` | string | Yes |  |
| `direction` | string ("asc" | "desc") | Yes |  |
| `filter_range` | object | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Start task timer

**Slug:** `AMBIGUOUS_MCP_START_TASK_TIMER`

Start 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

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

### Stop task timer

**Slug:** `AMBIGUOUS_MCP_STOP_TASK_TIMER`

Stop 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

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

### Submit feedback

**Slug:** `AMBIGUOUS_MCP_SUBMIT_FEEDBACK`

Tell 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No |  |
| `context` | object | No |  |
| `priority` | string | No |  |
| `attachments` | array | No |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `screenshotDataUrl` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Submit form

**Slug:** `AMBIGUOUS_MCP_SUBMIT_FORM`

Submit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | No | Legacy alias for `answers`. Same payload. |
| `slug` | string | Yes |  |
| `answers` | object | No | Canonical wire name. Map of field_id -> respondent value. Either `answers` or `data` (alias) is required; sending both with disagreeing values returns 400. |
| `captcha_token` | string | No | Cloudflare Turnstile token (when captcha_enabled). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `respondent_email` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Task asset create

**Slug:** `AMBIGUOUS_MCP_TASK_ASSET_CREATE`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No | File name to keep with the image; defaults to `image`. |
| `mime_type` | string | No | Declared type. The stored type is decided from the bytes. |
| `source_url` | string | No | 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. |
| `content_base64` | string | No | The image bytes, base64-encoded (no `data:` prefix). |
| `source_file_id` | string | No | Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Task collaborators add

**Slug:** `AMBIGUOUS_MCP_TASK_COLLABORATORS_ADD`

Share 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `user_id` | string | Yes | The workspace member to share this task with. Subscribed on add. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Task collaborators list

**Slug:** `AMBIGUOUS_MCP_TASK_COLLABORATORS_LIST`

List the collaborators on a task — the people holding `editor` on it (and its subtasks) without a role on its project.

#### Input Parameters

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

### Task collaborators remove

**Slug:** `AMBIGUOUS_MCP_TASK_COLLABORATORS_REMOVE`

Revoke a task collaborator's grant. The add-time subscription is left in place — it grants no access on its own.

#### Input Parameters

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

### Tasks activity

**Slug:** `AMBIGUOUS_MCP_TASKS_ACTIVITY`

List audit-log activity entries for a task (status changes, assignments, comments, label edits, etc.). Paginated via `limit`/`offset`.

#### Input Parameters

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

### Tasks batch

**Slug:** `AMBIGUOUS_MCP_TASKS_BATCH`

Batch-fetch up to 50 tasks by ID. Powers LinkedTaskItem hydration in Docs/Wiki.

#### Input Parameters

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

### Tasks by key

**Slug:** `AMBIGUOUS_MCP_TASKS_BY_KEY`

Resolve a workspace-scoped task key (e.g. `WS-123`) to its task ID. Used by deep links and integrations.

#### Input Parameters

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

### Tasks delete

**Slug:** `AMBIGUOUS_MCP_TASKS_DELETE`

Soft-delete a task. Only the creator can delete.

#### Input Parameters

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

### Tasks export

**Slug:** `AMBIGUOUS_MCP_TASKS_EXPORT`

Export 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Free-text search across title + description. |
| `fields` | string | No |  |
| `format` | string | No | 'csv' (default) &#124; 'json'. Validated by handler so the 400 error message is preserved. |
| `notify` | string | No |  |
| `status` | string | No | Filter by system status. Comma-separated for multi-select. |
| `deal_id` | string | No | Filter to tasks linked to this CRM deal. |
| `cycle_id` | string | No | Filter by cycle ID. `none` returns tasks with no cycle. |
| `label_id` | string | No | Filter by a single label ID (must be a UUID). |
| `priority` | string | No |  |
| `coworkers` | string | No | Pass 'true' to filter to tasks assigned to AI coworkers in the caller's workspace. |
| `label_ids` | string | No | Comma-separated label IDs (AND match). |
| `untriaged` | string ("true" | "false") | No | Pass 'true' to filter to tasks with no project_id. |
| `contact_id` | string | No | Filter to tasks linked to this CRM contact. |
| `creator_id` | string | No | Filter by creator user ID. |
| `crm_linked` | string ("true" | "false") | No | Pass 'true' to return tasks linked to a CRM contact or deal. |
| `project_id` | string | No |  |
| `sla_status` | string ("on_track" | "at_risk" | "breached" | "achieved" | "failed" | "not_applicable") | No | Match the worst actionable SLA leg. not_applicable requires a measured neutral leg and no actionable leg. |
| `subscribed` | string | No | Pass 'me' to filter to tasks the caller is subscribed to. |
| `assignee_id` | string | No | Filter to tasks assigned to this user. `unassigned` to filter to unassigned. |
| `updated_min` | string | No | ISO 8601 lower bound on `updated_at`. |
| `due_date_end` | string | No | YYYY-MM-DD upper bound (inclusive). |
| `has_due_date` | string ("true" | "false") | No | Pass 'true' to filter to tasks with a due date set. |
| `hide_blocked` | string ("true" | "false") | No | Pass 'true' to filter out tasks blocked via task_relations. |
| `any_label_ids` | string | No | Comma-separated label IDs (OR match). |
| `cancelled_max` | string | No | Exclusive ISO 8601 upper bound on `cancelled_at`. |
| `cancelled_min` | string | No | Inclusive ISO 8601 lower bound on `cancelled_at`. |
| `completed_max` | string | No | ISO 8601 upper bound on `completed_at`. |
| `completed_min` | string | No | ISO 8601 lower bound on `completed_at`. |
| `show_archived` | string ("true" | "false") | No | Pass 'true' to include archived tasks (default: hidden). |
| `start_date_to` | string | No |  |
| `due_date_start` | string | No | YYYY-MM-DD lower bound (inclusive). |
| `parent_task_id` | string | No | Filter by parent task ID. Special value `null` (string) returns top-level tasks only. |
| `task_status_id` | string | No | Filter by custom status ID. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `start_date_from` | string | No |  |
| `managed_coworkers` | string | No | Pass 'true' to filter to tasks assigned to AI coworkers managed by the caller. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `exclude_task_status_ids` | string | No | Comma-separated custom status IDs to exclude. |

### Tasks favorites add

**Slug:** `AMBIGUOUS_MCP_TASKS_FAVORITES_ADD`

Pin a saved task view or project in your Tasks sidebar. For document, Drive, channel or team favorites, use set_resource_starred.

#### Input Parameters

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

### Tasks favorites list

**Slug:** `AMBIGUOUS_MCP_TASKS_FAVORITES_LIST`

List your Tasks-sidebar pins: saved views and projects, not starred documents, Drive items, channels or teams.

#### Input Parameters

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

### Tasks favorites remove

**Slug:** `AMBIGUOUS_MCP_TASKS_FAVORITES_REMOVE`

Unpin 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

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

### Tasks favorites reorder

**Slug:** `AMBIGUOUS_MCP_TASKS_FAVORITES_REORDER`

Reorder your Tasks-sidebar view/project pins using ordered_ids (favorite-row IDs, top-to-bottom), not resource IDs.

#### Input Parameters

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

### Tasks inbox count

**Slug:** `AMBIGUOUS_MCP_TASKS_INBOX_COUNT`

Count of triage-bucket tasks (untriaged + projects in 'triage' status). Powers the sidebar inbox badge.

#### Input Parameters

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

### Tasks labels assign

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_ASSIGN`

Assign a label to a task. Returns the task's full label list.

#### Input Parameters

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

### Tasks labels create

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_CREATE`

Create a workspace task label. Returns 409 if a label with the same name already exists in the group.

#### Input Parameters

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

### Tasks labels delete

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_DELETE`

Delete a task label. Existing assignments are removed.

#### Input Parameters

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

### Tasks labels list

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_LIST`

List 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

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

### Tasks labels remove

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_REMOVE`

Remove a label assignment from a task. Returns the task's remaining label list.

#### Input Parameters

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

### Tasks labels update

**Slug:** `AMBIGUOUS_MCP_TASKS_LABELS_UPDATE`

Update a task label.

#### Input Parameters

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

### Tasks pr links

**Slug:** `AMBIGUOUS_MCP_TASKS_PR_LINKS`

List GitHub pull requests linked to a task (via the integration-links service).

#### Input Parameters

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

### Tasks relations batch

**Slug:** `AMBIGUOUS_MCP_TASKS_RELATIONS_BATCH`

Batch-fetch every relation type for up to 200 tasks. Powers relation overlays and sweeps.

#### Input Parameters

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

### Tasks relations create

**Slug:** `AMBIGUOUS_MCP_TASKS_RELATIONS_CREATE`

Create 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

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

### Tasks relations delete

**Slug:** `AMBIGUOUS_MCP_TASKS_RELATIONS_DELETE`

Delete a task relation edge. Auto-deletes the inverse edge for blocking/blocked_by pairs.

#### Input Parameters

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

### Tasks relations list

**Slug:** `AMBIGUOUS_MCP_TASKS_RELATIONS_LIST`

List edges in the task-relations graph for a task (related, blocking, blocked_by, duplicate).

#### Input Parameters

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

### Tasks remove subscriber

**Slug:** `AMBIGUOUS_MCP_TASKS_REMOVE_SUBSCRIBER`

Remove another user's subscription from a task. Requires task access.

#### Input Parameters

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

### Tasks sla dashboard

**Slug:** `AMBIGUOUS_MCP_TASKS_SLA_DASHBOARD`

Aggregate SLA metrics for the workspace (compliance rates, avg times, counts per status). Optionally scope to a project.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `days` | string | No | Window in days (1..365, default 90). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `project_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Tasks sla thresholds

**Slug:** `AMBIGUOUS_MCP_TASKS_SLA_THRESHOLDS`

Get the workspace's SLA thresholds (response + resolution times per priority). Auth-only.

#### Input Parameters

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

### Tasks subscribed

**Slug:** `AMBIGUOUS_MCP_TASKS_SUBSCRIBED`

List task IDs the caller is subscribed to (manual + auto-subscribed via creator/assignee/comment).

#### Input Parameters

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

### Tasks subscriptions list

**Slug:** `AMBIGUOUS_MCP_TASKS_SUBSCRIPTIONS_LIST`

List all users subscribed to a task (with the reason each is subscribed).

#### Input Parameters

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

### Tasks subscription status

**Slug:** `AMBIGUOUS_MCP_TASKS_SUBSCRIPTION_STATUS`

Check whether the current user is subscribed to a task (and the reason if so).

#### Input Parameters

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

### Tasks subtasks

**Slug:** `AMBIGUOUS_MCP_TASKS_SUBTASKS`

List immediate subtasks of a task (`parent_task_id = :id`).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `limit` | string | No | Max items to return (default 50, max 200). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | string | No | Number of items to skip (default 0). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Tasks templates delete

**Slug:** `AMBIGUOUS_MCP_TASKS_TEMPLATES_DELETE`

Delete a task template. Workspace admins or project admins only.

#### Input Parameters

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

### Tasks templates get

**Slug:** `AMBIGUOUS_MCP_TASKS_TEMPLATES_GET`

Get a single task template by ID.

#### Input Parameters

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

### Tasks templates update

**Slug:** `AMBIGUOUS_MCP_TASKS_TEMPLATES_UPDATE`

Update a task template. Workspace admins or project admins only.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No |  |
| `project_id` | string | No | If set, only project admins + workspace admins can edit. Pass null for workspace-wide. |
| `sort_order` | number | No |  |
| `templateId` | string | Yes |  |
| `description` | string | No |  |
| `default_labels` | array | No |  |
| `default_status` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_estimate` | string | No |  |
| `default_priority` | string | No |  |
| `default_assignee_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `default_custom_field_values` | object | No |  |

### Tasks views create

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_CREATE`

Create a saved task view (filter + layout). Setting `is_shared: true` exposes it to the workspace.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | Yes |  |
| `filters` | string | No |  |
| `is_shared` | boolean | No |  |
| `project_id` | string | No |  |
| `sort_order` | number | No |  |
| `default_layout` | string | No |  |
| `default_sort_by` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_group_by` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `default_sort_direction` | string | No |  |

### Tasks views delete

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_DELETE`

Delete a saved task view.

#### Input Parameters

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

### Tasks views layout get

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_LAYOUT_GET`

Get the caller's layout preferences for a view, or fall back to the view's defaults. `source` indicates which.

#### Input Parameters

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

### Tasks views layout update

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_LAYOUT_UPDATE`

Upsert the caller's layout preferences for a view (per-project scope optional).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `layout` | string | No |  |
| `viewId` | string | Yes |  |
| `columns` | string | No |  |
| `sort_by` | string | No |  |
| `group_by` | string | No |  |
| `project_id` | string | No |  |
| `wip_limits` | string | No |  |
| `show_completed` | boolean | No |  |
| `sort_direction` | string | No |  |
| `board_swimlanes` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Tasks views list

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_LIST`

List task views accessible to the caller (own + shared + system defaults).

#### Input Parameters

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

### Tasks views update

**Slug:** `AMBIGUOUS_MCP_TASKS_VIEWS_UPDATE`

Update a saved task view (rename, change filters or layout defaults, toggle sharing).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | No |  |
| `viewId` | string | Yes |  |
| `filters` | string | No |  |
| `is_shared` | boolean | No |  |
| `project_id` | string | No |  |
| `sort_order` | number | No |  |
| `default_layout` | string | No |  |
| `default_sort_by` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_group_by` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `default_sort_direction` | string | No |  |

### Teams cancel join request

**Slug:** `AMBIGUOUS_MCP_TEAMS_CANCEL_JOIN_REQUEST`

Cancel your own pending join request for this team.

#### Input Parameters

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

### Teams get subscription

**Slug:** `AMBIGUOUS_MCP_TEAMS_GET_SUBSCRIPTION`

Get the caller's email-delivery preference for the team. Returns `{team_id, user_id, email_delivery}`.

#### Input Parameters

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

### Teams join

**Slug:** `AMBIGUOUS_MCP_TEAMS_JOIN`

Join a team. Open teams grant instant membership; request teams create a pending join request; invite teams reject.

#### Input Parameters

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

### Teams leave

**Slug:** `AMBIGUOUS_MCP_TEAMS_LEAVE`

Leave a team. Cannot leave if you're the last admin.

#### Input Parameters

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

### Teams members list

**Slug:** `AMBIGUOUS_MCP_TEAMS_MEMBERS_LIST`

Paginated member list. Private teams visible only to members or admins.

#### Input Parameters

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

### Teams members remove

**Slug:** `AMBIGUOUS_MCP_TEAMS_MEMBERS_REMOVE`

Remove a member. Admin only. Cannot remove the last admin.

#### Input Parameters

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

### Teams members update role

**Slug:** `AMBIGUOUS_MCP_TEAMS_MEMBERS_UPDATE_ROLE`

Change a member's role. Admin only. Cannot demote the last admin.

#### Input Parameters

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

### Teams requests approve

**Slug:** `AMBIGUOUS_MCP_TEAMS_REQUESTS_APPROVE`

Approve a join request — adds the user as a member.

#### Input Parameters

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

### Teams requests deny

**Slug:** `AMBIGUOUS_MCP_TEAMS_REQUESTS_DENY`

Deny a join request.

#### Input Parameters

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

### Teams requests list

**Slug:** `AMBIGUOUS_MCP_TEAMS_REQUESTS_LIST`

List pending join requests. Admin only.

#### Input Parameters

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

### Teams searchable

**Slug:** `AMBIGUOUS_MCP_TEAMS_SEARCHABLE`

Search 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

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

### Teams update subscription

**Slug:** `AMBIGUOUS_MCP_TEAMS_UPDATE_SUBSCRIPTION`

Update 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

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

### Transfer ownership

**Slug:** `AMBIGUOUS_MCP_TRANSFER_OWNERSHIP`

Make 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

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

### Trash mail thread

**Slug:** `AMBIGUOUS_MCP_TRASH_MAIL_THREAD`

Trash all messages in a thread atomically. Moves every message in the thread to the trash folder.

#### Input Parameters

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

### Unblock sender

**Slug:** `AMBIGUOUS_MCP_UNBLOCK_SENDER`

Unblock by id or pattern.

#### Input Parameters

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

### Undo send email

**Slug:** `AMBIGUOUS_MCP_UNDO_SEND_EMAIL`

Undo an in-flight send within the undo-send window.

#### Input Parameters

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

### Unenroll contact from sequence

**Slug:** `AMBIGUOUS_MCP_UNENROLL_CONTACT_FROM_SEQUENCE`

Permanently 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

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

### Unfurl link

**Slug:** `AMBIGUOUS_MCP_UNFURL_LINK`

Fetch OpenGraph / link-preview metadata for a URL (title, description, image, site name, favicon). Useful for generating rich previews of shared links, or inspecting what a URL would look like when shared in chat. Only http(s) URLs are allowed, and internal/private addresses are blocked.

#### Input Parameters

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

### Ungroup slide elements

**Slug:** `AMBIGUOUS_MCP_UNGROUP_SLIDE_ELEMENTS`

Dissolve 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

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

### Unprotect range

**Slug:** `AMBIGUOUS_MCP_UNPROTECT_RANGE`

Remove a protected range from a spreadsheet by its ID. Returns 200 on success, 404 if the range does not exist.

#### Input Parameters

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

### Unpublish calendar

**Slug:** `AMBIGUOUS_MCP_UNPUBLISH_CALENDAR`

Revoke the public .ics feed for a calendar, making it private again.

#### Input Parameters

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

### Unpublish form

**Slug:** `AMBIGUOUS_MCP_UNPUBLISH_FORM`

Unpublish a form so it stops accepting public responses. Semantic shortcut for PATCH /api/forms/{id} with is_published=false.

#### Input Parameters

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

### Unsave message

**Slug:** `AMBIGUOUS_MCP_UNSAVE_MESSAGE`

Remove a saved (bookmarked) message from the user's saved list. The message itself is untouched; only the personal bookmark is deleted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel_id` | string | Yes |  |
| `message_id` | string | Yes | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Untrash email

**Slug:** `AMBIGUOUS_MCP_UNTRASH_EMAIL`

Restore a trashed email to inbox

#### Input Parameters

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

### Untrash mail thread

**Slug:** `AMBIGUOUS_MCP_UNTRASH_MAIL_THREAD`

Restore all trashed messages in a thread to inbox. Only affects messages currently in trash.

#### Input Parameters

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

### Update access

**Slug:** `AMBIGUOUS_MCP_UPDATE_ACCESS`

Change 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | 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. |
| `role` | string ("viewer" | "commenter" | "editor") | No |  |
| `team_id` | string | No | 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. |
| `user_id` | string | No | The specific person's ID, separate from the resource id. On update/removal, use the user ID from that resource's permission entry. |
| `expires_at` | string | No | ISO 8601 deadline for the grant, or null for no expiry. Bounded by the shareExpiryMaxDays platform limit. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update api key

**Slug:** `AMBIGUOUS_MCP_UPDATE_API_KEY`

Update an API key's name, scopes, or rate limit. Requires admin role.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Resource ID. |
| `name` | string | No |  |
| `scopes` | array | No |  |
| `expires_at` | string | No |  |
| `rate_limit` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `confirm_wildcard` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update canvas

**Slug:** `AMBIGUOUS_MCP_UPDATE_CANVAS`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Canvas board id. |
| `cover` | string | No | Owner-chosen preview cover. |
| `title` | string | No | Rename the board. |
| `settings` | object | No | Board settings (grid style). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update canvas timer

**Slug:** `AMBIGUOUS_MCP_UPDATE_CANVAS_TIMER`

Control 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Canvas board id. |
| `action` | string | Yes |  |
| `duration_ms` | integer | No | Countdown length in milliseconds (server stamps ends_at = now + this). action start only. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update channel member role

**Slug:** `AMBIGUOUS_MCP_UPDATE_CHANNEL_MEMBER_ROLE`

Change 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

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

### Update chart

**Slug:** `AMBIGUOUS_MCP_UPDATE_CHART`

Patch 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `x` | number | No |  |
| `y` | number | No |  |
| `id` | string | Yes |  |
| `tab` | string | No |  |
| `plot` | object | No |  |
| `type` | string ("bar" | "stackedBar" | "line" | "area" | "pie" | "donut" | "scatter" | "combo") | No |  |
| `title` | string | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `series` | object | No |  |
| `chart_id` | string | Yes |  |
| `dataRange` | object | No |  |
| `useHeaders` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update conditional format

**Slug:** `AMBIGUOUS_MCP_UPDATE_CONDITIONAL_FORMAT`

Update a conditional formatting rule by ID. Partial update: ranges or one canonical rule payload; replacing the kind clears the previous kind.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `ranges` | array | No |  |
| `ruleId` | string | Yes |  |
| `booleanRule` | object | No |  |
| `dataBarRule` | object | No |  |
| `iconSetRule` | object | No |  |
| `gradientRule` | object | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update contact

**Slug:** `AMBIGUOUS_MCP_UPDATE_CONTACT`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `email` | string | No |  |
| `phone` | string | No |  |
| `title` | string | No |  |
| `website` | string | No |  |
| `industry` | string | No |  |
| `company_id` | string | No |  |
| `lifecycle_stage` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | string | No |  |
| `expected_updated_at` | string | No | The updated_at from the last contact read. A stale revision returns 409; read again and submit only remaining changes. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update contact group

**Slug:** `AMBIGUOUS_MCP_UPDATE_CONTACT_GROUP`

Update an existing contact group's name, color, or sort order. Group name must remain unique within the workspace.

#### Input Parameters

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

### Update coworker

**Slug:** `AMBIGUOUS_MCP_UPDATE_COWORKER`

Update coworker metadata (persona, focus areas, display name, avatar).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `persona` | string | No |  |
| `avatar_url` | string | No |  |
| `focus_areas` | array | No |  |
| `display_name` | string | No |  |
| `enabled_skills` | string | No | Scope the coworker to these skills. Null clears the scope (full skill set). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update crm property definition

**Slug:** `AMBIGUOUS_MCP_UPDATE_CRM_PROPERTY_DEFINITION`

Update a custom-property definition's label or select options.

#### Input Parameters

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

### Update crm view

**Slug:** `AMBIGUOUS_MCP_UPDATE_CRM_VIEW`

Update a saved CRM view (rename, change filters, toggle default/shared).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `filters` | object | No |  |
| `is_shared` | boolean | No |  |
| `is_default` | boolean | No |  |
| `sort_field` | string | No |  |
| `entity_type` | string ("contacts" | "companies" | "deals") | No | Which list page the saved view applies to. |
| `sort_direction` | string ("asc" | "desc") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update data connector

**Slug:** `AMBIGUOUS_MCP_UPDATE_DATA_CONNECTOR`

Update a data connector's name, config, target cells, or refresh schedule.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `config` | object | No |  |
| `targetCol` | string | No |  |
| `targetRow` | string | No |  |
| `target_col` | number | No |  |
| `target_row` | number | No |  |
| `targetSheet` | string | No |  |
| `connector_id` | string | Yes |  |
| `target_sheet` | string | No |  |
| `refreshSchedule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `refresh_schedule` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update deal

**Slug:** `AMBIGUOUS_MCP_UPDATE_DEAL`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | No |  |
| `amount` | string | No |  |
| `status` | string ("open" | "won" | "lost") | No | Lifecycle of a deal. `won` and `lost` close the deal; `lost` requires a `lost_reason`. |
| `currency` | string | No |  |
| `owner_id` | string | No |  |
| `stage_id` | string | No |  |
| `close_date` | string | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `lost_reason` | string | No |  |
| `pipeline_id` | string | No |  |
| `probability` | integer | No |  |
| `confirm_zero` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | object | No |  |
| `primary_contact_id` | string | No | Alias for `contact_id`. Either is accepted; sending both with different values returns 400. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update deal line item

**Slug:** `AMBIGUOUS_MCP_UPDATE_DEAL_LINE_ITEM`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `quantity` | number | No |  |
| `product_id` | string | No |  |
| `sort_order` | integer | No |  |
| `unit_price` | number | No |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `billing_interval` | string | No |  |
| `discount_percent` | number | No |  |
| `sync_deal_amount` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update deal template

**Slug:** `AMBIGUOUS_MCP_UPDATE_DEAL_TEMPLATE`

Update a deal template. Providing `line_items` replaces the entire line-item list.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `amount` | string | No |  |
| `currency` | string | No |  |
| `stage_id` | string | No |  |
| `is_active` | boolean | No |  |
| `line_items` | array | No |  |
| `description` | string | No |  |
| `pipeline_id` | string | No |  |
| `probability` | string | No |  |
| `title_template` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `custom_properties` | object | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `close_date_offset_days` | string | No |  |

### Update deck settings

**Slug:** `AMBIGUOUS_MCP_UPDATE_DECK_SETTINGS`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `theme` | string | No |  |
| `aspect_ratio` | string ("16:9" | "4:3") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `showSlideNumbers` | boolean | No | Camel-case alias accepted by the SDK (AMB-6729). |
| `defaultBackground` | string | No | Camel-case alias accepted by the SDK. |
| `default_background` | string | No |  |
| `show_slide_numbers` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update document

**Slug:** `AMBIGUOUS_MCP_UPDATE_DOCUMENT`

Edit 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | No |  |
| `labels` | array | No |  |
| `content` | string | No | 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`. |
| `operations` | array | No | 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. |
| `page_style` | object | No |  |
| `suggesting` | boolean | No | Commenter-relaxed write: content changes must carry track-change marks (auto-wrapped for agents). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update document page style

**Slug:** `AMBIGUOUS_MCP_UPDATE_DOCUMENT_PAGE_STYLE`

Set 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

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

### Update draft email

**Slug:** `AMBIGUOUS_MCP_UPDATE_DRAFT_EMAIL`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cc` | array | No |  |
| `id` | string | Yes |  |
| `to` | array | No | Empty drafts allowed; required when sending. |
| `bcc` | array | No |  |
| `fields` | string | No |  |
| `labels` | array | No |  |
| `notify` | string | No |  |
| `deal_id` | string | No |  |
| `subject` | string | No |  |
| `body_html` | string | No | HTML import, normalized to Markdown when body_markdown is absent. Takes precedence over body_text. |
| `body_text` | string | No | Literal plain-text body, normalized to Markdown when body_markdown and body_html are absent. |
| `thread_id` | string | No | Attach the message to an existing thread. |
| `contact_id` | string | No |  |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `references` | array | No |  |
| `attachments` | array | No |  |
| `in_reply_to` | string | No |  |
| `body_markdown` | string | No | Canonical authoring-format body. Takes precedence over HTML/text, including an explicit empty string. Compiles to HTML on send. |
| `attachment_ids` | array | No | Drive file IDs to attach. |
| `idempotency_key` | string | No | Optional retry key. Reusing the same key with the same send request returns the original send. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `request_read_receipt` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update event

**Slug:** `AMBIGUOUS_MCP_UPDATE_EVENT`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `color` | string | No |  |
| `force` | boolean | No |  |
| `title` | string | No |  |
| `end_at` | string | No |  |
| `guests` | array | No | 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. |
| `status` | string ("confirmed" | "tentative" | "cancelled" | "outofoffice") | No | Event status. `outofoffice` is used by the OOO responder. |
| `all_day` | boolean | No |  |
| `deal_id` | string | No |  |
| `location` | string | No |  |
| `start_at` | string | No |  |
| `attendees` | array | No | 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. |
| `event_url` | string | No |  |
| `contact_id` | string | No |  |
| `event_type` | string ("default" | "outOfOffice" | "focusTime") | No | 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. |
| `visibility` | string ("default" | "public" | "private") | No | Visibility scope for the event. |
| `description` | string | No |  |
| `send_updates` | string ("all" | "external_only" | "none") | No | 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. |
| `transparency` | string ("opaque" | "transparent") | No | Free/busy classification (RFC 5545 TRANSP). `opaque` = Busy (default; blocks availability). `transparent` = Free (e.g. focus time). |
| `conference_url` | string | No | 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. |
| `skip_event_ids` | array | No | Existing-event ids the `new_and_existing` bulk-decline should leave untouched. |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `recurrence_dates` | array | No |  |
| `guests_can_modify` | boolean | No |  |
| `auto_decline_scope` | string ("new_only" | "new_and_existing") | No | 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. |
| `conference_provider` | string | No |  |
| `auto_decline_message` | string | No | Auto-reply note sent with an OOO decline. |
| `meeting_notes_doc_id` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `guests_can_invite_others` | boolean | No |  |
| `guests_can_see_other_guests` | boolean | No |  |

### Update form

**Slug:** `AMBIGUOUS_MCP_UPDATE_FORM`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `slug` | string | No |  |
| `title` | string | No |  |
| `fields` | array | No |  |
| `schema` | object | No |  |
| `settings` | object | No |  |
| `closes_at` | string | No |  |
| `description` | string | No |  |
| `is_published` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update form variant

**Slug:** `AMBIGUOUS_MCP_UPDATE_FORM_VARIANT`

Update 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

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

### Update identity api key

**Slug:** `AMBIGUOUS_MCP_UPDATE_IDENTITY_API_KEY`

Update 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

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

### Update mail label

**Slug:** `AMBIGUOUS_MCP_UPDATE_MAIL_LABEL`

Update a mail label's name, color or sidebar order.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No |  |
| `color` | string ("red" | "orange" | "yellow" | "green" | "blue" | "purple" | "pink" | "cyan" | "gray") | No | Built-in label palette. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `label_id` | string | Yes |  |
| `parent_id` | string | No |  |
| `mailbox_id` | string | No | Target a shared mailbox you hold. Omit for your own mailbox; 404 if you don't hold it. |
| `sort_order` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `show_in_sidebar` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update mail rule

**Slug:** `AMBIGUOUS_MCP_UPDATE_MAIL_RULE`

Update a mail rule's conditions or actions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No |  |
| `actions` | array | No |  |
| `enabled` | boolean | No |  |
| `rule_id` | string | Yes |  |
| `conditions` | array | No |  |
| `match_mode` | string ("all" | "any") | No |  |
| `sort_order` | integer | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `stop_processing` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update mail template

**Slug:** `AMBIGUOUS_MCP_UPDATE_MAIL_TEMPLATE`

Update a saved mail template's subject or body.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No |  |
| `subject` | string | No |  |
| `category` | string | No |  |
| `body_html` | string | No | HTML import normalized to Markdown when body_markdown is absent; wins over body_text. |
| `body_text` | string | No | Literal plain-text body normalized to Markdown when Markdown/HTML are absent. |
| `sort_order` | integer | No |  |
| `template_id` | string | Yes |  |
| `body_markdown` | string | No | Canonical Markdown body; wins over HTML/text even when explicitly empty. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update named range

**Slug:** `AMBIGUOUS_MCP_UPDATE_NAMED_RANGE`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | Yes |  |
| `range` | string | No |  |
| `newName` | string | No |  |
| `expression` | string | No |  |
| `referenceStyle` | string ("fixed" | "caller-relative-a1") | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update pipeline

**Slug:** `AMBIGUOUS_MCP_UPDATE_PIPELINE`

Update 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

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

### Update pivot table

**Slug:** `AMBIGUOUS_MCP_UPDATE_PIVOT_TABLE`

Patch 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `tab` | string | No |  |
| `filters` | string | No |  |
| `pivot_id` | string | Yes |  |
| `rowFields` | array | No |  |
| `useHeaders` | boolean | No |  |
| `sourceRange` | string | No |  |
| `valueFields` | array | No |  |
| `columnFields` | array | No |  |
| `showRowTotals` | boolean | No |  |
| `sourceTabName` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `showColumnTotals` | boolean | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update product

**Slug:** `AMBIGUOUS_MCP_UPDATE_PRODUCT`

Update a CRM product's name, price or other fields.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `sku` | string | No |  |
| `name` | string | No |  |
| `currency` | string | No |  |
| `is_active` | boolean | No |  |
| `unit_price` | number | No |  |
| `description` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `billing_interval` | string ("one_time" | "monthly" | "quarterly" | "yearly") | No |  |
| `contract_term_months` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update project

**Slug:** `AMBIGUOUS_MCP_UPDATE_PROJECT`

Update a project's name, description, icon, or color. Provide only the fields you want to change.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `icon` | string | No |  |
| `name` | string | No |  |
| `color` | string | No |  |
| `visibility` | string ("private" | "team" | "workspace") | No |  |
| `description` | string | No |  |
| `workspaceRole` | string ("commenter" | "editor") | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `estimation_scale` | string ("fibonacci" | "linear" | "t-shirt") | No |  |
| `auto_archive_days` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `notification_channel_id` | string | No |  |

### Update quote

**Slug:** `AMBIGUOUS_MCP_UPDATE_QUOTE`

Update a CRM quote. Providing `line_items` replaces the entire line-item list. Totals are auto-recomputed.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `notes` | string | No |  |
| `terms` | string | No |  |
| `title` | string | No |  |
| `status` | string ("draft" | "sent" | "viewed" | "accepted" | "rejected" | "expired") | No | Quote lifecycle. `accepted`/`rejected` are terminal; `viewed` is recorded by the open-tracking pixel. |
| `deal_id` | string | No |  |
| `currency` | string | No |  |
| `owner_id` | string | No |  |
| `tax_rate` | number | No |  |
| `company_id` | string | No |  |
| `contact_id` | string | No |  |
| `line_items` | array | No |  |
| `valid_until` | string | No |  |
| `quote_number` | string | No |  |
| `discount_type` | string | No |  |
| `discount_value` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update resource comment

**Slug:** `AMBIGUOUS_MCP_UPDATE_RESOURCE_COMMENT`

Update 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

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

### Update role

**Slug:** `AMBIGUOUS_MCP_UPDATE_ROLE`

Update a custom role's name or permissions. Requires admin role.

#### Input Parameters

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

### Update scheduled message

**Slug:** `AMBIGUOUS_MCP_UPDATE_SCHEDULED_MESSAGE`

Edit 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

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

### Update scheduler link

**Slug:** `AMBIGUOUS_MCP_UPDATE_SCHEDULER_LINK`

Update a scheduler link (rename, change availability, toggle active, etc.).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `slug` | string | No |  |
| `title` | string | No |  |
| `location` | string | No |  |
| `stage_id` | string | No |  |
| `timezone` | string | No |  |
| `is_active` | boolean | No |  |
| `brand_color` | string | No |  |
| `description` | string | No |  |
| `pipeline_id` | string | No |  |
| `member_user_ids` | array | No | Round-robin roster: workspace user ids that share this link's bookings. Empty/omitted = solo (owner only). When set, a slot is offered while any member is free and each booking is assigned to the least-loaded free member. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `duration_minutes` | integer | No |  |
| `max_advance_days` | integer | No |  |
| `availability_hours` | string | No |  |
| `min_notice_minutes` | integer | No |  |
| `auto_create_contact` | boolean | No |  |
| `buffer_after_minutes` | integer | No |  |
| `buffer_before_minutes` | integer | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update scoring rule

**Slug:** `AMBIGUOUS_MCP_UPDATE_SCORING_RULE`

Update a lead scoring rule (name, field, operator, value, points, is_active).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `field` | string | No |  |
| `value` | string | No |  |
| `points` | integer | No |  |
| `operator` | string | No | PATCH preserves unknown operator values for forward compatibility. |
| `is_active` | boolean | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update security settings

**Slug:** `AMBIGUOUS_MCP_UPDATE_SECURITY_SETTINGS`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `require_2fa` | boolean | No |  |
| `ip_allowlist` | array | No |  |
| `outside_sharing` | string ("on" | "off" | "domains") | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `password_min_length` | integer | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `session_timeout_hours` | integer | No |  |
| `outside_sharing_domains` | array | No | Domains outside sharing is allowed with when outside_sharing is domains, e.g. ["acme.com"]. |
| `require_2fa_enforcement` | string ("enforced" | "coming_soon") | No |  |
| `ip_allowlist_enforcement` | string ("enforced" | "coming_soon") | No |  |

### Update sequence

**Slug:** `AMBIGUOUS_MCP_UPDATE_SEQUENCE`

Update a sequence (rename, description, toggle active, replace step list). Providing `steps` replaces the entire step list.

#### Input Parameters

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

### Update settings

**Slug:** `AMBIGUOUS_MCP_UPDATE_SETTINGS`

Update workspace settings (name, logo, timezone, etc.). Requires admin role. Pass a flat key-value object.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `theme` | string | No |  |
| `cycle_defaults` | string | No | Defaults for new task cycles, e.g. `{ duration_days, auto_rollover }`. |
| `sla_thresholds` | string | No | Per-priority response and resolution SLA minutes: `{ urgent: { response, resolution }, … }`; null clears. |
| `email_signature` | string | No | Workspace default email signature (Markdown), used by members without a personal one. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_timezone` | string | No | IANA timezone new members and workspace-wide schedules default to. |
| `default_reactions` | string | No | Up to six emoji strings offered as one-click reactions in chat; null clears. |
| `user_storage_quota` | string | No | Per-member Drive quota in bytes; takes precedence over `default_storage_quota`. |
| `ai_processing_enabled` | string | No | Boolean; null clears. |
| `default_cooldown_days` | string | No | Non-negative integer days between task cycles by default; null clears. |
| `default_storage_quota` | string | No | Per-member Drive quota in gigabytes for members with no override. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |
| `tasks_auto_close_days` | string | No | Positive integer days after which done tasks auto-close; null disables. |
| `tasks_auto_archive_days` | string | No | Positive integer days after which closed tasks auto-archive; null disables. |
| `chat_read_receipts_enabled` | string | No | Boolean; null clears. |
| `default_cycle_duration_days` | string | No | Positive integer days a new task cycle spans by default; null clears. |

### Update shared drive

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHARED_DRIVE`

Update a shared drive (manager-only).

#### Input Parameters

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

### Update shared drive member

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHARED_DRIVE_MEMBER`

Update a member role (manager-only).

#### Input Parameters

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

### Update sheet image

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHEET_IMAGE`

Update editable floating images with cell anchors and CSS pixel geometry. Image src must reference an image asset owned by this sheet.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `alt` | string | No |  |
| `col` | integer | No |  |
| `row` | integer | No |  |
| `src` | string | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `offsetX` | number | No |  |
| `offsetY` | number | No |  |
| `image_id` | string | Yes |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update sheet merges

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHEET_MERGES`

Replace 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `sheet` | string | No | Target tab name. Omit to use the first tab. |
| `merges` | array | No | 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. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update sheet picture group

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHEET_PICTURE_GROUP`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `alt` | string | No |  |
| `col` | integer | No |  |
| `row` | integer | No |  |
| `root` | string | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `offsetX` | number | No |  |
| `offsetY` | number | No |  |
| `group_id` | string | Yes |  |
| `intrinsicWidth` | number | No |  |
| `intrinsicHeight` | number | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update sheet shape

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHEET_SHAPE`

Update editable floating shapes with editable text, cell anchors and CSS pixel geometry.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `col` | integer | No |  |
| `row` | integer | No |  |
| `fill` | string | No |  |
| `text` | string | No |  |
| `type` | string ("rect" | "ellipse") | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `stroke` | string | No |  |
| `offsetX` | number | No |  |
| `offsetY` | number | No |  |
| `padding` | number | No |  |
| `fontSize` | number | No |  |
| `shape_id` | string | Yes |  |
| `textAlign` | string ("left" | "center" | "right") | No |  |
| `textColor` | string | No |  |
| `textFrame` | string | No |  |
| `fontFamily` | string | No |  |
| `textLayout` | string ("standard" | "excel") | No |  |
| `textScaleX` | number | No |  |
| `textScaleY` | number | No |  |
| `strokeWidth` | number | No |  |
| `drawingFrame` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update sheet validation settings

**Slug:** `AMBIGUOUS_MCP_UPDATE_SHEET_VALIDATION_SETTINGS`

Set worksheet validation prompt suppression without replacing cells, rules, or presentation. Send disablePrompts=null to restore the absent default setting.

#### Input Parameters

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

### Update sign document

**Slug:** `AMBIGUOUS_MCP_UPDATE_SIGN_DOCUMENT`

Update a draft signing document.

#### Input Parameters

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

### Update slicer

**Slug:** `AMBIGUOUS_MCP_UPDATE_SLICER`

Patch 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `x` | number | No |  |
| `y` | number | No |  |
| `id` | string | Yes |  |
| `tab` | string | No |  |
| `title` | string | No |  |
| `width` | number | No |  |
| `height` | number | No |  |
| `columnId` | string | No |  |
| `slicer_id` | string | Yes |  |
| `useHeaders` | boolean | No |  |
| `sourceRange` | object | No |  |
| `selectedValues` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update slide

**Slug:** `AMBIGUOUS_MCP_UPDATE_SLIDE`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `index` | string | Yes |  |
| `notes` | string | No |  |
| `slide` | object | No | Alternative envelope — fields merged with top-level keys. |
| `layout` | object | No |  |
| `elements` | array | No | Full-replace element list for the slide. |
| `background` | string | No |  |
| `transition` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update slide master

**Slug:** `AMBIGUOUS_MCP_UPDATE_SLIDE_MASTER`

Update a master slide's name, background, or elements. Slides using the master resolve the updated elements by reference.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No |  |
| `layout` | object | No |  |
| `elements` | array | No |  |
| `master_id` | string | Yes |  |
| `background` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update task

**Slug:** `AMBIGUOUS_MCP_UPDATE_TASK`

Update a task. Status changes to 'done' auto-spawn the next recurrence (when set), trigger CRM activity logging, and emit task.completed events.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `title` | string | No |  |
| `status` | string ("todo" | "in_progress" | "done" | "cancelled" | "blocked") | No | System task status category. Drives the built-in board columns. |
| `deal_id` | string | No |  |
| `goal_id` | string | No |  |
| `cycle_id` | string | No |  |
| `due_date` | string | No |  |
| `estimate` | string | No |  |
| `priority` | string ("urgent" | "high" | "medium" | "low") | No | Task priority. Determines SLA timer and sort weight. |
| `contact_id` | string | No |  |
| `project_id` | string | No |  |
| `sort_order` | number | No |  |
| `start_date` | string | No |  |
| `assignee_id` | string | No |  |
| `description` | string | No |  |
| `parent_task_id` | string | No |  |
| `subscriber_ids` | array | No | 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. |
| `task_status_id` | string | No |  |
| `due_date_source` | string ("manual" | "sla") | No | Defaults to `manual` when `due_date` changes through this update. Set explicitly to `sla` to mark a system-set due date. |
| `recurrence_rule` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `estimated_minutes` | string | No |  |
| `time_spent_minutes` | string | No | Manual override; usually auto-managed by time entries. |
| `custom_field_values` | object | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update team

**Slug:** `AMBIGUOUS_MCP_UPDATE_TEAM`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `icon` | string | No |  |
| `name` | string | No |  |
| `slug` | string | No |  |
| `color` | string | No |  |
| `team_id` | string | Yes |  |
| `visibility` | string ("public" | "private") | No |  |
| `description` | string | No |  |
| `join_policy` | string ("open" | "request" | "invite") | No |  |
| `parent_team_id` | string | No |  |
| `posting_policy` | string ("open" | "members_only" | "admins_only") | No |  |
| `email_domain_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `default_channels` | array | No |  |
| `email_local_part` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update user

**Slug:** `AMBIGUOUS_MCP_UPDATE_USER`

Update a member's role, status, or storage quota. Requires admin or owner; the last owner cannot lose ownership.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `type` | string ("human" | "agent") | No | User identity. Humans authenticate with passwords / SSO; agents with API keys. |
| `roles` | array | No |  |
| `username` | string | No |  |
| `avatar_url` | string | No |  |
| `display_name` | string | No |  |
| `capacity_hours` | string | No | Per-user weekly Workload capacity in hours. Null clears the override back to the workspace default. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `storage_quota_bytes` | string | No |  |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update wiki page

**Slug:** `AMBIGUOUS_MCP_UPDATE_WIKI_PAGE`

Update 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `icon` | string | No |  |
| `slug` | string | No |  |
| `title` | string | No |  |
| `content` | string | No | Page content as Markdown string or ProseMirror JSON object. |
| `space_id` | string | No | Target space ID for cross-space move. |
| `sort_order` | number | No |  |
| `cover_image` | string | No |  |
| `is_template` | boolean | No |  |
| `parent_page_id` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `content_markdown` | string | No | Legacy alias for `content`. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Update wiki synced block

**Slug:** `AMBIGUOUS_MCP_UPDATE_WIKI_SYNCED_BLOCK`

Update 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

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

### Update workspace

**Slug:** `AMBIGUOUS_MCP_UPDATE_WORKSPACE`

Update workspace name or slug. Requires admin role.

#### Input Parameters

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

### Use mail template

**Slug:** `AMBIGUOUS_MCP_USE_MAIL_TEMPLATE`

Record template use.

#### Input Parameters

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

### Users list

**Slug:** `AMBIGUOUS_MCP_USERS_LIST`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Substring filter against `display_name` and `username` (case-insensitive). |
| `type` | string ("human" | "agent") | No | Restrict to one principal kind. Omitted, both are listed. |
| `limit` | string | No | Max rows to return. Default 50, hard cap 100. |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `exclude_suspended` | string ("true" | "false") | No | Pass 'true' to drop suspended memberships. Omitted, they are listed. |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Use sign template

**Slug:** `AMBIGUOUS_MCP_USE_SIGN_TEMPLATE`

Create a new draft document from a template, populating fields with placeholder signer roles.

#### Input Parameters

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

### Verify domain

**Slug:** `AMBIGUOUS_MCP_VERIFY_DOMAIN`

Trigger DNS verification for a workspace domain. Requires admin role.

#### Input Parameters

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

### Verify domain ownership

**Slug:** `AMBIGUOUS_MCP_VERIFY_DOMAIN_OWNERSHIP`

Verify custom domain ownership via DNS TXT record. On success, auto-registers with SES to retrieve DKIM/SPF records. Requires admin role.

#### Input Parameters

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

### Webhooks create

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_CREATE`

Register 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

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

### Webhooks delete

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_DELETE`

Delete one webhook subscription by id.

#### Input Parameters

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

### Webhooks deliveries list

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_DELIVERIES_LIST`

List recent delivery attempts (status, response, retries). Paginated via `?limit=` (default 25) and `?offset=` (default 0).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `limit` | integer | No | Page size (default 25, max 500). |
| `fields` | string | No |  |
| `notify` | string | No |  |
| `offset` | integer | No | Offset for pagination (must be ≥ 0). |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Webhooks event types

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_EVENT_TYPES`

List event types an agent can subscribe to. Includes the `*` wildcard.

#### Input Parameters

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

### Webhooks get

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_GET`

Get one webhook subscription's config by id.

#### Input Parameters

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

### Webhooks list

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_LIST`

List webhook registrations owned by the caller.

#### Input Parameters

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

### Webhooks test

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_TEST`

Send a test ping payload to the webhook URL.

#### Input Parameters

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

### Webhooks update

**Slug:** `AMBIGUOUS_MCP_WEBHOOKS_UPDATE`

Update a webhook (url, events, description, active, headers). Body shape matches `UpdateWebhookInput`. `headers` replaces the whole custom-header map; `null` or `{}` clears it.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `url` | string | No |  |
| `name` | string | No |  |
| `active` | string | No |  |
| `events` | array | No |  |
| `headers` | string | No |  |
| `description` | string | No |  |
| `bearer_token` | string | No |  |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Wiki database create

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_CREATE`

Create an inline database on a wiki page. Requires editor role on the host page.

#### Input Parameters

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

### Wiki database get

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_GET`

Get an inline database with its full row set.

#### Input Parameters

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

### Wiki database row create

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_ROW_CREATE`

Append a row to an inline database. Requires editor role on the host page.

#### Input Parameters

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

### Wiki database row delete

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_ROW_DELETE`

Delete a database row.

#### Input Parameters

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

### Wiki database row update

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_ROW_UPDATE`

Update properties or sort order on a database row.

#### Input Parameters

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

### Wiki database update

**Slug:** `AMBIGUOUS_MCP_WIKI_DATABASE_UPDATE`

Update an inline database's name, schema, or views. Requires editor role on the host page.

#### Input Parameters

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

### Wiki native backup

**Slug:** `AMBIGUOUS_MCP_WIKI_NATIVE_BACKUP`

Export a separately labeled, digest-bound native Wiki backup containing the complete workspace Wiki graph. This is not DOCX.

#### Input Parameters

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

### Wiki native restore

**Slug:** `AMBIGUOUS_MCP_WIKI_NATIVE_RESTORE`

Restore a native Wiki backup into its empty source workspace. Preserves spaces, hierarchy, page content, databases, backlinks, synced blocks, permissions, versions, and comments.

#### Input Parameters

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

### Wiki page asset create

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_ASSET_CREATE`

Add 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `name` | string | No | File name to keep with the image; defaults to `image`. |
| `mime_type` | string | No | Declared type. The stored type is decided from the bytes. |
| `source_url` | string | No | 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. |
| `content_base64` | string | No | The image bytes, base64-encoded (no `data:` prefix). |
| `source_file_id` | string | No | Copy the current bytes of a Drive file the caller can view instead of sending bytes. The Drive file is never referenced afterwards. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Wiki page backlinks list

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_BACKLINKS_LIST`

List wiki pages that contain `[[link]]` references to this page. Use this to see what pages cite a given page, or to find inbound knowledge links.

#### Input Parameters

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

### Wiki page children list

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_CHILDREN_LIST`

List 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

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

### Wiki page database create

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_DATABASE_CREATE`

Create an inline database on a specific wiki page.

#### Input Parameters

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

### Wiki page duplicate

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_DUPLICATE`

Duplicate a wiki page (and optionally its descendants) into a target space + parent. Returns the new top-level page.

#### Input Parameters

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

### Wiki page export

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_EXPORT`

Export a wiki page to docx, pdf, html, or md. Streams the file with a Content-Disposition attachment header.

#### Input Parameters

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

### Wiki page permanent delete

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_PERMANENT_DELETE`

Permanently delete a trashed wiki page. Irreversible.

#### Input Parameters

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

### Wiki page restore

**Slug:** `AMBIGUOUS_MCP_WIKI_PAGE_RESTORE`

Restore a trashed wiki page and its children.

#### Input Parameters

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

### Wiki space delete

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_DELETE`

Delete a wiki space and all of its pages.

#### Input Parameters

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

### Wiki space get

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_GET`

Get a wiki space by slug, with its full page tree. Supports cursor pagination on `pages`.

#### Input Parameters

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

### Wiki space member add

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_MEMBER_ADD`

Add a user as a direct member of a wiki space with a given role.

#### Input Parameters

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

### Wiki space member remove

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_MEMBER_REMOVE`

Remove a direct member from a wiki space.

#### Input Parameters

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

### Wiki space members list

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_MEMBERS_LIST`

List distinct members of a space — the owner plus everyone with a page-level permission inside it.

#### Input Parameters

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

### Wiki space update

**Slug:** `AMBIGUOUS_MCP_WIKI_SPACE_UPDATE`

Update a wiki space. Only the space owner may change settings.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes |  |
| `icon` | string | No |  |
| `name` | string | No |  |
| `slug` | string | No |  |
| `is_private` | boolean | No |  |
| `visibility` | string ("restricted" | "workspace" | "link" | "public") | No | Space/page visibility. `restricted` = invitees only. `workspace` = any workspace member. `link` = anyone with the link. `public` = indexable. |
| `description` | string | No |  |
| `workspaceRole` | string ("viewer" | "commenter" | "editor") | No | Role the Everyone-team row grants when visibility is `workspace`. |
| `request_context` | string | Yes | Describe why this request is being made and how it supports the user’s overall goal. This explanation is used for analytics to understand how this request is intended to accomplish that goal. Provide 20–30 words in third person, without using “we,” “I,” or “you.” Do not include credentials, secrets, or personal information. Example: “Reviewing upcoming calendar events to identify scheduling conflicts and prepare a weekly availability summary that helps the team coordinate its meetings.” |
| `reference_resource_id` | string | No | If available, provide the ID of the email, chat message, comment, task, document, file, or other Ambiguous resource where the user requested this work. |

### Wiki trash list

**Slug:** `AMBIGUOUS_MCP_WIKI_TRASH_LIST`

List trashed (soft-deleted) wiki pages in the workspace.

#### Input Parameters

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