Skip to main content
Glama
manganate006

playwright-spa-mcp

spa_evaluate

Execute custom JavaScript in the page context to test or manipulate single-page app behavior, with optional navigation and session management.

Instructions

Execute JavaScript in the page context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to navigate to first (optional)
scriptYesJavaScript code to execute
sessionNoSession IDdefault
Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral traits such as side effects, security implications, or that the result is the script's return value.

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 description is a single, efficient sentence, but it omits potentially valuable information; still, it is not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool executes arbitrary JavaScript, yet the description does not mention return values, error handling, or side effects, leaving the agent with significant uncertainty about its behavior.

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 already describes each parameter; the description adds no extra meaning beyond the schema.

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?

Description clearly states the action ('Execute JavaScript') and the context ('in the page context'), making it distinct from sibling tools that focus on UI interactions like clicks or fills.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., spa_assert, spa_get_text), nor any mention of prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manganate006/playwright-spa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server