Skip to main content
Glama
simplypixi

BugBug MCP Server

by simplypixi

get_profiles

Retrieve a paginated list of test run profiles from the BugBug test automation platform to manage and execute automated testing configurations.

Instructions

Get list of BugBug run profiles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
pageSizeNoNumber of results per page

Implementation Reference

  • Full tool definition including handler function that executes the get_profiles tool logic by calling the BugBug API client and formatting the paginated list of profiles.
    export const getProfilesTool: Tool = {
      name: 'get_profiles',
      title: 'Get list of BugBug run profiles',
      description: 'Get list of BugBug run profiles',
      inputSchema: z.object({
        page: z.number().optional().describe('Page number for pagination'),
        pageSize: z.number().optional().describe('Number of results per page'),
      }).shape,
      handler: async ({ page, pageSize }) => {
          try {
            const response = await bugbugClient.getProfiles(page, pageSize);
            
            if (response.status !== 200) {
              return {
                content: [
                  {
                    type: 'text',
                    text: `Error: ${response.status} ${response.statusText}`,
                  },
                ],
              };
            }
    
            const { count, page: currentPage, results } = response.data;
            
            let profilesList = '';
            if (results && results.length > 0) {
              profilesList = results.map((profile: BugBugProfile) => 
                `- **${profile.name}** (ID: ${profile.id})${profile.isDefault ? ' [DEFAULT]' : ''}`
              ).join('\n');
            } else {
              profilesList = 'No profiles found.';
            }
            
            return {
              content: [
                {
                  type: 'text',
                  text: `**BugBug Run Profiles** (Page ${currentPage || 1}, Total: ${count || 0}):\n\n${profilesList}`,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: 'text',
                  text: `Error fetching profiles: ${error instanceof Error ? error.message : 'Unknown error'}`,
                },
              ],
            };
          }
        }
    };
  • Zod input schema defining optional pagination parameters for the get_profiles tool.
    inputSchema: z.object({
      page: z.number().optional().describe('Page number for pagination'),
      pageSize: z.number().optional().describe('Number of results per page'),
    }).shape,
  • Registration function that imports and registers all tools, including get_profiles from profiles.ts, with the MCP server.
    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 makes the HTTP request to fetch paginated profiles, used by the tool handler.
    async getProfiles(page?: number, pageSize?: number): Promise<ApiResponse<PaginatedResponse<BugBugProfile>>> {
      const params = new URLSearchParams();
      if (page) params.append('page', page.toString());
      if (pageSize) params.append('page_size', pageSize.toString());
      
      const query = params.toString() ? `?${params.toString()}` : '';
      return this.makeRequest(`/profiles/${query}`);
    }
Behavior3/5

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

Annotations only provide a title that repeats the description, offering no behavioral hints. The description adds minimal context by implying it returns a list, but lacks details on pagination behavior, rate limits, authentication needs, or error handling. With no annotations to rely on, this is a baseline disclosure.

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, making it easy to scan and understand quickly, which is ideal for conciseness.

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 the tool has no output schema and annotations only repeat the title, the description is insufficient. It doesn't explain return values (e.g., format of profiles), pagination details, or error cases, leaving gaps in understanding how to interpret results or handle edge cases.

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%, with parameters 'page' and 'pageSize' fully documented in the schema. The description adds no additional meaning about parameters, such as default values, constraints, or how they affect the list retrieval, so it meets the baseline for high schema coverage.

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 run profiles'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_profile' (singular) or 'get_suites' (different resource type), missing explicit distinction that would warrant a score of 5.

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_profile' (singular), 'get_suites', and 'get_tests', there's no indication of context, prerequisites, or exclusions, leaving usage ambiguous.

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