Skip to main content
Glama

browser_list_instances

Lists all active browser instances to manage multiple parallel browsing sessions in the Concurrent Browser MCP server.

Instructions

List all browser instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the tool schema for 'browser_list_instances', including name, description, and empty input schema (no parameters required).
    {
      name: 'browser_list_instances',
      description: 'List all browser instances',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Handler case in executeTools method that executes the tool by calling BrowserManager.listInstances().
    case 'browser_list_instances':
      return this.browserManager.listInstances();
  • Core implementation of listing all browser instances, mapping instance data and returning structured ToolResult.
    listInstances(): ToolResult {
      const instanceList = Array.from(this.instances.values()).map(instance => ({
        id: instance.id,
        isActive: instance.isActive,
        createdAt: instance.createdAt.toISOString(),
        lastUsed: instance.lastUsed.toISOString(),
        metadata: instance.metadata,
        currentUrl: instance.page.url()
      }));
    
      return {
        success: true,
        data: {
          instances: instanceList,
          totalCount: this.instances.size,
          maxInstances: this.config.maxInstances
        }
      };
    }
  • src/server.ts:40-45 (registration)
    Registers the MCP listTools handler which returns all tools including 'browser_list_instances' via BrowserTools.getTools().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      const tools = this.browserTools.getTools();
      return {
        tools: tools,
      };
    });
  • src/server.ts:48-75 (registration)
    Registers the MCP callTool handler which dispatches to BrowserTools.executeTools for executing 'browser_list_instances' and other tools.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await this.browserTools.executeTools(name, args || {});
        
        if (result.success) {
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(result.data, null, 2),
              },
            ],
          };
        } else {
          throw new McpError(ErrorCode.InternalError, result.error || 'Tool execution failed');
        }
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        throw new McpError(
          ErrorCode.InternalError,
          `Tool execution failed: ${error instanceof Error ? error.message : error}`
        );
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all browser instances' implies a read-only operation, but it doesn't specify what information is returned (e.g., instance IDs, URLs, status), whether the list is real-time or cached, or if there are any side effects like refreshing instances. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, clear sentence with zero waste. It's front-loaded with the core action ('List all browser instances') and doesn't include any redundant or verbose language. Every word earns its place, making it highly efficient.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on return values, behavior, or usage context. For a list operation with no structured output documentation, the description should ideally specify what information is returned to be more complete.

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?

The tool has 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to explain parameters, but it implicitly confirms there are none by not mentioning any. This is appropriate for a parameterless tool, earning a baseline 4 as it adds no unnecessary information.

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

Purpose4/5

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

The description 'List all browser instances' clearly states the verb ('List') and resource ('browser instances'), making the purpose immediately understandable. It distinguishes this tool from siblings that perform actions on browser instances (like click, navigate, close) rather than listing them. However, it doesn't specify what constitutes a 'browser instance' or the scope of 'all' (e.g., all currently active instances).

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether browser instances must be created first), nor does it differentiate from potential sibling tools like 'browser_get_page_info' which might provide overlapping information. Usage is implied by the name but not explicitly stated.

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/sailaoda/concurrent-browser-mcp'

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