Skip to main content
Glama

update-task

Destructive

Modify an existing Dooray task by providing only the fields to change; omitted fields keep their current values.

Instructions

Update an existing task in a Dooray project.

Only provide the fields you want to change. Fields you leave out keep their current values, so get-task is not needed first.

Fields:

  • Assignees, CC: assignees and cc each REPLACE that list. Passing only one of them keeps the other list. addAssignees, removeAssignees, addCc, removeCc change only the members you list. Do not combine add/remove options with assignees or cc

    • Member options: get-my-member-info, get-project-member-list, get-project-member-group-list. Format {"id": "...", "type": "member|group|email"} ("member": organizationMemberId, "group": group id, "email": email address)

  • Tags: tagIds REPLACES all tags. addTagIds, removeTagIds change only the tags you list. Do not combine them with tagIds

    • Check get-tag-list first: tags from every mandatory tag group (tagGroup.mandatory=true) must remain or the update fails with 500. tagGroup.selectOne=true allows exactly one tag from that group

  • Workflow: workflowId from get-project-workflow-list. Classes: backlog (대기), registered (등록/할 일), working (진행 중), closed (완료)

  • Parent (상위 업무): parentPostId. A task that already has sub-tasks cannot be set as a parent

  • Korean Terms: "to" = 담당자 (assignee), "cc" = 참조 (reference)

  • Priority: Use "none" to remove priority

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId

  • Extract the second numeric ID as taskId

Examples:

  • Change priority: {"projectId": "123", "taskId": "42", "priority": "high"}

  • Replace assignees, keep CC: {"projectId": "123", "taskId": "42", "assignees": [{"id": "user123", "type": "member"}]}

  • Change status: {"projectId": "123", "taskId": "42", "workflowId": "ID from get-project-workflow-list"}

  • Update tags: {"projectId": "123", "taskId": "42", "tagIds": ["tag1", "tag2"]}

  • Clear milestone: {"projectId": "123", "taskId": "42", "milestoneId": null}

  • Set parent task: {"projectId": "123", "taskId": "42", "parentPostId": "99"}

  • Add a CC, keep others: {"projectId": "123", "taskId": "42", "addCc": [{"id": "user456", "type": "member"}]}

  • Add and remove tags: {"projectId": "123", "taskId": "42", "addTagIds": ["tag3"], "removeTagIds": ["tag1"]}

