Kilotest

orderRetest

Orders a retest of a page whose existing report is considered obsolete, with automated approval or rejection and immediate enqueuing if approved. Use this instead of requestRetest when immediate retesting is wanted; testing typically takes 2 to 4 minutes. Returns an order confirmation and disposition details, including, if approved, a report identifier and a question about whether to wait for completion with the awaitTest tool.

Input Schema

Name	Required	Description	Default
`reason`	Yes	20- to 100-character reason why the page should be retested
`reportID`	Yes	Identifier of the latest report about the page (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 latest report about the page (example: x9z)",
-  "type": "string"
-}

addedInput schema / properties / reportID

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

removedInput schema / properties / timeStamp

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

changedInput schema / required

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

removedOutput schema / definitions / ReportIdentifier

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "jobID": {
-      "description": "Job identifier to pass to listIssues once the report is ready.",
-      "type": "string"
-    },
-    "timeStamp": {
-      "description": "Timestamp to pass to listIssues once the report is ready.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "timeStamp",
-    "jobID"
-  ],
-  "type": "object"
-}

changedOutput schema / properties / response content / properties / disposition of your order / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "do you want to wait for completion": {
-        "type": "string"
-      },
-      "how you can check for completion": {
-        "type": "string"
-      },
-      "report identifier": {
-        "anyOf": [
-          {
-            "$ref": "#/definitions/ReportIdentifier"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "what happens next": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "what happens next",
-      "report identifier",
-      "how you can check for completion",
-      "do you want to wait for completion"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "do you want to wait for completion": {
+        "type": "string"
+      },
+      "how you can check for completion": {
+        "type": "string"
+      },
+      "report identifier": {
+        "anyOf": [
+          {
+            "description": "Identifier of the report, to pass to listIssues once the report is ready (example: 260503T0432-x9z).",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "what happens next": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "what happens next",
+      "report identifier",
+      "how you can check for completion",
+      "do you want to wait for completion"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

AddedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare it is not read-only, is open-world, and is non-idempotent; the description adds what the annotations cannot — automated approval/rejection, immediate enqueuing on approval, and a 2-4 minute runtime. It does not disclose that repeat calls create duplicate orders despite idempotentHint=false, which would be useful for a non-idempotent mutation.

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 purpose and the sibling alternative are front-loaded in the first clause. The sentences are dense and mostly earn their place, though the trailing return-value sentence runs long and could be trimmed.

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 an output schema exists, the description need not explain return values, yet it usefully flags that approval yields a report identifier and an awaitTest decision. It covers the approval flow and timing, leaving only duplicate-order behavior and approval prerequisites unstated.

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%, so both parameters (reportID and reason, including the 20-100 character constraint) are already documented in the schema. The description adds only the framing that reportID refers to a page's obsolete latest report, which is marginal value over the structured fields. 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?

States a specific verb and resource ("Orders a retest of a page") plus the qualifying condition that the existing report is obsolete. It distinguishes itself from requestRetest by name, 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 Guidelines5/5

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

"Use this instead of requestRetest when immediate retesting is wanted" gives an explicit alternative and the condition that selects it. It also points to awaitTest as the follow-up for waiting on completion, covering the main decision path.

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.