firebase-tools icon indicating copy to clipboard operation
firebase-tools copied to clipboard

Reorganizing Crashlytics MCP Tools

Open maxl0rd opened this issue 2 weeks ago • 1 comments

Description

  • Consolidating all of the crashlytics_get_* tools into a single tool crashlytics_get_report. This will enable the set of supported reports to expand without adding additional tools.
  • Moving most of the content from the crashlytics:connect prompt to guide resources. This provides better support for the many MCP clients without support for prompts.
  • Numerous other improvements in prompt engineering and error handling

maxl0rd avatar Dec 05 '25 21:12 maxl0rd

Summary of Changes

Hello @maxl0rd, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the Crashlytics MCP tools by streamlining report generation into a single, unified function and externalizing detailed instructions into comprehensive resource guides. This change aims to enhance the system's scalability, improve the user experience for various MCP clients, and provide more robust error handling and guidance for developers interacting with Crashlytics data.

Highlights

  • Crashlytics Tool Consolidation: The multiple crashlytics_get_* tools have been consolidated into a single, more flexible crashlytics_get_report tool, allowing for easier expansion of supported reports without adding new tools.
  • Prompt Content Migration to Guides: Extensive instructional content from the crashlytics:connect prompt has been moved into dedicated resource guides, improving support for MCP clients that do not support interactive prompts.
  • Improved Prompt Engineering and Error Handling: The system now provides clearer instructions and better error handling, especially when required parameters like appId are missing, by directing users to relevant guides.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

gemini-code-assist[bot] avatar Dec 05 '25 21:12 gemini-code-assist[bot]