Tool Reference
CrashSight MCP currently provides the tools below. The client picks tools from the conversation; you can improve accuracy by including the app ID, platform, and time range in your prompt.
Unless noted otherwise, query tools can only access apps that the current account can view in the console. Identity comes from the API Key; you do not need to provide a password in chat.
Common platformId values: 1=Android, 2=iOS, 10=PC, 11=PS5, 12=Xbox, 13=Switch, 20=Linux, 40=Harmony.
1 Apps and account
| Tool | Description |
|---|---|
get_app_info_list | List apps the current account can access, with optional search by app ID or name |
who_am_i | Return the user identity bound to the API Key (user ID, nickname, email, and so on) to confirm the key works |
2 Issue search
| Tool | Description |
|---|---|
advanced_issue_search | Search issues by upload time, version, exception type, stack keyword, issue ID, and status. Maximum time range is 90 days |
get_top_issue_hourly | Hourly Top Issue ranking for a given time range |
get_top_issue_daily | Daily Top Issue ranking, filterable by crash, ANR, error, OOM, or jank |
query_issue_trend | Upload trend for specified issues (by day or hour, up to 90 days) |
advanced_issue_search supports a simple AND combination of common filters, or a JSON condition group for nested AND/OR logic.
3 Crash report details
| Tool | Description |
|---|---|
query_crash_list | List exception reports (crash, error, ANR, and so on). Filter by issue ID, report ID, time, type, user, or device. For OOM, use query_oom_mmap_crashes |
get_report_detail | Fetch one report's basic info, device info, and stack by app ID, platform, and report ID (no attachment body) |
get_report_attachments | Fetch attachments for one report, such as system/user logs, other thread stacks, registers, and loaded modules |
fetch_last_crash_detail_in_issue | Fetch the latest report under an issue. Use this when you have an Issue link but no report ID |
fetch_crash_detail_by_share_id | Fetch report details from the shareId in an anonymous share link; no app ID required |
fetch_crash_attachment_by_share_id | Fetch report attachments from the shareId in an anonymous share link |
query_oom_mmap_crashes | Query OOM (out-of-memory) reports on mobile platforms (Android / iOS / Harmony) |
When extracting parameters from console URLs:
- Issue link (no
report-id) →fetch_last_crash_detail_in_issue - Report detail link (contains
report-id) →get_report_detail/get_report_attachments - Anonymous share link (path contains
shared-report) →fetch_crash_detail_by_share_id/fetch_crash_attachment_by_share_id
4 Trends and statistics
| Tool | Description |
|---|---|
get_daily_trend | Daily trend for crash / ANR / error / OOM, up to 90 days |
get_realtime_hourly_stat | Realtime hourly stats for the current day (start and end hour must be on the same day, and the range cannot exceed 24 hours) |
get_hourly_cumulative_stat | Cumulative stats from 00:00 to each hour of the current day |
fetch_field_top_stats | Rank exception devices or online devices by version, model, OS, GPU, CPU, or GPU driver |
5 Tips
- If you do not know the app ID, ask the assistant to call
get_app_info_listfirst - Include a time range when searching issues or reports; most search APIs allow at most 90 days
- After you have a report ID, use
get_report_attachmentsfor logs or other thread stacks - If a result is large, the tool may return a download URL for the client to fetch the full JSON