Skip to main content
Glama
cuber-it

mcp-playwright-tools

by cuber-it

switch_tab

Switch to a specific browser tab using its numeric ID. Move focus between open tabs during automated testing.

Instructions

Switch to a tab by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'Switch to a tab by ID'. It does not explain side effects, error handling (e.g., invalid ID), or whether it changes focus or waits for the tab to load.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loaded, but it is too brief to be adequately informative. It could be expanded slightly without losing conciseness.

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?

Given the simplicity of the tool, the description is insufficient. It lacks details on valid inputs, output (though an output schema exists, its content is unknown), and failure modes. The agent may not know how to obtain the tab ID or what happens on failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no descriptions for tab_id (0% coverage). The description adds only 'by ID', which provides minimal meaning beyond the schema. It does not clarify what the ID represents (index, handle, etc.) or how to obtain it.

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 'Switch' and the resource 'a tab', specifying the action of changing the active tab. It is distinct from sibling tools like close_tab, new_tab, or list_tabs.

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 like list_tabs or close_tab. No mention of prerequisites or when not to use it.

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/cuber-it/mcp_playwright_tools'

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