Skip to main content
Glama

get_launch_details

Retrieve comprehensive launch details and test session data from Zebrunner Test Case Management for analysis and reporting.

Instructions

๐Ÿš€ Get comprehensive launch details including test sessions (uses new reporting API with enhanced authentication)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyNoProject key (e.g., 'android' or 'ANDROID') - alternative to projectId
projectIdNoProject ID (e.g., 7) - alternative to projectKey
launchIdYesLaunch ID (e.g., 118685)
includeLaunchDetailsNoInclude detailed launch information
includeTestSessionsNoInclude test sessions data
formatNoOutput formatjson

Implementation Reference

  • MCP tool registration for 'get_launch_details'. Defines input schema inline and handler that delegates to reportingHandlers.getLauncherDetails(args). This is the entry point where the tool is made available via MCP server.tool().
    server.tool(
      "get_launch_details",
      "๐Ÿš€ Get comprehensive launch details including test sessions (uses new reporting API with enhanced authentication)",
      {
        projectKey: z.string().min(1).optional().describe("Project key (e.g., 'android' or 'ANDROID') - alternative to projectId"),
        projectId: z.number().int().positive().optional().describe("Project ID (e.g., 7) - alternative to projectKey"),
        launchId: z.number().int().positive().describe("Launch ID (e.g., 118685)"),
        includeLaunchDetails: z.boolean().default(true).describe("Include detailed launch information"),
        includeTestSessions: z.boolean().default(true).describe("Include test sessions data"),
        format: z.enum(['dto', 'json', 'string']).default('json').describe("Output format")
      },
      async (args) => reportingHandlers.getLauncherDetails(args)
    );
  • Zod schema definition for GetLauncherDetailsInput used by the get_launch_details tool (imported in server-with-reporting.ts but schema redefined inline in registration).
    export const GetLauncherDetailsInputSchema = z.object({
      projectKey: z.string().min(1).optional(),
      projectId: z.number().int().positive().optional(),
      launchId: z.number().int().positive(),
      includeLaunchDetails: z.boolean().default(true),
      includeTestSessions: z.boolean().default(true),
      format: z.enum(['dto', 'json', 'string']).default('json')
    });
  • ZebrunnerReportingClient.getLaunch(): Core API method to fetch launch details, likely called within the tool handler reportingHandlers.getLauncherDetails().
    async getLaunch(launchId: number, projectId: number): Promise<LaunchResponse> {
      const url = `/api/reporting/v1/launches/${launchId}?projectId=${projectId}`;
      const response = await this.makeAuthenticatedRequest<any>('GET', url);
      
      // Extract the actual launch data from the nested response
      const launchData = response.data || response;
      
      return LaunchResponseSchema.parse(launchData);
    }
  • ZebrunnerReportingClient.getTestSessions(): Fetches test sessions for a launch, supporting the includeTestSessions parameter in the tool.
    async getTestSessions(launchId: number, projectId: number): Promise<TestSessionsResponse> {
      const url = `/api/reporting/v1/launches/${launchId}/test-sessions?projectId=${projectId}`;
      const response = await this.makeAuthenticatedRequest<any>('GET', url);
      
      // Handle different response structures
      const sessionsData = response.data || response;
      
      return TestSessionsResponseSchema.parse(sessionsData);
    }

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/maksimsarychau/mcp-zebrunner'

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