Kilotest

listIssues

Read-onlyIdempotent

Lists the issues reported in one report, along with the history of all reports about the same page. Use this after listPages to switch to an earlier or later report or to begin examining this report. Returns the history and the basics about this report’s issues.

Input Schema

Name	Required	Description	Default
`reportID`	Yes	Identifier of the report (example: 260503T0432-x9z)

Output Schema

Name	Required	Description	Default
`tool name`	Yes
`this request`	Yes
`tool collection`	Yes
`response content`	Yes
`response metadata`	Yes
`URLs of similar requests for web users`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 1, 2026
- addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / approval
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / confirmation
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / order confirmation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / properties / request confirmation
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / definitions / ToolsFacts / properties / description / properties / how to generate more findings / required
```
Previous value: -[
-  "new testing",
-  "retesting",
-  "latency",
-  "confirmation"
-]New value: +[
+  "new testing",
+  "retesting",
+  "approval",
+  "latency",
+  "request confirmation",
+  "order confirmation"
+]
```

Changed6 schema fields changedOct 18, 2026

removedInput schema / properties / jobID

Removed value: -{
-  "description": "Job identifier of the report (example: x9z)",
-  "type": "string"
-}

addedInput schema / properties / reportID

Added value: +{
+  "description": "Identifier of the report (example: 260503T0432-x9z)",
+  "type": "string"
+}

removedInput schema / properties / timeStamp

Removed value: -{
-  "description": "Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "reportID"
+]

changedOutput schema / definitions / ReportBasics / properties / identifier / description

Previous value: -"timeStamp-jobID identifier of the report."New value: +"Identifier of the report (example: 260503T0432-x9z)."

changedOutput schema / properties / response content / properties / history of reports about the page / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "completion date and time": {
-          "type": "string"
-        },
-        "days since the report was completed": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "how to get details about the report": {
-          "additionalProperties": false,
-          "properties": {
-            "URL": {
-              "type": "string"
-            },
-            "method": {
-              "const": "GET",
-              "type": "string"
-            }
-          },
-          "required": [
-            "method",
-            "URL"
-          ],
-          "type": "object"
-        },
-        "identifier": {
-          "description": "timeStamp-jobID identifier of the report.",
-          "type": "string"
-        },
-        "web users can get details about the report at": {
-          "type": "string"
-        },
-        "whether it is the latest report about the page": {
-          "type": "boolean"
-        },
-        "whether it is the oldest report about the page": {
-          "type": "boolean"
-        },
-        "whether it is the report described in this response": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "identifier",
-        "completion date and time",
-        "days since the report was completed",
-        "whether it is the oldest report about the page",
-        "whether it is the latest report about the page",
-        "whether it is the report described in this response",
-        "how to get details about the report",
-        "web users can get details about the report at"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "completion date and time": {
+          "type": "string"
+        },
+        "days since the report was completed": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "how to get details about the report": {
+          "additionalProperties": false,
+          "properties": {
+            "URL": {
+              "type": "string"
+            },
+            "method": {
+              "const": "GET",
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "URL"
+          ],
+          "type": "object"
+        },
+        "identifier": {
+          "description": "Identifier of the report (example: 260503T0432-x9z).",
+          "type": "string"
+        },
+        "web users can get details about the report at": {
+          "type": "string"
+        },
+        "whether it is the latest report about the page": {
+          "type": "boolean"
+        },
+        "whether it is the oldest report about the page": {
+          "type": "boolean"
+        },
+        "whether it is the report described in this response": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "identifier",
+        "completion date and time",
+        "days since the report was completed",
+        "whether it is the oldest report about the page",
+        "whether it is the latest report about the page",
+        "whether it is the report described in this response",
+        "how to get details about the report",
+        "web users can get details about the report at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / response content / properties / history of reports about the page

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "completion date and time": {
+            "type": "string"
+          },
+          "days since the report was completed": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "how to get details about the report": {
+            "additionalProperties": false,
+            "properties": {
+              "URL": {
+                "type": "string"
+              },
+              "method": {
+                "const": "GET",
+                "type": "string"
+              }
+            },
+            "required": [
+              "method",
+              "URL"
+            ],
+            "type": "object"
+          },
+          "identifier": {
+            "description": "timeStamp-jobID identifier of the report.",
+            "type": "string"
+          },
+          "web users can get details about the report at": {
+            "type": "string"
+          },
+          "whether it is the latest report about the page": {
+            "type": "boolean"
+          },
+          "whether it is the oldest report about the page": {
+            "type": "boolean"
+          },
+          "whether it is the report described in this response": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "identifier",
+          "completion date and time",
+          "days since the report was completed",
+          "whether it is the oldest report about the page",
+          "whether it is the latest report about the page",
+          "whether it is the report described in this response",
+          "how to get details about the report",
+          "web users can get details about the report at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "All reports about the same page, from oldest to latest, or null if the report is unavailable."
+}

