Skip to main content
Glama
Sign In
Backlog MCP Server

Backlog MCP Server

by nulab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_project_list

Read-only

Retrieves a list of Backlog projects, letting you filter by archived status or view all projects when administrator permissions allow.

Instructions

Returns list of projects

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoOnly applies to administrators. If ‘true,’ it returns all projects. If ‘false,’ it returns only projects they have joined.
archivedNoFor unspecified parameters, this form returns all projects. For ‘false’ parameters, it returns unarchived projects. For ‘true’ parameters, it returns archived projects.

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.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds nothing beyond that — no mention that the result set depends on admin status or archived state, which is the key behavioral nuance of this tool.

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 single sentence is front-loaded and free of waste, but it is under-specified rather than concise — it stops well short of what an agent needs. Brevity here reflects thin content, not efficiency.

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 list tool with no output schema, the description says nothing about what a returned project contains, ordering, pagination, or how the default call behaves (joined projects only). Against 60+ siblings including get_project, this leaves the agent guessing.

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%, and the schema itself explains the 'all' and 'archived' semantics thoroughly, including defaults. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 a specific verb ('Returns') and resource ('list of projects'), so the basic purpose is recoverable. However, with siblings like get_project (singular) and get_project_users present, it offers no differentiation — an agent cannot tell from the text alone how this list differs from fetching a single project.

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 call this versus get_project or get_project_users, and no mention of prerequisites such as admin rights implied by the 'all' parameter. The agent gets no selection criteria at all.

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