Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

open-new-page

Open a new browser page within AdsPower profiles to manage multiple browsing sessions for testing and automation tasks.

Instructions

Open a new page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'open-new-page' tool. It checks if the browser is connected, creates a new page in the current context using Puppeteer, sets it as the current page instance, and returns a success message.
    async openNewPage() {
        browser.checkConnected();
        const newPage = await browser.pageInstance!.context().newPage();
        browser.pageInstance = newPage;
        return `New page opened successfully`;
    },
  • The schema used for the 'open-new-page' tool, which is an empty object schema indicating no input parameters are required.
    emptySchema: z.object({}).strict(),
  • Registers the 'open-new-page' tool with the MCP server, providing the tool name, description, input schema, and the wrapped handler function.
    server.tool('open-new-page', 'Open a new page', schemas.emptySchema.shape,
        wrapHandler(automationHandlers.openNewPage));
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. 'Open a new page' implies a creation/mutation action, but it doesn't disclose behavioral traits such as whether this requires an existing browser context, what happens if no browser is open, or if it returns a page identifier. For a tool with zero annotation coverage, this leaves critical operational details unspecified.

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 extremely concise with just three words, front-loading the core action. Every word earns its place by specifying the verb and object without any fluff or redundant information. It's appropriately sized for a simple tool with no parameters.

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?

Given the tool's apparent complexity (likely interacting with a browser to open pages) and lack of annotations or output schema, the description is incomplete. It doesn't explain prerequisites (e.g., needing an open browser), return values, or error conditions. For a tool in a browser automation context with many siblings, more context is needed to guide effective use.

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%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly doesn't mention any. A baseline of 4 is appropriate since no parameter information is required, and the description doesn't mislead about parameters.

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

Purpose3/5

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

The description 'Open a new page' clearly states the action (open) and resource (new page), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'navigate' or 'open-browser', leaving ambiguity about whether this opens a new tab/window or navigates within an existing page. It's not tautological but remains somewhat vague.

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. With siblings like 'navigate' (for changing URLs) and 'open-browser' (for launching browsers), it's unclear if this tool is for opening new tabs, windows, or something else. No explicit when/when-not or alternative recommendations are included.

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