changedOutput schema / properties / response content / required

Previous value: -[
-  "basics about the report",
-  "details about the report",
-  "how to request that the page be retested",
-  "how a web user can request that the page be retested",
-  "how to get the full report in JSON",
-  "how a web user can get the full report in JSON",
-  "basics about all issues reported in the report"
-]New value: +[
+  "basics about the report",
+  "history of reports about the page",
+  "details about the report",
+  "how to request that the page be retested",
+  "how a web user can request that the page be retested",
+  "how to get the full report in JSON",
+  "how a web user can get the full report in JSON",
+  "basics about all issues reported in the report"
+]

Changed2 schema fields changedOct 2, 2026
- removedOutput schema / definitions / RequestReference / properties / method / const
```
Removed value: -"GET"
```
- addedOutput schema / definitions / RequestReference / properties / method / enum
```
Added value: +[
+  "GET",
+  "POST"
+]
```

Changed4 schema fields changedSep 15, 2026

changedOutput schema / definitions / ReportBasics / properties / days since the report was completed / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

addedOutput schema / properties / response content / properties / basics about all issues reported in the report / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "how to get details about the issue": {
+          "additionalProperties": false,
+          "properties": {
+            "URL": {
+              "type": "string"
+            },
+            "method": {
+              "const": "GET",
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "URL"
+          ],
+          "type": "object"
+        },
+        "identifier": {
+          "type": "string"
+        },
+        "impact on a user": {
+          "type": "string"
+        },
+        "priority": {
+          "enum": [
+            "lowest",
+            "low",
+            "high",
+            "highest"
+          ],
+          "type": "string"
+        },
+        "rule engines with any violations belonging to the issue": {
+          "items": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "web users can get details about the issue at": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "identifier",
+        "summary",
+        "impact on a user",
+        "priority",
+        "rule engines with any violations belonging to the issue",
+        "how to get details about the issue",
+        "web users can get details about the issue at"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / response content / properties / basics about all issues reported in the report / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "how to get details about the issue": {
-      "additionalProperties": false,
-      "properties": {
-        "URL": {
-          "type": "string"
-        },
-        "method": {
-          "const": "GET",
-          "type": "string"
-        }
-      },
-      "required": [
-        "method",
-        "URL"
-      ],
-      "type": "object"
-    },
-    "identifier": {
-      "type": "string"
-    },
-    "impact on a user": {
-      "type": "string"
-    },
-    "priority": {
-      "enum": [
-        "lowest",
-        "low",
-        "high",
-        "highest"
-      ],
-      "type": "string"
-    },
-    "rule engines with any violations belonging to the issue": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "summary": {
-      "type": "string"
-    },
-    "web users can get details about the issue at": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "identifier",
-    "summary",
-    "impact on a user",
-    "priority",
-    "rule engines with any violations belonging to the issue",
-    "how to get details about the issue",
-    "web users can get details about the issue at"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / response content / properties / basics about all issues reported in the report / type
```
Removed value: -"array"
```

First observedSep 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds useful behavioral context by mentioning report history and switching reports, but it does not cover pagination, error conditions, or other operational details.

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 short and front-loads the main purpose before usage guidance. There is minor redundancy between the mention of report history and the final sentence about returning history and basics, but overall it is efficient.

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?

Given rich annotations, a fully described single parameter, and an output schema, the description is largely complete for an agent to select and invoke the tool. It could be improved by clarifying how it relates to sibling reporting tools, but no critical invocation detail is missing.

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 description coverage is 100% and there is only one parameter, reportID, whose meaning is documented in the schema. The description references 'one report' and 'this report' but adds no format or constraint details beyond the schema.

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

Purpose4/5

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

The description clearly states the specific action and resource: listing issues in one report, plus report history for the same page. It names listPages as a predecessor but does not explicitly differentiate from siblings such as getReport, listDiagnoses, or listViolators.

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

Usage Guidelines4/5

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

It gives a clear usage context: call this after listPages to switch between earlier/later reports or begin examining a report. It does not state when not to use this tool versus similar reporting tools, so it stops short of full alternative guidance.

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

All Kilotest tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.