Skip to main content
Glama
nulab

Backlog MCP Server

add_issue

Create a new issue in a Backlog project by specifying project ID, summary, issue type, priority, and optional details like dates, assignee, and custom fields.

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
organizationNoOptional organization name. Use list_organizations to inspect available organizations.
Behavior2/5

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

No annotations provided; description only states 'creates' without disclosing behavioral traits like side effects, permissions, or error handling.

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?

Single sentence with no unnecessary content. Efficient and front-loaded.

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 18 parameters and no output schema/annotations, description is too minimal. Lacks return value, error conditions, and usage 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 provides detailed descriptions for all 18 parameters (100% coverage). Description adds no additional meaning beyond what schema already conveys.

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?

Description clearly states it creates a new issue in a specified project, which distinguishes it from sibling tools like add_issue_comment or update_issue.

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 on when to use versus alternatives like update_issue or delete_issue, nor prerequisites or context.

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