Skip to main content
Glama

get_launch_details

Retrieve comprehensive launch data including test sessions and execution details from Zebrunner reporting API for test analysis and reporting.

Instructions

🚀 Get comprehensive launch details including test sessions (uses new reporting API with enhanced authentication)

Input Schema

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

Implementation Reference

  • Registration of the MCP tool 'get_launch_details'. Defines input schema inline and delegates execution to the reportingHandlers.getLauncherDetails method.
    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 GetLauncherDetailsInputSchema used by the get_launch_details tool (imported in server-with-reporting.ts but schema redefined inline).
    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') });
  • API client method getLaunch() retrieves core launch details by ID and project ID, fundamental to the get_launch_details tool implementation.
    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); }
  • API client method getTestSessions() retrieves test sessions for a launch, used to fulfill the includeTestSessions option in get_launch_details 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