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";
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Add an issue' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about authentication requirements, rate limits, whether the operation is idempotent, what happens on success/failure, or what the response contains. This is a significant gap for a mutation tool with zero annotation coverage.

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 extremely concise at just one sentence with zero wasted words. It's front-loaded with the core purpose and contains no unnecessary information. This is an example of appropriate brevity for a tool where the schema provides comprehensive parameter documentation.

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 this is a mutation tool with 13 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after adding an issue, what the return value might be, error conditions, or behavioral constraints. The description provides minimal context for a complex creation operation.

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 13 parameters with clear descriptions. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Add an issue using the Backlog Issue API' which provides a clear verb ('Add') and resource ('issue'), but it's vague about what 'issue' means in this context and doesn't distinguish it from sibling tools like backlog_add_wiki. It doesn't specify whether this creates a bug report, task, or other work item type.

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?

No guidance is provided about when to use this tool versus alternatives. With siblings like backlog_get_issue, backlog_update_issue, and backlog_delete_issue, the description offers no indication of when creation is appropriate versus retrieval, modification, or deletion. There's no mention of prerequisites or typical use cases.

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

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

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