Skip to main content
Glama
Sign In
Backlog MCP Server

Backlog MCP Server

by nulab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_project

Create a new Backlog project by specifying its name and key, with optional settings for charts, subtasking, text formatting, and project leader permissions.

Instructions

Creates a new project

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.1
  2. Removedv0.13.1
  3. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "Optional organization name. Use list_organizations to inspect available organizations.",
+  "type": "string"
+}
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it doesn't mention that repeated calls with the same key may fail, what gets created (default settings), or auth requirements for a mutation tool.

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

Conciseness4/5

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

A single front-loaded sentence with zero waste, though it borders on under-specification rather than tightness. Nothing is padded, but there is also almost nothing there.

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 six-parameter creation tool with no output schema, the description leaves key gaps: it doesn't say what is returned (e.g., the new project's identifier needed for subsequent calls) or what constraints apply to the required key. Annotations cover the safety profile only, so the description should carry more of the load here.

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 all six parameters including the required name/key pair and defaults for chartEnabled, subtaskingEnabled, and textFormattingRule are already documented. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ("Creates a new project"), which unambiguously tells the agent this is the create operation for projects. It doesn't explicitly contrast with update_project or get_project_list, but the name plus phrasing already make the distinction obvious.

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?

There is no guidance on when to use this versus alternatives, no prerequisites (permissions, existing project keys, space selection), and no note about what to do if the key already exists. The agent must infer everything from the one-line purpose.

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