Skip to main content
Glama

List Projects

list_projects

Retrieve a list of accessible Codebeamer projects, including IDs, names, and keys. Use project IDs to fetch trackers or items.

Instructions

List all Codebeamer projects the authenticated user can access. Returns a summary table with project IDs, names, and keys. Use the returned IDs to fetch trackers or items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starts at 1)
pageSizeNoItems per page (max 100)

Implementation Reference

  • Registration of the 'list_projects' tool with McpServer. The handler calls client.listProjects() and formats the result via formatProjectList().
    server.registerTool(
      "list_projects",
      {
        title: "List Projects",
        description:
          "List all Codebeamer projects the authenticated user can access. " +
          "Returns a summary table with project IDs, names, and keys. " +
          "Use the returned IDs to fetch trackers or items.",
        inputSchema: {
          page: z
            .number()
            .int()
            .min(1)
            .default(1)
            .describe("Page number (starts at 1)"),
          pageSize: z
            .number()
            .int()
            .min(1)
            .max(100)
            .default(25)
            .describe("Items per page (max 100)"),
        },
      },
      async ({ page, pageSize }) => {
        const result = await client.listProjects(page, pageSize);
        return { content: [{ type: "text", text: formatProjectList(result) }] };
      },
    );
  • Input schema for 'list_projects' using Zod: page (default 1, min 1) and pageSize (default 25, max 100).
    inputSchema: {
      page: z
        .number()
        .int()
        .min(1)
        .default(1)
        .describe("Page number (starts at 1)"),
      pageSize: z
        .number()
        .int()
        .min(1)
        .max(100)
        .default(25)
        .describe("Items per page (max 100)"),
    },
  • src/index.ts:38-38 (registration)
    Where registerProjectTools is called in the main entry point to set up the tool on the server.
    registerProjectTools(server, client);
  • Client method listProjects() that makes an HTTP GET request to /projects and converts the response to an array of CbProject objects.
    async listProjects(page: number, pageSize: number): Promise<CbProject[]> {
      const raw = await this.http.get<unknown>("/projects", {
        params: { page, pageSize },
        resource: "projects",
      });
      return toArray(raw);
    }
  • Formatting helper formatProjectList() that converts an array of CbProject objects into a markdown table string.
    export function formatProjectList(projects: CbProject[]): string {
      const header = `## Projects (${projects.length} total)\n`;
    
      if (projects.length === 0) return `${header}\n_No projects found._`;
    
      const rows = projects.map(
        (p) =>
          `| ${p.id} | ${p.name} | ${p.keyName ?? "-"} | ${p.closed ? "Closed" : "Open"} |`,
      );
    
      return [
        header,
        "| ID | Name | Key | Status |",
        "|----|------|-----|--------|",
        ...rows,
      ].join("\n");
    }
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the operation lists projects accessible to the authenticated user and returns a summary table. It implies a read-only operation, and while it could explicitly mention read-only or safety, the context is sufficient.

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 two sentences, front-loaded with purpose, and every sentence adds value. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains the return content and how to use the results. Given the absence of output schema, it provides adequate context. However, it does not mention pagination behavior or total count, which would be helpful for a complete understanding.

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% for both parameters (page, pageSize). The description does not add additional meaning beyond what the schema provides, so the baseline score of 3 applies.

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?

The description clearly states the verb 'List', the resource 'all Codebeamer projects', and the scope 'the authenticated user can access'. It distinguishes from siblings by specifying the return fields (IDs, names, keys) and linking to subsequent tools (fetch trackers or items).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly suggests using the returned IDs to fetch trackers or items, providing a clear use case. While it doesn't explicitly state when not to use this tool, the context from sibling tools implies its role as a starting point for project exploration.

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/3KniGHtcZ/codebeamer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server