Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

get_crash_log

Retrieve crash log content from a TestFlight beta feedback submission by providing the crash submission ID.

Instructions

Download the crash log content for a specific beta feedback crash submission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crash_submission_idYesThe beta feedback crash submission ID

Implementation Reference

  • The handler function that executes the get_crash_log tool logic. It receives the crash_submission_id from the validated args, calls the API helper, and returns the crash log content.
    export async function handleGetCrashLog(
      client: AppStoreConnectClient,
      args: z.infer<typeof getCrashLogSchema>
    ) {
      const content = await getCrashLog(client, args.crash_submission_id);
      return { crashLog: content };
    }
  • Zod schema defining the input for get_crash_log. Takes a single required parameter: crash_submission_id (string).
    export const getCrashLogSchema = z.object({
      crash_submission_id: z
        .string()
        .describe("The beta feedback crash submission ID"),
    });
  • src/index.ts:112-122 (registration)
    Registration of the 'get_crash_log' tool on the MCP server. Maps the tool name to the schema and handler, and returns the result as text content.
    server.tool(
      "get_crash_log",
      "Download the crash log content for a specific beta feedback crash submission.",
      getCrashLogSchema.shape,
      async (args) => {
        const result = await handleGetCrashLog(client, args);
        return {
          content: [{ type: "text", text: result.crashLog }],
        };
      }
    );
  • The API helper function that fetches the crash log content from the App Store Connect API. Calls the endpoint /betaFeedbackCrashSubmissions/{id}/relationships/crashLog and extracts the content attribute.
    export async function getCrashLog(
      client: AppStoreConnectClient,
      crashSubmissionId: string
    ): Promise<string> {
      const response = await client.request<JsonApiResource>(
        `/betaFeedbackCrashSubmissions/${crashSubmissionId}/relationships/crashLog`
      );
      // The crash log is returned as a resource with content attribute
      const attrs = response.data?.attributes as Record<string, unknown> | undefined;
      return (attrs?.content as string) ?? "No crash log content available.";
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It indicates a read/download operation but does not disclose output format, authentication needs, or potential side effects. For a simple download, this is adequate but not rich.

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?

Single sentence, no redundant words, perfect structure for a simple tool.

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

Completeness4/5

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

For a tool with one required parameter and no output schema, the description covers the core behavior. However, omitting output format (e.g., plain text) or error conditions slightly reduces completeness.

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 coverage is 100% with parameter description 'The beta feedback crash submission ID'. The tool description adds little beyond that, just rephrasing. Baseline 3 is appropriate as no additional semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Download', the resource 'crash log content', and the context 'for a specific beta feedback crash submission'. It distinguishes from sibling tools like get_feedback_detail, which likely returns feedback details rather than crash logs.

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 on when to use this tool versus alternatives (e.g., get_feedback_detail). It does not mention prerequisites or scenarios where it should not be used.

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/BandaruDheeraj/testflight-feedback-mcp'

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