Skip to main content
Glama
manganate006

playwright-spa-mcp

spa_click

Click an element while automatically waiting for the single-page app to stabilize. Handles React, Vue, Angular, and generic SPAs.

Instructions

Click an element with SPA-aware waiting. Waits for DOM to stabilize after click.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to navigate to first (optional)
sessionNoSession IDdefault
spaModeNo
selectorYesCSS selector to click
screenshotNoTake screenshot after action
waitForIdleNoWait for DOM idle after click
Behavior2/5

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

With no annotations, the description carries full burden but only mentions 'waits for DOM to stabilize after click'. It omits details on error handling, return values, destructive nature, or auth requirements.

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 sentences, no fluff, front-loaded with purpose.

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 description does not explain return values, the role of the 'url' parameter, or how the tool interacts with navigation siblings. Given 6 parameters and no output schema, more context is needed.

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 83%, so baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides.

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 'click' and the resource 'element', and specifies 'SPA-aware waiting', which distinguishes it from sibling tools like spa_fill and spa_type_realistic.

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 use for clicking in SPAs requiring DOM stabilization, but does not explicitly state when to use or when not to use, nor does it mention alternatives like spa_iframe_click.

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