Kilotest

listIssues

Read-onlyIdempotent

Provide details about one report, including basics about the issues reported in it. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jobID`	Yes	Job identifier of the report (example: x9z)
`timeStamp`	Yes	Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)

Output Schema

TableJSON 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.

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

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine domain context (Kilotest tests front-end quality; results nest report→issue→violator→diagnosis), but says nothing about volume, pagination, or what 'basics' omits.

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?

Two sentences, front-loaded with the action and followed by compact framing context. The second sentence is arguably broader than needed for this one tool, but it is not filler.

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?

An output schema exists, so return values need not be explained, and the hierarchy sentence supplies the missing mental model for a tool in a nested resource family. What remains missing is call ordering relative to listReports, which is a minor gap.

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 both required parameters (jobID, timeStamp) carry format and example documentation. The description adds no parameter-level meaning 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.

Purpose3/5

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

The description says it provides details about one report 'including basics about the issues reported in it', which is close to the name listIssues but frames the tool as a report-detail getter. An agent cannot easily tell whether this or getReport returns the report itself, and no sibling is named to distinguish them.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus getReport, listReports, listViolators, or listDiagnoses, nor any prerequisites such as needing a jobID/timestamp pair from listReports. The hierarchy sentence implies position in a drill-down but never tells the agent to call this at that step.

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

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?