Skip to main content
Glama

get-project-template

Retrieve complete project template details including body, guide, subject, users, tags, and milestone to create new tasks from templates in Dooray.

Instructions

Get detailed information about a specific project template.

This tool retrieves complete template details including body, guide, subject, users, tags, and milestone. The returned data is intended for creating new tasks from templates.

IMPORTANT - Full Details Returned: This tool returns ALL template fields (not filtered) because:

  • Template data will be used for creating new tasks

  • Need body, guide, subject, users, tags, milestone for task creation

  • This is a detail view, not a list view

Template Macros: Template macros like ${year}, ${month}, etc. are returned as-is (not interpolated). These can be processed when creating tasks if needed.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

How to get template IDs: Use the get-project-template-list tool to list all templates in a project and get their IDs.

Examples:

  • Get template details: {"projectId": "123456", "templateId": "789012"}

  • "Show me details of template 789012 in project 123456"

Returns complete template information including:

  • id: Template ID

  • templateName: Template name

  • project: Project info (id, code)

  • body: Template body with mimeType and content (markdown or HTML)

  • guide: Template guide/instructions with mimeType and content

  • subject: Default task subject

  • users: Default assignees (to) and CC

  • tags: Default tag IDs

  • milestone: Default milestone (id, name)

  • priority: Default priority level

  • dueDate, dueDateFlag: Default due date settings

  • isDefault: Whether this is the default template

Use this tool to get full template details before creating a new task from the template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID where the template belongs
templateIdYesTemplate ID to retrieve

Implementation Reference

  • The main tool handler that fetches the project template details via API and returns JSON-formatted result or error response.
    export async function getProjectTemplateHandler(args: GetProjectTemplateInput) {
      try {
        const result = await projectsApi.getProjectTemplate({
          projectId: args.projectId,
          templateId: args.templateId,
        });
    
        // Return FULL template (no filtering) - needed for task creation
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${formatError(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for validating tool inputs: projectId and templateId.
    export const getProjectTemplateSchema = z.object({
      projectId: z.string().describe('Project ID where the template belongs'),
      templateId: z.string().describe('Template ID to retrieve'),
    });
  • Tool specification object used for listing the tool in MCP, including name, detailed description, and input schema.
    export const getProjectTemplateTool = {
      name: 'get-project-template',
      description: `Get detailed information about a specific project template.
    
    This tool retrieves complete template details including body, guide, subject, users, tags, and milestone. The returned data is intended for creating new tasks from templates.
    
    **IMPORTANT - Full Details Returned**:
    This tool returns ALL template fields (not filtered) because:
    - Template data will be used for creating new tasks
    - Need body, guide, subject, users, tags, milestone for task creation
    - This is a detail view, not a list view
    
    **Template Macros**:
    Template macros like \${year}, \${month}, etc. are returned as-is (not interpolated). These can be processed when creating tasks if needed.
    
    **URL Pattern Recognition**:
    When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.
    
    **How to get template IDs**:
    Use the \`get-project-template-list\` tool to list all templates in a project and get their IDs.
    
    Examples:
    - Get template details: {"projectId": "123456", "templateId": "789012"}
    - "Show me details of template 789012 in project 123456"
    
    Returns complete template information including:
    - **id**: Template ID
    - **templateName**: Template name
    - **project**: Project info (id, code)
    - **body**: Template body with mimeType and content (markdown or HTML)
    - **guide**: Template guide/instructions with mimeType and content
    - **subject**: Default task subject
    - **users**: Default assignees (to) and CC
    - **tags**: Default tag IDs
    - **milestone**: Default milestone (id, name)
    - **priority**: Default priority level
    - **dueDate**, **dueDateFlag**: Default due date settings
    - **isDefault**: Whether this is the default template
    
    Use this tool to get full template details before creating a new task from the template.`,
      inputSchema: {
        type: 'object',
        properties: {
          projectId: {
            type: 'string',
            description: 'Project ID where the template belongs',
          },
          templateId: {
            type: 'string',
            description: 'Template ID to retrieve',
          },
        },
        required: ['projectId', 'templateId'],
      },
    };
  • src/index.ts:60-60 (registration)
    Registers the tool's handler and schema in the central toolRegistry for call_tool requests.
    'get-project-template': { handler: getProjectTemplateHandler, schema: getProjectTemplateSchema },
  • src/index.ts:83-83 (registration)
    Adds the tool specification to the tools array returned in list_tools requests.
    getProjectTemplateTool,
Behavior4/5

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

With no annotations provided, the description carries full burden and does so effectively. It discloses important behavioral traits: 'returns ALL template fields (not filtered)', explains why ('Template data will be used for creating new tasks'), describes template macro handling ('returned as-is, not interpolated'), and explains URL pattern recognition for parameter extraction. It doesn't mention error conditions or rate limits, but provides substantial behavioral context.

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 well-structured with clear sections (purpose, important details, macros, URL patterns, how to get IDs, examples, return fields, usage guidance). While somewhat lengthy, each section adds value. The front-loaded purpose statement is clear, and the information is organized for easy scanning.

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?

Given the tool's complexity (retrieving detailed template data for task creation), no annotations, and no output schema, the description provides excellent completeness. It explains the purpose, usage context, behavioral details, parameter guidance, relationship to sibling tools, and comprehensively lists all return fields with explanations of their significance for task creation.

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?

The input schema has 100% description coverage, so baseline is 3. The description adds significant value beyond the schema by explaining 'URL Pattern Recognition' - how to extract projectId from Dooray URLs, and providing concrete examples of parameter usage. It also clarifies the relationship between parameters and template identification.

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 the tool's purpose: 'Get detailed information about a specific project template' and 'retrieves complete template details'. It distinguishes from its sibling 'get-project-template-list' by specifying this is a detail view, not a list view, and explicitly mentions the sibling tool for obtaining template IDs.

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?

The description provides explicit usage guidance: 'Use this tool to get full template details before creating a new task from the template' and 'Use the `get-project-template-list` tool to list all templates in a project and get their IDs'. It clearly states when to use this tool versus the sibling list tool and connects it to task creation workflows.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jhl8041/dooray-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server