Skip to main content
Glama

browser_resize

Adjust browser window dimensions to specific width and height values for testing or automation workflows.

Instructions

Resize window

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYes
heightYes

Implementation Reference

  • index.js:434-441 (registration)
    The browser_resize tool is registered using server.tool, taking width and height as input and proxying the call via proxyToolCall.
    server.tool('browser_resize', 'Resize window', {
      width: z.number(),
      height: z.number()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_resize', args);
    });
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to explain synchronous/asynchronous behavior, dimension constraints, viewport vs window distinctions, or error handling for invalid dimensions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

While brief (two words), this constitutes under-specification rather than effective conciseness. The extreme brevity leaves critical information missing rather than efficiently conveyed.

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 lack of annotations, output schema, and parameter descriptions, the two-word description is insufficient for a browser automation tool that affects visible state and requires specific pixel dimensions.

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

Parameters1/5

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

The schema has 0% description coverage for width and height parameters, and the description provides no compensation—failing to specify units (pixels), valid ranges, or whether these represent viewport or window dimensions.

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

Purpose2/5

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

The description 'Resize window' is essentially a tautology that restates the tool name (browser_resize). While it identifies the action (resize) and target (window), it lacks specificity about which window (browser viewport vs OS window) and doesn't distinguish from sibling tools like browser_navigate or browser_click.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus alternatives, prerequisites (e.g., needing an open browser), or specific conditions where resizing is necessary (e.g., responsive testing vs viewport adjustments).

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/OMGEverdo/browser-pool-mcp'

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