API & DEVELOPERS

MCP reference · v1

update_task

Update an authorized task. Contributor, reviewer and portal-administrator permissions are enforced by the server.

Changes saved state

Company permissions

Required scopes: orchesphere.read, orchesphere.jobs. Current identity, company and service/portal rights are checked for every call. Scopes do not create access.

Task admin/contributor/reviewer. Reviewer can update status only. Reassignment is not exposed. Parent portal and company rights still apply. Equivalent REST operation.

Input schema

FieldTypeRequiredDescription / bounds
workspaceIdstringYesAn assigned company workspace ID.
taskIdstringYes—
titlestringNomaxLength: 240
descriptionstringNomaxLength: 6000
status"todo" | "in_progress" | "blocked" | "review" | "done" | "cancelled"No—
Complete MCP input schema
{
  "type": "object",
  "properties": {
    "workspaceId": {
      "type": "string",
      "description": "An assigned company workspace ID."
    },
    "taskId": {
      "type": "string"
    },
    "title": {
      "type": "string",
      "maxLength": 240
    },
    "description": {
      "type": "string",
      "maxLength": 6000
    },
    "status": {
      "type": "string",
      "enum": [
        "todo",
        "in_progress",
        "blocked",
        "review",
        "done",
        "cancelled"
      ]
    }
  },
  "required": [
    "workspaceId",
    "taskId"
  ],
  "additionalProperties": false
}

Tool call

json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "update_task",
    "arguments": {
      "workspaceId": "11111111-1111-4111-8111-111111111111",
      "taskId": "33333333-3333-4333-8333-333333333333"
    }
  }
}

POST to https://orchesphere.ai/mcp with a Bearer token approved for the MCP resource. Initialize the connection first. Examples use fictional identifiers.

Response handling

A successful tool result includes text content and structuredContent. Inspect isError before treating a tool result as successful. Authentication and scope failures may use HTTP 401/403 with WWW-Authenticate. This tool does not publish a separate MCP output schema; use its returned structure rather than assuming a provider business-record response.

All MCP tools · Errors and retry guidance