Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

get-opened-browser

Retrieve a list of currently active browser instances from the AdsPower LocalAPI MCP Server for profile management and automation tasks.

Instructions

Get the list of opened browsers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the logic for the 'get-opened-browser' tool by querying the API for opened browsers and returning the list.
    async getOpenedBrowser() {
        const response = await axios.get(`${LOCAL_API_BASE}${API_ENDPOINTS.GET_OPENED_BROWSER}`);
        
        if (response.data.code === 0) {
            return `Opened browser list: ${JSON.stringify(response.data.data.list, null, 2)}`;
        }
        throw new Error(`Failed to get opened browsers: ${response.data.msg}`);
    },
  • The input schema for the 'get-opened-browser' tool, which is empty as it requires no parameters.
    emptySchema: z.object({}).strict(),
  • The registration of the 'get-opened-browser' tool in the MCP server, linking to the handler and schema.
    server.tool('get-opened-browser', 'Get the list of opened browsers', schemas.emptySchema.shape,
        wrapHandler(browserHandlers.getOpenedBrowser));
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this returns only currently active browsers, includes browser metadata, shows real-time status, or has any performance considerations. The description is minimal and lacks important 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and gets straight to the point without unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the browser list returns, what information each browser entry contains, whether the list is filtered or comprehensive, or how this differs from similar sibling tools. The minimal description leaves too many questions unanswered.

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 zero parameters with 100% schema coverage, so the schema fully documents the input requirements. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. This meets the baseline expectation for parameterless tools.

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 clearly states the verb ('Get') and resource ('list of opened browsers'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling 'get-browser-list' - both appear to retrieve browser information, creating potential confusion about when to use each.

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 like 'get-browser-list' or 'get-application-list'. There's no mention of prerequisites, timing considerations, or what distinguishes this from similar sibling tools.

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/AdsPower/local-api-mcp-typescript'

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