Mushi-Mushi

Report detail

get_report_detail

Read-onlyIdempotent

Fetch a complete bug-report record by ID: description, console logs, network requests, screenshot, classification, fix history, and a paste-ready fix packet. Read-only; reporter identities are excluded.

Instructions

Fetch the full record for one bug report by id: description, console logs, network requests, screenshot URL, classification (stage 1/2), fix history, the paste-ready fix packet and the inventory action it is filed against. Returns { report } with the documented fields; includeRaw=true returns every column the detail route has instead. Reporter identifiers (end-user id, reporter token hash, session id, display name) are never returned. Read-only. Use when you have a reportId and need everything about it; for evidence only use get_report_evidence, for the activity thread use get_report_timeline, for a one-call fix bundle use get_fix_context.

Input Schema

TableJSON Schema

Name	Required	Description
`reportId`	Yes	The report UUID (`report_id` is accepted too.)
`projectId`	No	Project UUID — required for org-scoped keys with multiple projects. (`project_id` is accepted too.)
`includeRaw`	No	Return every column the detail route has (LLM invocation log, storage paths, custom metadata, …) instead of the documented fields. Reporter identifiers are removed either way. (`include_raw` is accepted too.)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`report`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.1.12Sep 24, 2026

addedInput schema / properties / includeRaw

Added value: +{
+  "description": "Return every column the detail route has (LLM invocation log, storage paths, custom metadata, …) instead of the documented fields. Reporter identifiers are removed either way. (`include_raw` is accepted too.)",
+  "type": "boolean"
+}

addedInput schema / properties / projectId

Added value: +{
+  "description": "Project UUID — required for org-scoped keys with multiple projects. (`project_id` is accepted too.)",
+  "type": "string"
+}

removedInput schema / properties / project_id

Removed value: -{
-  "description": "Project UUID — required for org-scoped keys with multiple projects.",
-  "type": "string"
-}

changedInput schema / properties / reportId / description

Previous value: -"The report UUID"New value: +"The report UUID (`report_id` is accepted too.)"

addedOutput schema / properties / report / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / report / properties

Added value: +{
+  "breadcrumbs": {},
+  "category": {
+    "description": "bug | slow | visual | confusing | other",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "child_report_ids": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "component": {
+    "description": "Component or page the bug was attributed to",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "console_logs": {
+    "description": "Console entries captured with the report"
+  },
+  "created_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "description": {
+    "description": "What the reporter wrote (untrusted text)",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "environment": {
+    "description": "Browser/OS/viewport the SDK captured"
+  },
+  "fix_attempts": {
+    "description": "Latest fix attempts, newest first",
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "status": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "fix_packet": {
+    "description": "Paste-ready fix prompt composed server-side"
+  },
+  "id": {
+    "description": "Report UUID",
+    "type": "string"
+  },
+  "inventory_action": {
+    "description": "Inventory action the report is filed against, when resolved"
+  },
+  "network_logs": {
+    "description": "Network requests captured with the report"
+  },
+  "project_id": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "reproduction_steps": {},
+  "screenshot_url": {
+    "description": "Signed screenshot URL",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "severity": {
+    "description": "critical | high | medium | low",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "stage1_classification": {
+    "description": "Stage-1 (fast) classification"
+  },
+  "stage2_analysis": {
+    "description": "Stage-2 analysis: rootCause, suggestedFix, …"
+  },
+  "status": {
+    "description": "Workflow status, e.g. new, classified, fixing, fixed, verified, reopened",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "summary": {
+    "description": "One-line summary written by the classifier",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "title": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / report / required
```
Added value: +[
+  "id"
+]
```
addedOutput schema / properties / report / type
```
Added value: +"object"
```

Changed2 schema fields changedv0.1.10Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.1.0Jun 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint, and the description adds valuable behavioral context: reporter identifiers are never returned, includeRaw=true returns every column instead, and the response is wrapped in { report }. These details go well beyond what the annotations convey.

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?

Every sentence earns its place: purpose, content list, response shape, privacy note, read-only statement, usage scenario, and sibling alternatives. It is dense but not bloated, and the most important information is front-loaded.

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

Completeness5/5

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

Combined with the full input schema, output schema, and annotations, this description covers what is returned, what is redacted, the alternative includeRaw mode, and when to choose sibling tools. Nothing critical is missing for an agent to invoke it correctly.

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% and each parameter has a description including accepted aliases. The tool description mentions includeRaw's effect but does not add significant new parameter semantics beyond the schema, so the baseline 3 applies.

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?

Clearly states a specific verb 'Fetch' with a specific resource 'the full record for one bug report by id' and enumerates its contents. It distinguishes itself from siblings by naming which tool to use for evidence, timeline, and fix bundle alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when you have a reportId and need everything about it' and gives conditional routing to get_report_evidence, get_report_timeline, and get_fix_context. This is textbook when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.