Returns: Updated task. The body is returned as mimeType and contentLength. Use get-task to read the body.

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": {
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "update-task"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoNew complete list of CC recipients (참조). REPLACES all existing CC recipients. Assignees are kept when assignees is not passed. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each CC object has {id: string, type: "member"|"group"|"email"}.
bodyNoNew task body content
addCcNoCC recipients to add, keeping current ones. Cannot be combined with assignees or cc.
tagIdsNoNew complete array of tag IDs. REPLACES all existing tags. IMPORTANT: Check for mandatory tag groups using get-tag-list tool. Projects may require specific tags from mandatory tag groups, or update will fail with 500 error.
taskIdYesTask ID to update
dueDateNoNew due date in ISO 8601 format
subjectNoNew task subject/title
priorityNoTask priority level (highest, high, normal, low, lowest, none)
removeCcNoCC recipients to remove. Cannot be combined with assignees or cc.
addTagIdsNoTag IDs to add, keeping current tags. Cannot be combined with tagIds.
assigneesNoNew complete list of assignees (담당자). REPLACES all existing assignees. CC is kept when cc is not passed. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each assignee object has {id: string, type: "member"|"group"|"email"}.
projectIdYesProject ID where the task belongs
workflowIdNoNew workflow ID (status). Use get-project-workflow-list to see available workflow statuses for this project. Workflow classes: backlog (대기), registered (등록/할 일), working (진행 중), closed (완료).
milestoneIdNoNew milestone ID, or null to remove milestone
addAssigneesNoAssignees to add, keeping current ones. Cannot be combined with assignees or cc.
parentPostIdNoParent task ID to set as parent (상위 업무 설정). Nested hierarchy is NOT allowed: a task that already has sub-tasks cannot be set as a parent.
removeTagIdsNoTag IDs to remove. Cannot be combined with tagIds.
removeAssigneesNoAssignees to remove. Cannot be combined with assignees or cc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • changedInput schema / properties / assignees / description
      Previous value: -"New complete list of assignees (담당자). REPLACES all existing assignees. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each assignee object has {id: string, type: \"member\"|\"group\"|\"email\"}."New value: +"New complete list of assignees (담당자). REPLACES all existing assignees. CC is kept when cc is not passed. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each assignee object has {id: string, type: \"member\"|\"group\"|\"email\"}."
    • changedInput schema / properties / cc / description
      Previous value: -"New complete list of CC recipients (참조). REPLACES all existing CC recipients. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each CC object has {id: string, type: \"member\"|\"group\"|\"email\"}."New value: +"New complete list of CC recipients (참조). REPLACES all existing CC recipients. Assignees are kept when assignees is not passed. To get options: (1) use get-my-member-info for current user, (2) use get-project-member-list for project members, (3) use get-project-member-group-list for member groups. Each CC object has {id: string, type: \"member\"|\"group\"|\"email\"}."
  2. Changed10 schema fields changedv0.2.0
    • addedInput schema / properties / addAssignees
      Added value: +{
      +  "description": "Assignees to add, keeping current ones. Cannot be combined with assignees or cc.",
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "member",
      +          "group",
      +          "email"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / addCc
      Added value: +{
      +  "description": "CC recipients to add, keeping current ones. Cannot be combined with assignees or cc.",
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "member",
      +          "group",
      +          "email"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / addTagIds
      Added value: +{
      +  "description": "Tag IDs to add, keeping current tags. Cannot be combined with tagIds.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / parentPostId
      Added value: +{
      +  "description": "Parent task ID to set as parent (상위 업무 설정). Nested hierarchy is NOT allowed: a task that already has sub-tasks cannot be set as a parent.",
      +  "type": "string"
      +}
    • addedInput schema / properties / removeAssignees
      Added value: +{
      +  "description": "Assignees to remove. Cannot be combined with assignees or cc.",
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "member",
      +          "group",
      +          "email"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / removeCc
      Added value: +{
      +  "description": "CC recipients to remove. Cannot be combined with assignees or cc.",
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "member",
      +          "group",
      +          "email"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / removeTagIds
      Added value: +{
      +  "description": "Tag IDs to remove. Cannot be combined with tagIds.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / taskId
      Added value: +{
      +  "description": "Task ID to update",
      +  "type": "string"
      +}
    • removedInput schema / properties / taskNumber
      Removed value: -{
      -  "description": "Task number to update",
      -  "type": "number"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "taskNumber"
      -]New value: +[
      +  "projectId",
      +  "taskId"
      +]
  3. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag this as a destructive, non-read-only, open-world mutation, and the description adds substantial behavior beyond that: replace-vs-add semantics per field list, the 500 failure when mandatory tag-group tags are dropped, the tagGroup.selectOne constraint, the ban on setting a task with sub-tasks as a parent, and null to clear milestone/priority. It also discloses the return shape limitation (body returned only as mimeType and contentLength).

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

Conciseness4/5

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

Front-loaded with the contract, then organized under bold field headers and a distinct Examples block, so an agent can skim to the relevant field. It is long and repeats a few constraints already encoded in the schema (the add/remove mutual exclusion appears three times), and the example list could be trimmed, but no sentence is actively misleading or wasted.

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

Completeness5/5

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

For an 18-parameter destructive mutation with nested objects and no output schema, the description covers everything needed to call it correctly: defaults/merge semantics, mutual exclusions, prerequisite lookups, failure modes, ID sourcing, and what the response does and does not contain. Nothing material is left for the agent to guess.

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?

Schema coverage is 100%, so the schema already carries per-parameter meaning; the description still adds value by giving the URL-parsing rule that maps a Dooray task URL to projectId and taskId, the Korean term mapping ("to"=담당자, "cc"=참조), the member object format, and the "none" sentinel for priority. Eight worked examples concretize combinations the schema cannot express, though some field prose (e.g., "tagIds REPLACES all tags") restates schema text.

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

Purpose4/5

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

States a specific verb and resource ("Update an existing task in a Dooray project") and enumerates the mutable field groups, so the agent knows exactly the operation's scope. It stops short of naming the sibling it differs from (update-task-body exists in the catalog) — it only hints via "The body is returned as mimeType and contentLength. Use get-task to read the body" — so routing between the two update tools is left partly to inference.

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 the partial-update contract ("Only provide the fields you want to change. Fields you leave out keep their current values, so get-task is not needed first"), which pre-empts the most likely agent error. It also gives mutual-exclusion rules ("Do not combine add/remove options with assignees or cc", addTagIds/removeTagIds vs tagIds) and points to prerequisite tools (get-tag-list, get-project-workflow-list, get-my-member-info, get-project-member-list, get-project-member-group-list).

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