Skip to main content
Glama
simplypixi

BugBug MCP Server

by simplypixi

get_suites

Retrieve and filter test suites from the BugBug automation platform to manage and organize testing workflows.

Instructions

Get list of BugBug test suites

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderingNoSort order
pageNoPage number for pagination
pageSizeNoNumber of results per page
queryNoSearch query for suite names

Implementation Reference

  • The complete implementation of the 'get_suites' tool, including input schema, handler logic for fetching and formatting suites list from BugBug API.
    export const getSuitesTool: Tool = {
      name: 'get_suites',
      title: 'Get list of BugBug test suites',
      description: 'Get list of BugBug test suites',
      inputSchema: z.object({
        page: z.number().optional().describe('Page number for pagination'),
        pageSize: z.number().optional().describe('Number of results per page'),
        query: z.string().optional().describe('Search query for suite names'),
        ordering: z.enum(['name', '-name', 'created', '-created']).optional().describe('Sort order'),
      }).shape,
      handler: async ({ page, pageSize, query, ordering }) => {
          try {
            const response = await bugbugClient.getSuites(page, pageSize, query, ordering);
            
            if (response.status !== 200) {
              return {
                content: [
                  {
                    type: 'text',
                    text: `Error: ${response.status} ${response.statusText}`,
                  },
                ],
              };
            }
    
            const { count, page: currentPage, results } = response.data;
            
            let suitesList = '';
            if (results && results.length > 0) {
              suitesList = results.map((suite: BugBugSuite) => 
                `- **${suite.name || 'Unnamed Suite'}** (ID: ${suite.id}) - ${suite.testsCount || 0} tests`
              ).join('\n');
            } else {
              suitesList = 'No suites found.';
            }
            
            return {
              content: [
                {
                  type: 'text',
                  text: `**BugBug Test Suites** (Page ${currentPage || 1}, Total: ${count || 0}):\n\n${suitesList}`,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: 'text',
                  text: `Error fetching suites: ${error instanceof Error ? error.message : 'Unknown error'}`,
                },
              ],
            };
          }
        }
    };
  • Registration of all tools, including 'get_suites' from suitesTools, using server.registerTool with name, schema, and handler.
    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)
        );
      }
    }
  • Zod input schema defining parameters for the get_suites tool: page, pageSize, query, ordering.
    inputSchema: z.object({
      page: z.number().optional().describe('Page number for pagination'),
      pageSize: z.number().optional().describe('Number of results per page'),
      query: z.string().optional().describe('Search query for suite names'),
      ordering: z.enum(['name', '-name', 'created', '-created']).optional().describe('Sort order'),
    }).shape,
  • Helper method bugbugClient.getSuites that constructs API query parameters and calls makeRequest to fetch suites from /suites/ endpoint.
    async getSuites(page?: number, pageSize?: number, query?: string, ordering?: string): Promise<ApiResponse<PaginatedResponse<BugBugSuite>>> {
      const params = new URLSearchParams();
      if (page) params.append('page', page.toString());
      if (pageSize) params.append('page_size', pageSize.toString());
      if (query) params.append('query', query);
      if (ordering) params.append('ordering', ordering);
      
      const queryString = params.toString() ? `?${params.toString()}` : '';
      return this.makeRequest(`/suites/${queryString}`);
    }
Behavior3/5

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

Annotations provide a title but no behavioral hints (no readOnlyHint, destructiveHint, etc.). The description adds minimal behavioral context beyond the basic operation - it doesn't mention pagination behavior, rate limits, authentication requirements, or what constitutes a 'test suite' in this 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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a list operation and front-loads the essential information.

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?

For a list operation with 4 parameters and no output schema, the description provides basic purpose but lacks context about return format, pagination behavior, or error conditions. With no annotations covering behavioral aspects, the description should do more to explain what the tool actually returns and how it behaves.

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?

With 100% schema description coverage, all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema - it doesn't explain default values, parameter interactions, or provide examples of query syntax.

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 verb 'Get' and resource 'list of BugBug test suites', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_suite' (singular) or 'get_tests', leaving room for potential confusion about scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_suite' (for a single suite) or 'get_tests' (for individual tests). The description lacks context about appropriate use cases or prerequisites for listing suites.

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