mcpHosted AI, explicit consent

Review comment draft

tools/call

Act on a single AI-drafted comment: approve, reject, edit-then-approve, send it live to LinkedIn, or regenerate it with new instructions.

Parameters

workspaceId

string

Optional workspace ID or slug. Required when this credential can access multiple workspaces and no workspace was configured on the client.

draftIdrequired

string

The comment draft UUID.

actionrequired

string

No description.

approve | reject | edit | send | regenerate

edited_comment

string

Required for action=edit. Also usable to override the sent text for action=send.

rejection_reason

string

Optional context for action=reject.

instructions

string

Regeneration guidance for action=regenerate.

allowHostedAi

boolean

Must be true when this operation uses Pipeline hosted inference.

Example

MCP tools/calljson

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "review-comment-draft",
    "arguments": {
      "draftId": "00000000-0000-4000-8000-000000000000",
      "action": "approve",
      "allowHostedAi": true
    }
  }
}

Response

The operation is available, but its typed response schema has not been published yet.

JSON-RPC errors

-32602: Invalid parameters. Field-level details are returned in the JSON-RPC error data.
-32001: Authentication or hosted AI consent is required.
-32003: Workspace access is denied.
-32029: The request was rate limited.