kiro-frontend-engineer-mcp

Overview Schema Source Related Servers Discussions Admin

execute_playwright_test

Run local Playwright E2E test suites on generated components and capture terminal logs, pass/fail results, and error screenshots.

Instructions

Run local Playwright E2E test suites on generated components. Captures terminal logs, test pass/fail results, and error screenshots.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "testPath": "<testPath>"
    },
    "name": "execute_playwright_test"
  }
}

Input Schema

Name	Required	Description	Default
`testPath`	Yes	Path to test file or directory (relative to project root)
`headed`	No	Run in headed mode for debugging (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses captured outputs (logs, results, screenshots) but omits other behavioral traits like side effects (e.g., file modifications, network requests) or prerequisites. It is not misleading but could be more comprehensive.

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?

The description is two sentences long, front-loads the purpose, and includes essential details without any fluff. Every sentence adds value.

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?

For a tool with no output schema, the description covers key outputs (logs, results, screenshots). It could mention error handling or prerequisites (e.g., test framework setup), but overall it provides sufficient context for an agent to understand the tool's function and outputs.

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% and parameter descriptions are clear. The tool description does not add additional semantics beyond what the schema already provides, so baseline 3 is appropriate.

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?

The description clearly states the verb 'run' and the resource 'local Playwright E2E test suites' with scope 'on generated components'. It also lists captured artifacts (logs, results, screenshots). This fully defines the tool's purpose and distinguishes it from sibling tools (GitHub comments, CI logs, CLI).

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

Usage Guidelines3/5

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

The description implies when to use (for running Playwright tests) but provides no explicit when-not-to-use instructions or alternatives. Given sibling tools are unrelated, the implicit usage is adequate but not scored higher due to lack of explicit guidance.

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

Deploy Server