Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_tab_select

Select a browser tab to bring it into focus. Use this tool to switch between open tabs during browser automation tasks.

Instructions

browser tab select

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that selects a browser tab by index. Validates input, gets the page from the context's page list, calls bringToFront() to switch to it, and returns success with the tab's URL and title.
    async function browserTabSelect(index) {
      try {
        if (index === undefined || isNaN(index)) {
          return {
            success: false,
            message: 'Tab index is required'
          };
        }
    
        const browser = await getBrowser();
        const pages = context ? context.pages() : [];
    
        if (index < 0 || index >= pages.length) {
          return {
            success: false,
            message: `Invalid tab index: ${index}. Valid range: 0-${pages.length - 1}`
          };
        }
    
        page = pages[index];
        await page.bringToFront();
    
        return {
          success: true,
          message: `Switched to tab ${index}`,
          index,
          url: page.url(),
          title: await page.title()
        };
    
      } catch (error) {
        logger.error(`Error selecting tab: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Routes the 'browser_tab_select' MCP tool call to the browserTabSelect handler function, passing args.index.
    case 'browser_tab_select': data = await browserTools.browserTabSelect(args.index); break;
  • Registers 'browser_tab_select' in the tools/list response's browserExtras array so it appears as an available MCP tool.
    { n:'browser_network_requests' }, { n:'browser_tab_list' }, { n:'browser_tab_new' }, { n:'browser_tab_select' },
  • Helper function used by browserTabSelect (via getBrowser) to retrieve or create the current page context.
    async function getPage() {
      if (!page || page.isClosed()) {
        const browser = await getBrowser();
        if (!context) {
          context = await browser.newContext();
        }
        page = await context.newPage();
      }
      return page;
    }
  • Exports browserTabSelect from the module.exports so it can be imported by server.js.
    browserTabSelect,
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., whether selection changes focus, requires user confirmation, or modifies state).

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

Conciseness2/5

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

The description is extremely brief but lacks substance. Concision should be accompanied by completeness; here, it is under-specified.

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

Completeness1/5

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

For a tool with no parameters and no output schema, the description still fails to explain what 'select' means operationally, leaving the agent without sufficient context.

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

Parameters4/5

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

There are zero parameters, so schema coverage is 100%. The baseline for 0 params is 4. The description adds no parameter information, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'browser tab select' is a tautology of the tool name. It provides no specific verb or resource nuance, nor does it distinguish this tool from siblings like browser_tab_close or browser_tab_list.

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

Usage Guidelines1/5

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

No guidance is given on when to use this tool versus alternatives. The description fails to indicate prerequisites or context of use.

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/FutureAtoms/agentic-control-framework'

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