Skip to main content
Glama

new_page

Load a specified URL in a new Chrome browser page for automation, debugging, or testing purposes using Chrome DevTools.

Instructions

Creates a new page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to load in a new page.
timeoutNoMaximum wait time in milliseconds. If set to 0, the default timeout will be used.

Implementation Reference

  • The handler function for the 'new_page' tool. It creates a new page using context.newPage(), navigates to the provided URL with optional timeout, waits for post-navigation events, and includes updated pages in the response.
    handler: async (request, response, context) => {
      const page = await context.newPage();
    
      await context.waitForEventsAfterAction(async () => {
        await page.goto(request.params.url, {
          timeout: request.params.timeout,
        });
      });
    
      response.setIncludePages(true);
    },
  • The input schema for the 'new_page' tool, defining the required 'url' parameter and optional 'timeout' from timeoutSchema.
    schema: {
      url: z.string().describe('URL to load in a new page.'),
      ...timeoutSchema,
    },
  • src/main.ts:307-320 (registration)
    Global registration of all tools into the MCP server, including the new_page tool via pagesTools module.
    const tools = [
      ...Object.values(consoleTools),
      ...Object.values(emulationTools),
      ...Object.values(inputTools),
      ...Object.values(networkTools),
      ...Object.values(pagesTools),
      ...Object.values(performanceTools),
      ...Object.values(screenshotTools),
      ...Object.values(scriptTools),
      ...Object.values(snapshotTools),
    ];
    for (const tool of tools) {
      registerTool(tool as unknown as ToolDefinition);
    }
  • The McpContext.newPage() helper method called by the tool handler. Creates a new browser page, updates the pages snapshot, sets it as selected, adds collectors, and returns the page.
    async newPage(): Promise<Page> {
      const page = await this.browser.newPage();
      const pages = await this.createPagesSnapshot();
      this.setSelectedPageIdx(pages.indexOf(page));
      this.#networkCollector.addPage(page);
      this.#consoleCollector.addPage(page);
      return page;
    }
Behavior3/5

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

Annotations indicate readOnlyHint=false, consistent with the 'creates' action implying a write operation. The description adds no behavioral details beyond this, such as whether the page becomes active, if it loads in background, or any side effects. With annotations covering the basic safety profile, it meets the baseline but lacks additional 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 extremely concise with just three words, front-loading the core action. Every word earns its place, and there's no wasted text, making it highly efficient for quick understanding.

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 complexity of creating a new page (a write operation with potential side effects), no output schema, and minimal annotations, the description is insufficient. It doesn't explain what happens after creation, error conditions, or how it interacts with sibling tools, leaving significant gaps for an agent.

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

Parameters3/5

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

Schema description coverage is 100%, with clear documentation for both 'url' and 'timeout' parameters. The description adds no additional meaning beyond what the schema provides, such as explaining URL requirements or timeout implications. Baseline 3 is appropriate when schema does the heavy lifting.

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 'creates' and the resource 'new page', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'navigate_page' or 'select_page' which also involve page operations, so it doesn't reach the highest score.

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 'navigate_page' or 'select_page', nor does it mention prerequisites or context for creating a new page. It simply states what it does without usage context.

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/SHAY5555-gif/chrome-devtools-mcp'

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