Skip to main content
Glama
nzjami

Playwright MCP

by nzjami

browser_resize

Destructive

Adjust browser window dimensions to test responsive web designs or simulate different screen sizes for automated testing.

Instructions

Resize the browser window

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYesWidth of the browser window
heightYesHeight of the browser window

Implementation Reference

  • The handler function for the 'browser_resize' tool. It adds explanatory code comments to the response and resizes the browser viewport to the specified width and height using the page.setViewportSize method within a waitForCompletion block.
    handle: async (tab, params, response) => {
      response.addCode(`// Resize browser window to ${params.width}x${params.height}`);
      response.addCode(`await page.setViewportSize({ width: ${params.width}, height: ${params.height} });`);
    
      await tab.waitForCompletion(async () => {
        await tab.page.setViewportSize({ width: params.width, height: params.height });
      });
    },
  • Schema definition for the 'browser_resize' tool, including name, title, description, input schema validating width and height as numbers, and type as readOnly.
    schema: {
      name: 'browser_resize',
      title: 'Resize browser window',
      description: 'Resize the browser window',
      inputSchema: z.object({
        width: z.number().describe('Width of the browser window'),
        height: z.number().describe('Height of the browser window'),
      }),
      type: 'readOnly',
    },
  • src/tools.ts:36-52 (registration)
    Central registration of all tools, including 'browser_resize' via spreading the exports from common.ts (which defines browser_resize) into the allTools array.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description does not contradict. However, the description adds minimal behavioral context beyond annotations—it does not explain what 'resize' entails (e.g., whether it affects viewport, triggers events, or has side effects like reloading). With annotations covering safety, a baseline score is appropriate, but more detail would improve transparency.

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, direct sentence—'Resize the browser window'—with no unnecessary words. It is front-loaded and efficiently conveys the core action, making it easy for an AI agent to parse quickly without clutter.

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 moderate complexity (a destructive operation with two parameters), annotations provide safety hints, but there is no output schema. The description is minimal and does not address potential outcomes, errors, or dependencies (e.g., needing an open browser). It is adequate as a basic descriptor but lacks depth for full contextual understanding.

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 descriptions for 'width' and 'height' parameters. The description does not add any meaning beyond the schema (e.g., units, valid ranges, or default behaviors). According to the rules, with high schema coverage, the baseline score is 3, as the schema adequately documents parameters without extra description input.

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 'Resize the browser window' clearly states the verb ('Resize') and resource ('browser window'), making the purpose immediately understandable. However, it does not differentiate this tool from its siblings (e.g., browser_snapshot or browser_take_screenshot, which also relate to browser window manipulation), so it falls short of a perfect 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. For example, it does not mention whether this is for testing layouts, simulating device sizes, or other contexts, nor does it reference sibling tools like browser_snapshot for capturing the resized window. This lack of contextual usage information limits its effectiveness for an AI agent.

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/nzjami/mcpPlaywright'

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