playwright-generate-mcp

Overview Schema Source Related Servers Discussions Admin

Set project root

set_project_root

Explicitly set the target project root directory when automated discovery of playwright.config.* fails, ensuring Playwright tests target the correct project.

Instructions

Explicitly set the target project root directory. Use this as a fallback if playwright.config.* cannot be automatically discovered by other tools.

Input Schema

Name	Required	Description	Default
`projectRoot`	Yes	Absolute path to the target project root, e.g. "/home/user/my-app".

Output Schema

Name	Required	Description	Default
`message`	Yes
`projectRoot`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 15, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says 'explicitly set' but does not disclose whether the setting persists across calls/sessions, whether it overrides auto-discovery, what happens if the path is invalid, or any side effects.

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 short sentences, front-loaded with the action and followed by the fallback condition. No 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?

For a single-parameter setter with full schema coverage and an output schema, the description covers the essential purpose and trigger. The main remaining gap is behavioral detail (persistence, override semantics) that no structured field supplies.

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 the sole parameter is documented with type, requirement, and an example path. The description adds no parameter 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.

Purpose4/5

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

States a specific verb+resource: 'set the target project root directory'. It also scopes the tool as a fallback, which helps separate it from check_playwright_config, though it does not name that sibling explicitly.

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?

Gives a clear condition for use: fall back to this when playwright.config.* cannot be auto-discovered. It does not spell out when not to use it (e.g., when discovery succeeds) or name the alternative tools, but the trigger context is explicit.

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

Deploy Server