Skip to main content
Glama
simplypixi

BugBug MCP Server

by simplypixi

get_suite_run

Retrieve detailed execution results for a specific test suite run using its unique identifier, enabling analysis of test outcomes and performance.

Instructions

Get detailed results of a BugBug suite run

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesSuite run UUID

Implementation Reference

  • Executes the tool logic: fetches suite run data from bugbugClient.getSuiteRun, handles errors, formats test details and returns structured text response.
    handler: async ({ runId }) => {
        try {
    
          const response = await bugbugClient.getSuiteRun(runId);
          
          if (response.status !== 200) {
            return {
              content: [
                {
                  type: 'text',
                  text: `Error: ${response.status} ${response.statusText}`,
                },
              ],
            };
          }
    
          const run = response.data as BugBugSuiteRun;
          
          let testDetails = '';
          if (run.details && run.details.length > 0) {
            testDetails = run.details.map((test: BugBugTestDetail) => 
              `  - **${test.name}** (${test.status}) - Duration: ${test.duration || 'N/A'}`
            ).join('\n');
          } else {
            testDetails = '  No test details available';
          }
          
          return {
            content: [
              {
                type: 'text',
                text: `**Suite Run Details:**\n\n- **Name:** ${run.name}\n- **ID:** ${run.id}\n- **Status:** ${run.status}\n- **Duration:** ${run.duration || 'N/A'}\n- **Queued:** ${run.queued || 'N/A'}\n- **Error Code:** ${run.errorCode || 'None'}\n- **Web App URL:** ${run.webappUrl}\n\n**Test Results:**\n${testDetails}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error fetching suite run: ${error instanceof Error ? error.message : 'Unknown error'}`,
              },
            ],
          };
        }
      }
  • Zod schema for tool input: requires 'runId' as string.
    inputSchema: z.object({
      runId: z.string().describe('Suite run UUID'),
    }).shape,
  • Registers the get_suite_run tool (via suiteRunsTools) with the MCP server by collecting all tools and calling server.registerTool for each.
    export function registerAllTools(server: McpServer): void {
      const tools: Record<string, Tool> = {
        ...configTools,
        ...testsTools,
        ...testRunsTools,
        ...suitesTools,
        ...suiteRunsTools,
        ...profilesTools,
        ...advancedTools,
      };
    
      for (const t in tools) {
        server.registerTool(
          tools[t].name,
          {
            description: tools[t].description,
            inputSchema: tools[t].inputSchema,
            annotations: { title: tools[t].title },
          },
          (args: unknown) => tools[t].handler(args as unknown)
        );
      }
    }
  • BugBug API client method that performs the HTTP request to retrieve suite run details, used by the tool handler.
    async getSuiteRun(id: string): Promise<ApiResponse<BugBugSuiteRun>> {
      return this.makeRequest(`/suiteruns/${id}/`);
    }
  • src/index.ts:42-42 (registration)
    Top-level call to register all tools, including get_suite_run, on the MCP server instance.
    registerAllTools(server);
Behavior3/5

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

Annotations provide a title that matches the description but no behavioral hints (e.g., readOnlyHint, destructiveHint). The description adds minimal context by specifying 'detailed results,' implying richer data than status-only tools, but doesn't disclose aspects like rate limits, authentication needs, or response format. With no annotations, the description carries some burden but offers limited behavioral insight.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes to understanding the tool.

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

Completeness3/5

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

Given the tool has one parameter with full schema coverage and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'detailed results' include (e.g., logs, metrics, or structured data), which could be crucial for an agent. With no annotations and simple parameters, the description meets basic needs but leaves gaps in understanding the tool's full behavior and output.

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?

The input schema has 100% description coverage, with 'runId' clearly documented as a 'Suite run UUID.' The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or constraints. Given high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 clearly states the action ('Get detailed results') and resource ('BugBug suite run'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_suite_run_status' or 'get_suite_run_screenshots' that also retrieve information about suite runs, so it doesn't fully distinguish itself from alternatives.

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 such as 'get_suite_run_status' (which might give status only) or 'get_suite_run_screenshots' (which might retrieve visual data). There's no mention of prerequisites, context, or exclusions, leaving usage unclear relative to siblings.

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/simplypixi/bugbug-mcp-server'

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