Recruit CRM MCP

Overview Schema Source Related Servers Discussions Admin

update_task

Update an existing task by modifying its title, start date, description, task type, or owner. Unspecified fields remain unchanged.

Instructions

Update an existing task via partial POST to /v1/tasks/{id}.

Only non-None fields are forwarded; omitted fields are preserved. task_type_id is the integer ID from list_task_types; omit to keep current type. description accepts Markdown. NOTE: marking a task complete is not supported by the Recruit CRM API on this endpoint — the status field is silently ignored (see CLAUDE.md). Delete the task or use the RCRM UI instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "update_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes
`title`	No
`start_date`	No
`description`	No
`task_type_id`	No
`owner_id`	No

Output Schema

Name	Required	Description	Default
`kind`	Yes
`id`	Yes
`title`	No
`url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.19.0May 30, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses partial update semantics (non-None fields forwarded, omitted fields preserved), that task_type_id is an integer from list_task_types, and importantly that the status field is silently ignored for completion. Does not cover permissions or rate limits, but is otherwise transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds value. Clear structure: update action, partial update rule, specific parameter notes, and a warning. No redundancy or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, output schema exists, and no annotations, the description covers key behavioral aspects and provides warnings. Lacks mention of prerequisites (e.g., task existence) but is otherwise complete for the tool's purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description adds meaning: explains task_type_id source, description supports Markdown, and clarifies partial update behavior. Does not explain each parameter individually but provides sufficient context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it updates an existing task via partial POST to a specific endpoint. It distinguishes itself from other tools like create_task and get_task by explicitly focusing on update, and contrasts with delete task mentioned for completion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (update existing task) and when not to (marking task complete is not supported, advises delete or UI instead). Also provides guidance on task_type_id from list_task_types and notes that description accepts Markdown.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server