tabpilot-mcp

Overview Schema Source Related Servers Discussions Admin

activate_tab

Bring a specific browser tab to the front and focus its window, making it visible to the user or for screen captures. Use when you need to observe the active page or record the desktop.

Instructions

Bring a target browser tab to the front and focus its window.

Side effects: Changes system window focus and switches the user's active tab viewport. Does not reload the page or alter DOM state.

Usage guidelines:

When to use: Use when a human user needs to observe the active page, or before capturing desktop-wide OS screenshots and video screencasts.
When NOT to use: Do NOT call this before reading or interacting with tabs. TabPilot tools (read_tab, query_dom, click, fill, eval_js, screenshot) work off-screen in background tabs without stealing focus.

Args: tab_id: Exact tab identifier (e.g. from list_tabs). If omitted, uses the frontmost tab or matches by url_pattern. url_pattern: Optional regex pattern matched against tab URLs (e.g. 'github.com').

Returns: Confirmation message containing the activated tab ID and title/URL. Returns an error message if no matching tab is found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tab_id`	No
`url_pattern`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 17, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses side effects (changes system window focus, switches active tab viewport) and explicitly states non-effects (does not reload or alter DOM). This is thorough and accurate, going beyond a generic 'activates a tab' statement.

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?

The description is well-structured with clear section headers (Side effects, Usage guidelines, Args, Returns). Each sentence adds value; nothing is redundant. It is front-loaded with the core action and side effects before diving into usage and parameters, making it easy to parse quickly.

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

Completeness5/5

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

Given the tool's moderate complexity and lack of annotations, the description covers all necessary context: what it does, side effects, when to use/avoid, parameter details, and return behavior. The presence of an output schema (though not shown) is complemented by the description's explicit note about error messages. Nothing essential is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It provides detailed semantics for both parameters: 'tab_id' is explained as an exact identifier from 'list_tabs' with fallback behavior, and 'url_pattern' is described as a regex pattern with an example. This adds meaningful context that the raw schema (types and defaults only) lacks.

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 opens with a specific verb and resource: 'Bring a target browser tab to the front and focus its window.' It immediately distinguishes itself from sibling tools by explicitly noting that TabPilot tools work off-screen without stealing focus, so the agent can clearly identify when to use this tool versus others.

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

Usage Guidelines5/5

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

The 'When to use' and 'When NOT to use' sections are explicit and actionable. It names concrete scenarios (observation, screenshots) and explicitly forbids use before reading/interacting, listing the alternative tools. This leaves no ambiguity about when to invoke this tool.

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

Deploy Server