Skip to main content
Glama
nulab

Backlog MCP Server

add_issue

Create new issues in Backlog projects with details like summary, priority, dates, assignees, and custom fields for project management.

Instructions

Creates a new issue in the specified project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
summaryYesSummary of the issue
issueTypeIdYesIssue type ID
priorityIdYesPriority ID
descriptionNoCreates a new issue in the specified project.
startDateNoScheduled start date (yyyy-MM-dd)
dueDateNoScheduled due date (yyyy-MM-dd)
estimatedHoursNoEstimated work hours
actualHoursNoActual work hours
categoryIdNoCategory IDs
versionIdNoVersion IDs
milestoneIdNoMilestone IDs
assigneeIdNoUser ID of the assignee
notifiedUserIdNoUser IDs to notify
attachmentIdNoAttachment IDs
parentIssueIdNoParent issue ID
customFieldsNoList of custom fields to set on the issue

Implementation Reference

  • The handler function for the 'add_issue' tool that processes the input parameters including custom fields and calls the Backlog API to create a new issue.
    handler: async ({ customFields, ...params }) => {
      const customFieldPayload = customFieldsToPayload(customFields);
    
      const finalPayload = {
        ...params,
        ...customFieldPayload,
      };
    
      return backlog.postIssue(finalPayload);
    },
  • Input schema definition for the 'add_issue' tool using Zod, defining all parameters like projectId, summary, issueTypeId, etc., including custom fields.
    const addIssueSchema = buildToolSchema((t) => ({
      projectId: z.number().describe(t('TOOL_ADD_ISSUE_PROJECT_ID', 'Project ID')),
      summary: z
        .string()
        .describe(t('TOOL_ADD_ISSUE_SUMMARY', 'Summary of the issue')),
      issueTypeId: z
        .number()
        .describe(t('TOOL_ADD_ISSUE_ISSUE_TYPE_ID', 'Issue type ID')),
      priorityId: z
        .number()
        .describe(t('TOOL_ADD_ISSUE_PRIORITY_ID', 'Priority ID')),
      description: z
        .string()
        .optional()
        .describe(
          t('TOOL_ADD_ISSUE_DESCRIPTION', 'Detailed description of the issue')
        ),
      startDate: z
        .string()
        .optional()
        .describe(
          t('TOOL_ADD_ISSUE_START_DATE', 'Scheduled start date (yyyy-MM-dd)')
        ),
      dueDate: z
        .string()
        .optional()
        .describe(t('TOOL_ADD_ISSUE_DUE_DATE', 'Scheduled due date (yyyy-MM-dd)')),
      estimatedHours: z
        .number()
        .optional()
        .describe(t('TOOL_ADD_ISSUE_ESTIMATED_HOURS', 'Estimated work hours')),
      actualHours: z
        .number()
        .optional()
        .describe(t('TOOL_ADD_ISSUE_ACTUAL_HOURS', 'Actual work hours')),
      categoryId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_ADD_ISSUE_CATEGORY_ID', 'Category IDs')),
      versionId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_ADD_ISSUE_VERSION_ID', 'Version IDs')),
      milestoneId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_ADD_ISSUE_MILESTONE_ID', 'Milestone IDs')),
      assigneeId: z
        .number()
        .optional()
        .describe(t('TOOL_ADD_ISSUE_ASSIGNEE_ID', 'User ID of the assignee')),
      notifiedUserId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_ADD_ISSUE_NOTIFIED_USER_ID', 'User IDs to notify')),
      attachmentId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_ADD_ISSUE_ATTACHMENT_ID', 'Attachment IDs')),
      parentIssueId: z
        .number()
        .optional()
        .describe(t('TOOL_ADD_ISSUE_PARENT_ISSUE_ID', 'Parent issue ID')),
      customFields: z
        .array(
          z.object({
            id: z
              .number()
              .describe(
                t(
                  'TOOL_ADD_ISSUE_CUSTOM_FIELD_ID',
                  'The ID of the custom field (e.g., 12345)'
                )
              ),
            value: z
              .union([z.number(), z.array(z.number())])
              .optional()
              .describe(
                'The ID(s) of the custom field item. For single-select fields, provide a number. For multi-select fields, provide an array of numbers representing the selected item IDs.'
              ),
            otherValue: z
              .string()
              .optional()
              .describe(
                t(
                  'TOOL_ADD_ISSUE_CUSTOM_FIELD_OTHER_VALUE',
                  'Other value for list type fields'
                )
              ),
          })
        )
        .optional()
        .describe(
          t(
            'TOOL_ADD_ISSUE_CUSTOM_FIELDS',
            'List of custom fields to set on the issue'
          )
        ),
    }));
  • Registration of the 'add_issue' tool within the 'issue' toolset group returned by allTools.
    addIssueTool(backlog, helper),
  • Tool schema usage: input schema from addIssueSchema and output schema as IssueSchema.
    schema: z.object(addIssueSchema(t)),
    outputSchema: IssueSchema,
  • The 'issue' toolset group where the add_issue tool is registered as part of the tools array.
    {
      name: 'issue',
      description: 'Tools for managing issues and their comments.',
      enabled: false,
      tools: [
        getIssueTool(backlog, helper),
        getIssuesTool(backlog, helper),
        countIssuesTool(backlog, helper),
        addIssueTool(backlog, helper),
        updateIssueTool(backlog, helper),
        deleteIssueTool(backlog, helper),
        getIssueCommentsTool(backlog, helper),
        addIssueCommentTool(backlog, helper),
        getPrioritiesTool(backlog, helper),
        getCategoriesTool(backlog, helper),
        getCustomFieldsTool(backlog, helper),
        getIssueTypesTool(backlog, helper),
        getResolutionsTool(backlog, helper),
        getWatchingListItemsTool(backlog, helper),
        getWatchingListCountTool(backlog, helper),
        addWatchingTool(backlog, helper),
        updateWatchingTool(backlog, helper),
        deleteWatchingTool(backlog, helper),
        markWatchingAsReadTool(backlog, helper),
        getVersionMilestoneListTool(backlog, helper),
        addVersionMilestoneTool(backlog, helper),
        updateVersionMilestoneTool(backlog, helper),
        deleteVersionTool(backlog, helper),
      ],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention whether it requires authentication, what happens on success/failure, if there are rate limits, or what the return value looks like. For a mutation tool with 17 parameters, this leaves significant behavioral gaps.

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

Conciseness5/5

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

The description is a single, direct sentence that states exactly what the tool does without any unnecessary words. It's perfectly front-loaded and wastes no space, making it highly efficient for an AI agent to parse.

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

Completeness2/5

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

For a complex creation tool with 17 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation, what values are returned, error conditions, or behavioral constraints. The agent must rely entirely on the input schema without guidance on the tool's broader context.

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 description coverage is 100%, so the schema already documents all 17 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, but with complete schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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?

The description clearly states the action ('Creates') and resource ('new issue in the specified project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'update_issue' or 'delete_issue' beyond the basic verb, missing explicit sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'update_issue' or 'delete_issue', nor does it mention prerequisites such as required permissions or project existence. It lacks any context about when this tool is appropriate versus other issue-related operations.

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/nulab/backlog-mcp-server'

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