Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_add_issue

Add a new issue to a Backlog project by specifying details like project ID, summary, issue type, and priority. Streamlines task creation for efficient project management.

Instructions

Add an issue using the Backlog Issue API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actualHoursNoActual hours for the issue
assigneeIdNoAssignee id
categoryIdNoCategory id
descriptionNoDescription of the issue
dueDateNoDue date of the issue (YYYY-MM-DD format)
estimatedHoursNoEstimated hours for the issue
issueTypeIdYesIssue type id
milestoneIdNoMilestone id
priorityIdYesPriority id
projectIdYesProject id
startDateNoStart date of the issue (YYYY-MM-DD format)
summaryYesSummary of the issue
versionIdNoVersion id

Implementation Reference

  • The handler function that executes the backlog_add_issue tool: validates input parameters using AddIssueParamsSchema and calls issueService.addIssue to perform the operation.
    const handleAddIssue: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = AddIssueParamsSchema.parse(args);
    
    			const text = await issueService.addIssue(validatedParams);
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Results for your query:\n${text}`,
    					},
    				],
    				isError: false,
    			};
    		} catch (validationError) {
    			throw new ValidationError(
    				`Invalid parameters: ${validationError instanceof Error ? validationError.message : String(validationError)}`,
    			);
    		}
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: "text",
    					text: `Error: ${formatError(error)}`,
    				},
    			],
    			isError: true,
    		};
    	}
    };
  • Registers the backlog_add_issue tool name to its handler function handleAddIssue in the toolHandlers map, used by the MCP server.
    export const toolHandlers: Record<ToolName, ToolHandler> = {
    	backlog_get_projects: handleGetProjects,
    	backlog_get_project: handleGetProject,
    	backlog_get_issues: handleGetIssues,
    	backlog_get_issue: handleGetIssue,
    	backlog_add_issue: handleAddIssue,
    	backlog_update_issue: handleUpdateIssue,
    	backlog_delete_issue: handleDeleteIssue,
    	backlog_get_wikis: handleGetWikis,
    	backlog_get_wiki: handleGetWiki,
    	backlog_add_wiki: handleAddWiki,
    	backlog_update_wiki: handleUpdateWiki,
    	backlog_delete_wiki: handleDeleteWiki,
    };
  • Zod schema defining the input parameters for the backlog_add_issue tool, used for validation.
    export const AddIssueParamsSchema = z.object({
    	projectId: z.number().int().describe("Project id"),
    	summary: z.string().describe("Summary"),
    	parentIssueId: z.number().int().optional().describe("Parent issue id"),
    	description: z.string().optional().describe("Description"),
    	startDate: z.string().optional().describe("Start date"),
    	dueDate: z.string().optional().describe("Due date"),
    	estimatedHours: z.number().optional().describe("Estimated hours"),
    	actualHours: z.number().optional().describe("Actual hours"),
    	issueTypeId: z.number().int().describe("Issue type id"),
    	categoryId: z.array(z.number()).optional().describe("Category ids"),
    	versionId: z.array(z.number()).optional().describe("Version ids"),
    	milestoneId: z.array(z.number()).optional().describe("Milestone ids"),
    	priorityId: z.number().int().describe("Priority id"),
    	assigneeId: z.number().int().optional().describe("Assignee id"),
    	notifiedUserId: z.array(z.number()).optional().describe("Notified user ids"),
    	attachmentId: z.array(z.number()).optional().describe("Attachment ids"),
    });
  • Defines the MCP Tool object for backlog_add_issue, including name, description, and input schema converted from Zod schema.
    export const ADD_ISSUE_TOOL: Tool = createTool(
    	"backlog_add_issue",
    	"Add an issue using the Backlog Issue API.",
    	AddIssueParamsSchema,
    );
  • TypeScript union type ToolName that includes "backlog_add_issue" for type safety.
    export type ToolName =
    	| "backlog_get_projects"
    	| "backlog_get_project"
    	| "backlog_get_issues"
    	| "backlog_get_issue"
    	| "backlog_add_issue"
    	| "backlog_update_issue"
    	| "backlog_delete_issue"
    	| "backlog_get_wikis"
    	| "backlog_get_wiki"
    	| "backlog_add_wiki"
    	| "backlog_update_wiki"
    	| "backlog_delete_wiki";

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but fails to disclose any behavioral traits (e.g., side effects, authentication needs, idempotency). Merely stating 'Add an issue' gives no insight into what the tool does beyond the obvious.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but not front-loaded with key details. It lacks structure or prioritization of information, though it is not verbose.

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?

Given 13 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the tool's behavior, return value, or the context needed to use it effectively.

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 baseline is 3. The description adds no extra meaning beyond what the schema already provides, but it does not harm. Credit for having all parameters documented in schema.

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 'Add an issue' which conveys the verb and resource. However, it does not differentiate from sibling tools like backlog_update_issue, which could cause confusion for the agent.

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, such as when to create vs update an issue. This lack of usage context forces the agent to rely solely on the tool name and parameters.

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

Related Tools