Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-project-template

Creates reusable task templates in a Dooray project with predefined subject, body, assignees, tags, priority, and due date to standardize task creation.

Instructions

Create a new task template in a Dooray project.

Templates are pre-created task structures that help users quickly create tasks with predefined content.

Required Field:

  • templateName: The name of the template

Optional Fields:

  • users: Default assignees (to) and CC recipients

  • body: Default task body content (markdown or HTML)

  • guide: Instructions shown when creating tasks from this template

  • subject: Default task subject/title

  • dueDate: Default due date (ISO 8601 format)

  • dueDateFlag: Whether due date is enabled

  • milestoneId: Default milestone

  • tagIds: Default tags

  • priority: Default priority (highest, high, normal, low, lowest, none)

  • isDefault: Set as default template (auto-fills when creating new tasks)

Due Date Flags:

  • dueDateFlag: false → No schedule

  • dueDateFlag: true, dueDate: null → Schedule exists but date is TBD

  • dueDateFlag: true, dueDate: "2024-01-15T12:00:00+09:00" → Schedule with specific date

Examples:

  • Simple template: {"projectId": "123", "templateName": "Bug Report"}

  • With body: {"projectId": "123", "templateName": "Feature Request", "body": {"mimeType": "text/x-markdown", "content": "## Description\n\n## Expected Behavior\n\n## Steps to Reproduce"}}

  • With defaults: {"projectId": "123", "templateName": "Sprint Task", "priority": "normal", "tagIds": ["tag1"], "isDefault": true}

Returns the created template ID.

Input Schema

NameRequiredDescriptionDefault
bodyNoDefault task body content
guideNoGuide content shown when creating tasks
usersNoDefault users for tasks created from this template
tagIdsNoDefault tag IDs
dueDateNoDefault due date (ISO 8601 format)
subjectNoDefault task subject
priorityNoDefault priority
isDefaultNoSet as default template for this project
projectIdYesProject ID where the template will be created
dueDateFlagNoEnable due date
milestoneIdNoDefault milestone ID
templateNameYesTemplate name (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare write/non-destructive/open-world behavior. The description adds meaningful behavior beyond that: dueDateFlag state combinations, defaulting semantics, and that the created template ID is returned. It omits permission/auth requirements and uniqueness constraints, so it is strong but not complete.

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?

The description is front-loaded with purpose, then organized into required fields, optional fields, due-date flag rules, and examples. Some bullets repeat schema field descriptions, but the structure is appropriate for a 12-parameter tool with nested objects.

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 no output schema, the description usefully states that the created template ID is returned. It covers required and optional fields, due-date edge cases, and examples. It does not cover permission requirements, possible errors, or template-name uniqueness, but is complete enough for correct invocation.

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 baseline is 3. The description adds real semantics beyond the schema, especially the dueDateFlag combinations, priority values, body/guide mime types, and usage examples. Nested users object details are left to 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 states a specific verb and resource: 'Create a new task template in a Dooray project.' The word 'new' distinguishes it from update/delete/list template siblings, and the template definition adds useful context.

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

Usage Guidelines3/5

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

It explains what templates are and gives examples, implying when the tool is useful. However, it does not explicitly say when to use this versus update-project-template or get-project-template, nor does it state when-not conditions, so usage guidance is only implied.

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