playwright-e2e-mcp

Check a background run

get-run-status

Idempotent

Check progress or final results of background Playwright test runs, wait for completion, or cancel a run; defaults to the latest run.

Instructions

Progress (tests done/total, failures so far) or the final result of a run-test background run; the result becomes the last run for get-failure. waitSeconds waits; cancel stops it. Default: the latest run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-run-status"
  }
}

Input Schema

Name	Required	Description
`runId`	No
`cancel`	No
`waitSeconds`	No	Wait up to this long for it to finish

Output Schema

Name	Required	Description
`ok`	Yes	false when the call failed (see error) or the tests it ran failed
`run`	No
`error`	No
`runId`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.13.0Nov 2, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -{}
```

Changed1 schema field changedv0.7.0Oct 29, 2026

addedOutput schema / properties / run / properties / quarantined

Added value: +{
+  "description": "failures covered by an active quarantine entry (they do not fail the run)",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changed2 schema fields changedv0.6.1Oct 27, 2026

addedInput schema / additionalProperties
```
Added value: +{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "hint": {
+          "type": "string"
+        },
+        "kind": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "message"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "description": "false when the call failed (see error) or the tests it ran failed",
+      "type": "boolean"
+    },
+    "run": {
+      "additionalProperties": false,
+      "properties": {
+        "durationMs": {
+          "type": "number"
+        },
+        "exitCode": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "failed": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "failures": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "file": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "line": {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              "message": {
+                "type": "string"
+              },
+              "project": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              },
+              "tracePath": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "file",
+              "title",
+              "kind",
+              "message"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "failuresTruncated": {
+          "type": "boolean"
+        },
+        "flaky": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "partial": {
+          "type": "boolean"
+        },
+        "passed": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "skipped": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "passed",
+        "failed",
+        "flaky",
+        "skipped",
+        "durationMs",
+        "exitCode",
+        "partial",
+        "failures"
+      ],
+      "type": "object"
+    },
+    "runId": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedv0.3.2Oct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-readonly, idempotent, non-destructive behavior. The description adds useful context beyond that: cancel stops the run, waitSeconds waits, the result becomes the last run for get-failure, and the default is the latest run. It does not cover auth, rate limits, or edge cases such as canceling an already-finished run.

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?

A single compact sentence with semicolons, front-loaded with the return content and then the controls and default. Every clause carries useful 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 and annotations cover the safety profile, so the description need not explain return values. It covers the key controls and default target, but leaves minor edge cases unstated, such as canceling a completed run or wait timeout behavior.

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 only 33%, but the description compensates by giving semantics for all three parameters: runId defaults to the latest run, cancel stops it, and waitSeconds waits. It still does not specify runId format or what waitSeconds returns on timeout.

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 resource and return content: progress or final result of a run-test background run. It also names the default (latest run) and ties the result to get-failure, so an agent can distinguish it from run-test and get-failure.

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?

Explains that waitSeconds waits and cancel stops the run, and that the default target is the latest run. It references get-failure for the final result, but does not explicitly say when to poll versus wait or when cancel is inappropriate.

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