Kilotest

listViolators

Read-onlyIdempotent

Lists the elements of a tested page that were reported as exhibiting one issue in one report. Use this after listIssues to drill down from an issue to the elements violating rules belonging to that issue. Returns basics about each violating element.

Input Schema

Name	Required	Description	Default
`issueID`	Yes	Issue identifier (example: contrastPoor)
`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 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: -[
-  "issueID",
-  "timeStamp",
-  "jobID"
-]New value: +[
+  "issueID",
+  "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)."

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 elements exhibiting the issue

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count of rule engines reporting that the element exhibited the issue": {
+            "type": "number"
+          },
+          "how to get details about the element": {
+            "additionalProperties": false,
+            "properties": {
+              "URL": {
+                "type": "string"
+              },
+              "request method": {
+                "const": "GET",
+                "type": "string"
+              }
+            },
+            "required": [
+              "URL",
+              "request method"
+            ],
+            "type": "object"
+          },
+          "identifier": {
+            "description": "Catalog index of the element in the report; a string or number, copied verbatim.",
+            "type": [
+              "string",
+              "number"
+            ]
+          },
+          "inner text": {
+            "description": "Copied from the report catalog entry; type not guaranteed."
+          },
+          "tag name": {
+            "description": "Copied from the report catalog entry; type not guaranteed."
+          },
+          "web users can get details about the element at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "identifier",
+          "tag name",
+          "inner text",
+          "count of rule engines reporting that the element exhibited the issue",
+          "how to get details about the element",
+          "web users can get details about the element at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / response content / properties / basics about all elements reported as exhibiting the issue

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "count of rule engines reporting that the element exhibited the issue": {
-            "type": "number"
-          },
-          "how to get details about the element": {
-            "additionalProperties": false,
-            "properties": {
-              "URL": {
-                "type": "string"
-              },
-              "request method": {
-                "const": "GET",
-                "type": "string"
-              }
-            },
-            "required": [
-              "URL",
-              "request method"
-            ],
-            "type": "object"
-          },
-          "identifier": {
-            "type": "string"
-          },
-          "inner text": {
-            "description": "Copied from the report catalog entry; type not guaranteed."
-          },
-          "tag name": {
-            "description": "Copied from the report catalog entry; type not guaranteed."
-          },
-          "web users can get details about the element at": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "identifier",
-          "tag name",
-          "inner text",
-          "count of rule engines reporting that the element exhibited the issue",
-          "how to get details about the element",
-          "web users can get details about the element at"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

changedOutput schema / properties / response content / required

Previous value: -[
-  "basics about the report",
-  "basics about the issue",
-  "details about the issue",
-  "basics about all elements reported as exhibiting the issue"
-]New value: +[
+  "basics about the report",
+  "basics about the issue",
+  "details about the issue",
+  "basics about all elements exhibiting the issue"
+]

First observedSep 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the scoping constraint (one issue, one report) and a light hint that it 'returns basics about each violating element'. With the annotation bar this is adequate but not rich.

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?

Two sentences, zero padding, and the primary scope statement is front-loaded ahead of the usage guidance. Every clause carries information.

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 spelled out, and the description still notes the response contains 'basics about each violating element'. Combined with full annotation coverage and a 100% documented 2-param schema, an agent has everything needed to call 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 description coverage is 100% and both parameters carry examples ('contrastPoor', '260503T0432-x9z'), so the schema does the heavy lifting. The description only implies that issueID and reportID come from the preceding listIssues call; it adds no format or constraint detail beyond the schema, which is the correct baseline of 3.

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?

States a specific verb and resource ('lists the elements of a tested page') with an explicit scope: one issue in one report. It also implicitly distinguishes itself from the sibling listIssues by positioning this as the drill-down step, so an agent can tell the two apart without opening either schema.

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?

'Use this after listIssues to drill down from an issue to the elements violating rules belonging to that issue' gives explicit sequencing and the governing tool. It does not name a when-not case or an alternative for a different drill-down path, but the prerequisite relationship is unambiguous.

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.

Resources

Need Help?