Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-task

Create a new Dooray project task as a draft for review or save it immediately with assignees, tags, priority, and due date.

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: Task object (regular) or {id, url, message} (draft).

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.3/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: draft creation returns a URL instead of persisting, mandatory tag groups cause a 500 error if unsatisfied, and selectOne groups require exactly one tag. This is high-value failure-mode disclosure, though permission/auth requirements and whether creation is reversible are not addressed.

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-loads purpose and required params, then uses bolded sections and numbered steps so structure is easy to scan. It is somewhat long and repeats the assignee/tag guidance that also lives in the schema, but every block is functional.

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?

For an 11-parameter, nested-object creation tool with no output schema, the description supplies the draft/regular return shapes and the critical tag-prerequisite rule. Remaining gaps (auth, error handling beyond the 500 note) are minor given the rich schema.

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

Parameters3/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 every parameter including the assignee/CC object shape and enum values. The description adds only a marginal detail (extracting projectId from a Dooray URL) plus priority defaulting, which is already in the schema — baseline 3 is appropriate.

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 names the two required parameters. It is trivially distinguishable from siblings like update-task, create-task-comment, and get-task.

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 tells the agent to ask the user whether to create a draft vs. regular task and gives the conditions for each. It also enumerates a step-by-step interactive workflow with named prerequisite tools (get-project-template, get-tag-list, get-my-member-info), so when-to-use and when-not-to-use are both covered.

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

Deploy Server

Other Tools