Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_tab_list

Retrieve a list of all open browser tabs to manage and navigate your browsing session.

Instructions

browser tab list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that lists all open browser tabs. Uses Playwright's context.pages() to get tab info (index, URL, title, active status).
    async function browserTabList() {
      try {
        const browser = await getBrowser();
        const pages = context ? context.pages() : [];
    
        const tabs = pages.map((p, index) => ({
          index,
          url: p.url(),
          title: p.title(),
          active: p === page
        }));
    
        return {
          success: true,
          tabs,
          count: tabs.length
        };
    
      } catch (error) {
        logger.error(`Error listing tabs: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Registration of browser_tab_list as an MCP tool entry (no input parameters, minimal schema).
    const browserExtras = [
      { n:'browser_navigate_back' }, { n:'browser_navigate_forward' }, { n:'browser_hover' }, { n:'browser_drag' },
      { n:'browser_select_option' }, { n:'browser_press_key' }, { n:'browser_snapshot' }, { n:'browser_console_messages' },
      { n:'browser_network_requests' }, { n:'browser_tab_list' }, { n:'browser_tab_new' }, { n:'browser_tab_select' },
      { n:'browser_tab_close' }, { n:'browser_file_upload' }, { n:'browser_wait' }, { n:'browser_wait_for' },
      { n:'browser_resize' }, { n:'browser_handle_dialog' }
    ];
    for (const b of browserExtras) {
      tools.push({ name: b.n, description: b.n.replace(/_/g,' '), inputSchema: { type:'object', properties:{} } });
    }
  • Dispatch handler in server.js that calls browserTools.browserTabList() when the tool is invoked.
    case 'browser_tab_list': data = await browserTools.browserTabList(); break;
  • Module-level state variables for browser, context, and page used by browserTabList.
    let browser = null;
    let context = null;
  • Export of browserTabList from the browser_tools module.
      browserTabList,
      browserTabNew,
      browserTabSelect,
      browserTabClose,
      
      // Utilities
      browserConsoleMessages,
      browserFileUpload,
      browserWait,
      browserWaitFor,
      browserResize,
      browserHandleDialog,
      browserClose,
      browserInstall,
      browserNetworkRequests
    };
Behavior1/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 disclosure. It states nothing about side effects, read-only nature, permissions, or output format, leaving the agent without critical behavioral context.

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 short but under-specified. Conciseness is not the same as missing information; the description wastes its only sentence by restating the name.

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?

Given zero parameters and no annotations, the description should explain what 'tab list' entails—whether it lists tabs from all windows, active window, or some default. It also lacks any mention of the output schema or related tool distinctions.

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?

Although there are no parameters (baseline 4), the description fails to add any value beyond the schema. It does not hint at what the tool returns or how filtering/scope works, which would be beneficial given it provides no parameters.

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 list' is a tautology that merely repeats the tool name without specifying any verb or resource. It fails to clarify what the tool does, e.g., whether it lists all open tabs or tab metadata.

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 provided on when to use this tool versus sibling tools like browser_tab_select, browser_tab_new, or browser_tab_close. There is no mention of context, prerequisites, or exclusivity.

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