Skip to main content
Glama
nulab

Backlog MCP Server

get_project_list

Retrieve project lists from Backlog to view active, archived, or all projects based on user permissions and filtering criteria.

Instructions

Returns list of projects

Input Schema

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

Implementation Reference

  • Full tool definition including the handler function that executes backlog.getProjects({ archived, all }) to retrieve the project list.
    export const getProjectListTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getProjectListSchema>,
      (typeof ProjectSchema)['shape']
    > => {
      return {
        name: 'get_project_list',
        description: t(
          'TOOL_GET_PROJECT_LIST_DESCRIPTION',
          'Returns list of projects'
        ),
        schema: z.object(getProjectListSchema(t)),
        outputSchema: ProjectSchema,
        importantFields: ['id', 'projectKey', 'name'],
        handler: async ({ archived, all }) =>
          backlog.getProjects({ archived, all }),
      };
    };
  • Input schema definition for the get_project_list tool, defining optional 'archived' and 'all' boolean parameters.
    const getProjectListSchema = buildToolSchema((t) => ({
      archived: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_GET_PROJECT_LIST_ARCHIVED',
            'For unspecified parameters, this form returns all projects. For ‘false’ parameters, it returns unarchived projects. For ‘true’ parameters, it returns archived projects.'
          )
        ),
      all: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_GET_PROJECT_LIST_ALL',
            'Only applies to administrators. If ‘true,’ it returns all projects. If ‘false,’ it returns only projects they have joined.'
          )
        ),
    }));
  • Registration of the get_project_list tool by instantiating getProjectListTool and adding it to the 'project' toolset.
    getProjectListTool(backlog, helper),
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. 'Returns list of projects' implies a read-only operation but doesn't specify permissions, pagination, rate limits, or what 'list' entails (e.g., format, sorting). For a tool with no annotation coverage, this is inadequate transparency about how it behaves.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple list operation. Every word earns its place, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete for a tool with 2 parameters. It doesn't explain return values, error conditions, or behavioral nuances. For a read operation in a system with many sibling tools, more context is needed to help the agent use it correctly.

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 input schema fully documents both parameters ('archived' and 'all'). The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema 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.

Purpose4/5

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

The description 'Returns list of projects' clearly states the verb ('returns') and resource ('list of projects'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other project-related tools like 'get_project' or 'add_project' among the many siblings, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_project' (singular) and 'get_issues' (for issues within projects), there's no indication of context, prerequisites, or exclusions. This leaves the agent guessing about appropriate usage scenarios.

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