Skip to main content
Glama

List Trackers

list_trackers

Retrieve all trackers (Requirements, Bugs, Test Cases, etc.) in a Codebeamer project by providing the numeric project ID. Use the returned tracker IDs to access items or details.

Instructions

List all trackers (Requirements, Bugs, Test Cases, etc.) in a Codebeamer project. Use the returned tracker IDs to list items or get tracker details.

Input Schema

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

Implementation Reference

  • Handler function for the list_trackers tool. Calls client.listTrackers() and formats the result.
    server.registerTool(
      "list_trackers",
      {
        title: "List Trackers",
        description:
          "List all trackers (Requirements, Bugs, Test Cases, etc.) in a Codebeamer project. " +
          "Use the returned tracker IDs to list items or get tracker details.",
        inputSchema: {
          projectId: z
            .number()
            .int()
            .positive()
            .describe("Numeric project ID"),
          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 ({ projectId, page, pageSize }) => {
        const result = await client.listTrackers(projectId, page, pageSize);
        return { content: [{ type: "text", text: formatTrackerList(result) }] };
      },
    );
  • Schema definition for list_trackers input: projectId (number), page (optional, default 1), pageSize (optional, default 25).
    {
      title: "List Trackers",
      description:
        "List all trackers (Requirements, Bugs, Test Cases, etc.) in a Codebeamer project. " +
        "Use the returned tracker IDs to list items or get tracker details.",
      inputSchema: {
        projectId: z
          .number()
          .int()
          .positive()
          .describe("Numeric project ID"),
        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)"),
      },
  • Registration of the list_trackers tool via server.registerTool() inside the registerTrackerTools function.
    export function registerTrackerTools(
      server: McpServer,
      client: CodebeamerClient,
    ): void {
      server.registerTool(
        "list_trackers",
        {
          title: "List Trackers",
          description:
            "List all trackers (Requirements, Bugs, Test Cases, etc.) in a Codebeamer project. " +
            "Use the returned tracker IDs to list items or get tracker details.",
          inputSchema: {
            projectId: z
              .number()
              .int()
              .positive()
              .describe("Numeric project ID"),
            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 ({ projectId, page, pageSize }) => {
          const result = await client.listTrackers(projectId, page, pageSize);
          return { content: [{ type: "text", text: formatTrackerList(result) }] };
        },
      );
  • Client method listTrackers() that makes the HTTP GET request to /projects/{projectId}/trackers.
    async listTrackers(
      projectId: number,
      page: number,
      pageSize: number,
    ): Promise<CbTracker[]> {
      const raw = await this.http.get<unknown>(`/projects/${projectId}/trackers`, {
        params: { page, pageSize },
        resource: `trackers for project ${projectId}`,
      });
      return toArray(raw);
    }
  • Formatter that renders the list of CbTracker objects into a Markdown table.
    export function formatTrackerList(trackers: CbTracker[]): string {
      const header = `## Trackers (${trackers.length} total)\n`;
    
      if (trackers.length === 0) return `${header}\n_No trackers found._`;
    
      const rows = trackers.map(
        (t) =>
          `| ${t.id} | ${t.name} | ${t.type?.name ?? "-"} | ${t.keyName ?? "-"} |`,
      );
    
      return [
        header,
        "| ID | Name | Type | Key |",
        "|----|------|------|-----|",
        ...rows,
      ].join("\n");
    }
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions listing all trackers but does not discuss pagination behavior, performance implications, or any side effects. While the schema covers pagination parameters, the description adds no further behavioral context.

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 the core action, and contains no fluff. Every sentence earns its place.

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?

For a simple listing tool with three parameters and no output schema, the description is mostly sufficient. It could be more complete by mentioning that the response includes additional tracker fields (like name), but the hint 'Use the returned tracker IDs' implies minimal output. Given the tool's simplicity, it is reasonably complete.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description does not add additional meaning to parameters beyond what the schema provides, except that it hints at the output (tracker IDs), which is not parameter-specific.

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 it lists all trackers in a Codebeamer project, specifying the verb 'list', resource 'trackers', and context 'project'. This distinguishes it from sibling tools like list_tracker_items (which list items within a tracker) and get_tracker (which gets details of a specific tracker).

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 guides the agent to use the returned tracker IDs for subsequent operations like list items or get tracker details. However, it does not explicitly state when not to use this tool or directly compare with alternatives, though it is implied.

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