Skip to main content
Glama

create-task

Creates a new task in a Dooray project, letting users save it immediately or as a draft, and set assignees, tags, priority, due date, or subtask details.

Instructions

Create a new task (업무) in a Dooray project. Required: projectId, subject.

DRAFT vs REGULAR: ASK USER which type to create:

  • Draft (isDraft: true): Returns URL to continue editing in browser. Use for complex tasks or when user wants to review.

  • Regular (isDraft: false, default): Saves immediately. Use when all info is available.

INTERACTIVE WORKFLOW:

  1. Templates: Ask about get-project-template-list. If yes, use get-project-template for defaults.

  2. Content: Get subject and body. If no template and no body, ask user for details.

  3. Assignees/CC: Use get-my-member-info, get-project-member-list, or get-project-member-group-list. Format: {id, type: "member|group|email"}

  4. Tags: Call get-tag-list. CRITICAL: Check mandatory tag groups - must select or creation fails (500 error). selectOne=true requires exactly ONE tag from group.

Key Points:

Examples:

  • Draft: {"projectId": "123", "subject": "Bug fix", "isDraft": true}

  • Regular: {"projectId": "123", "subject": "Deploy", "assignees": [{"id": "user1", "type": "member"}], "tagIds": ["tag1"], "priority": "high"}

Returns: {id} (regular) or {id, url, message} (draft). For taskNumber, call get-task with includeBody false.

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>",
      "subject": "<subject>"
    },
    "name": "create-task"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoList of CC recipients (참조). To get CC 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"}.
bodyNoTask body with formatted content. IMPORTANT: If user has not provided body content and no template is selected, ask the user for task details/description before creating the task.
tagIdsNoArray of tag IDs to apply to this task. IMPORTANT: Check for mandatory tag groups using get-tag-list tool. Projects may require specific tags from mandatory tag groups.
dueDateNoDue date in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ)
isDraftNoSet to true to create a draft task (임시 업무) that can be continued in the browser. Returns a URL for further editing. Default: false (creates regular task).
subjectYesTask subject/title (required)
priorityNoTask priority level (highest, high, normal, low, lowest, none). Default: "none" if not specified by user.
assigneesNoList of assignees (담당자). To get assignee 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 will be created
milestoneIdNoMilestone ID to associate with this task
parentPostIdNoParent task ID to create this as a subtask (하위업무). Omit to create a regular task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / isDraft
      Added value: +{
      +  "description": "Set to true to create a draft task (임시 업무) that can be continued in the browser. Returns a URL for further editing. Default: false (creates regular task).",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true; the description adds real behavioral context beyond them: mandatory tag groups cause a 500 error if unsatisfied, selectOne=true requires exactly one tag, draft returns a URL while regular saves immediately, and priority defaults to "none". It even documents the return shape ({id} vs {id, url, message}) despite no output schema.

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 core verb, then segmented into DRAFT vs REGULAR, WORKFLOW, Key Points, Examples, and Returns — easy to scan. It is somewhat long and a few lines (assignee format, tag list) duplicate the schema, but nearly every section carries actionable information.

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 11-parameter tool with nested objects and no output schema, the description covers mode selection, prerequisite lookups, error conditions, defaults, subtask semantics, and return values. An agent has everything needed to invoke it correctly without opening other resources.

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 documents all 11 parameters; the description still adds meaning beyond it — the priority default when unspecified, parentPostId as the subtask (하위업무) mechanism, and a practical tip to extract PROJECT_ID from Dooray URLs. The assignee/tag guidance largely restates the schema, keeping this just under a 5.

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?

Opens with a specific verb+resource ("Create a new task (업무) in a Dooray project") and immediately splits the operation into draft vs regular modes, which lets an agent distinguish it from update-task and other siblings. The scope and the two creation modes are stated up front rather than buried.

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?

Gives an explicit when-to-use for each mode (draft for complex tasks or review, regular when all info is available) and a step-by-step interactive workflow that names concrete alternatives: get-project-template-list, get-project-template, get-my-member-info, get-project-member-list, get-project-member-group-list, and get-tag-list. It also states when-not/required behavior (must ask user which type; must ask for body if none).

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