Skip to main content
Glama
deenesjakoruzh
nulab

Backlog MCP Server

by nulab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

add_project

Create new projects in Backlog by specifying name, key, and configuration options like chart display, subtasking, and text formatting rules.

Instructions

Creates a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
keyYesProject key
chartEnabledNoWhether to enable chart (default: false)
subtaskingEnabledNoWhether to enable subtasking (default: false)
projectLeaderCanEditProjectLeaderNoWhether project leaders can edit other project leaders (default: false)
textFormattingRuleNoText formatting rule (default: 'backlog')

Implementation Reference

  • src/tools/addProject.ts:60-76 (handler)
    The async handler function that executes the tool logic by calling backlog.postProject with the validated input parameters to create a new project.
    handler: async ({
  name,
  key,
  chartEnabled,
  subtaskingEnabled,
  projectLeaderCanEditProjectLeader,
  textFormattingRule,
}) =>
  backlog.postProject({
    name,
    key,
    chartEnabled: chartEnabled ?? false,
    subtaskingEnabled: subtaskingEnabled ?? false,
    projectLeaderCanEditProjectLeader:
      projectLeaderCanEditProjectLeader ?? false,
    textFormattingRule: textFormattingRule ?? 'backlog',
  }),
  • src/tools/addProject.ts:7-46 (schema)
    Zod-based input schema for the 'add_project' tool, defining required name and key, and optional boolean flags and text formatting rule.
    const addProjectSchema = buildToolSchema((t) => ({
  name: z.string().describe(t('TOOL_ADD_PROJECT_NAME', 'Project name')),
  key: z.string().describe(t('TOOL_ADD_PROJECT_KEY', 'Project key')),
  chartEnabled: z
    .boolean()
    .optional()
    .describe(
      t(
        'TOOL_ADD_PROJECT_CHART_ENABLED',
        'Whether to enable chart (default: false)'
      )
    ),
  subtaskingEnabled: z
    .boolean()
    .optional()
    .describe(
      t(
        'TOOL_ADD_PROJECT_SUBTASKING_ENABLED',
        'Whether to enable subtasking (default: false)'
      )
    ),
  projectLeaderCanEditProjectLeader: z
    .boolean()
    .optional()
    .describe(
      t(
        'TOOL_ADD_PROJECT_LEADER_CAN_EDIT',
        'Whether project leaders can edit other project leaders (default: false)'
      )
    ),
  textFormattingRule: z
    .enum(['backlog', 'markdown'])
    .optional()
    .describe(
      t(
        'TOOL_ADD_PROJECT_TEXT_FORMATTING',
        "Text formatting rule (default: 'backlog')"
      )
    ),
}));
  • src/tools/tools.ts:81-86 (registration)
    Registration of the addProjectTool within the 'project' toolset group in the allTools function, alongside other project management tools.
      getProjectListTool(backlog, helper),
  addProjectTool(backlog, helper),
  getProjectTool(backlog, helper),
  updateProjectTool(backlog, helper),
  deleteProjectTool(backlog, helper),
],

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Creates a new project' implies a write operation, but it doesn't disclose any behavioral traits such as required permissions, whether the creation is idempotent, potential side effects (e.g., affecting other resources), rate limits, or what the response looks like (since no output schema exists). This leaves significant gaps for an agent to understand the tool's behavior.

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 'Creates a new project' is extremely concise—a single sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without unnecessary elaboration.

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 the complexity (a creation tool with 6 parameters, 2 required), no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions or side effects, provide usage context, or hint at return values. For a mutation tool with rich parameters, 'Creates a new project' is too minimal to be fully helpful to an agent.

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%, meaning all parameters are documented in the input schema with descriptions. The tool description adds no additional meaning beyond the schema (e.g., it doesn't explain relationships between parameters like 'key' and 'name', or provide usage examples). According to the rules, with high schema coverage, the baseline is 3 even without param info in the description, which applies here.

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 'Creates a new project' clearly states the action (creates) and resource (project), which is adequate. However, it doesn't differentiate from sibling tools like 'add_issue' or 'add_version_milestone' that also create resources, nor does it specify what constitutes a 'project' in this context beyond the basic verb+resource pairing.

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 on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., permissions needed), when not to use it (e.g., for updating existing projects, where 'update_project' exists), or how it relates to other creation tools in the sibling list. The description is purely functional without contextual advice.

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