Skip to main content
Glama
manganate006

playwright-spa-mcp

spa_iframe_click

Click an element inside a specified iframe, with optional prior navigation and screenshot capture.

Instructions

Click an element inside an iframe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to navigate to first (optional)
frameYesCSS selector for the iframe
sessionNoSession IDdefault
selectorYesCSS selector for element inside iframe
screenshotNoTake screenshot after action
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as loading requirements, error handling, or cross-origin limitations. The description carries full burden for transparency but only states the basic action.

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?

A single sentence that is front-loaded and efficient. However, the brevity sacrifices necessary detail.

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 has 5 parameters and no output schema. The description is too brief for the complexity of clicking inside an iframe, failing to explain navigation, iframe readiness, or screenshot 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 description coverage is 100%, so parameters are already documented. The tool description adds no extra meaning beyond what the schema provides. 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 is 'Click an element inside an iframe.' It clearly specifies the action (click) and the target resource (element inside an iframe), which distinguishes it from siblings like spa_click (click on main page) and spa_iframe_fill (fill inside iframe).

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or exclusion criteria. For example, it does not clarify when to use spa_iframe_click vs spa_iframe_fill.

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