Mushi-Mushi

Recent bug reports

get_recent_reports

Read-onlyIdempotent

List recent bug reports for a project, newest first. Filter by status, category, or severity to survey open issues and key details.

Instructions

List recent bug reports for a project, newest first. Returns { reports: [{ id, status, category, severity, summary, component, created_at, processing_error }], total }; includeRaw=true returns every list column instead. Reporter identifiers (end-user id, reporter token hash, session id, display name) are never returned. Optional filters: status (new|classified|grouped|fixing|fixed|verified|reopened|dismissed|…), category (bug|slow|visual|confusing|other), severity (critical|high|medium|low), limit (default 20, max 100). Use to survey open reports; for one report use get_report_detail, to find a bug by text use search_reports.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max reports to return (default 20, max 100)
`status`	No	Filter by status. "new" also matches queued rows; "classified" and "fixed" include legacy aliases.
`category`	No	Filter by category.
`severity`	No	Filter by severity.
`projectId`	No	Project UUID — defaults to the server-configured project. Useful when your key spans several projects; the error you get without it lists their ids. (`project_id` is accepted too.)
`includeRaw`	No	Return every column the list route has (breadcrumbs, environment, tags, …) instead of the documented fields. Reporter identifiers are removed either way. (`include_raw` is accepted too.)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`reports`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.1.12Sep 24, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category: bug, slow, visual, confusing, other"New value: +"Filter by category."

addedInput schema / properties / category / enum

Added value: +[
+  "bug",
+  "slow",
+  "visual",
+  "confusing",
+  "other"
+]

addedInput schema / properties / includeRaw

Added value: +{
+  "description": "Return every column the list route has (breadcrumbs, environment, tags, …) 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 — defaults to the server-configured project. Useful when your key spans several projects; the error you get without it lists their ids. (`project_id` is accepted too.)",
+  "type": "string"
+}

removedInput schema / properties / project_id

Removed value: -{
-  "description": "Project UUID — defaults to the server-configured project. Useful when you have multiple projects and want to query a specific one by its ID. Get IDs by calling list_projects or get_account_overview first.",
-  "type": "string"
-}

changedInput schema / properties / severity / description

Previous value: -"Filter by severity: critical, high, medium, low"New value: +"Filter by severity."

addedInput schema / properties / severity / enum

Added value: +[
+  "critical",
+  "high",
+  "medium",
+  "low"
+]

changedInput schema / properties / status / description

Previous value: -"Filter by status: new, classified, grouped, fixing, fixed, dismissed"New value: +"Filter by status. \"new\" also matches queued rows; \"classified\" and \"fixed\" include legacy aliases."

addedInput schema / properties / status / enum

Added value: +[
+  "new",
+  "pending",
+  "submitted",
+  "queued",
+  "classified",
+  "grouped",
+  "fixing",
+  "fixed",
+  "dismissed",
+  "triaged",
+  "in_progress",
+  "resolved",
+  "verified",
+  "reopened"
+]

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

addedOutput schema / properties / reports / items / properties

Added value: +{
+  "category": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "component": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "created_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "id": {
+    "type": "string"
+  },
+  "severity": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "status": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "summary": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / reports / items / required
```
Added value: +[
+  "id"
+]
```
addedOutput schema / properties / reports / items / 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.6/5.0

Behavior4/5

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

Although annotations already declare readOnlyHint=true, idempotentHint=true, the description adds important behavioral context: it promises newest-first ordering, discloses that includeRaw=true changes the returned columns, and states that reporter identifiers are never returned. This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded with the core purpose and return shape, followed by filters and routing guidance. It earns its length because it packs meaningful details (never returns reporter IDs, includeRaw behavior, limit defaults), but a sentence or two could be trimmed since some filter details duplicate the schema enums.

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?

With an output schema present and annotations covering read-only/idempotent safety, the description still supplies what an agent needs: ordering, optional filters, limit bounds, includeRaw semantics, the never-returned reporter data, and routing to siblings. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all six parameters thoroughly, including enums and aliases. The description itself repeats some filter details (status/category/severity enums, limit defaults) and adds the note that reporter identifiers are never returned—useful but not a major compensation need. Baseline 3 is exceeded slightly because the description reinforces the key filter semantics and the default/max limit, but it also largely duplicates the schema.

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 states a specific verb and resource ('List recent bug reports for a project, newest first'), specifies the return shape, and distinguishes itself from siblings by naming alternatives (get_report_detail, search_reports). The scope (project, newest first) is clear, and the presence of filters reinforces its purpose.

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 to survey open reports; for one report use get_report_detail, to find a bug by text use search_reports.' This provides clear when-to-use guidance and names alternatives, which is exactly what the dimension asks for.

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