Skip to main content
Glama

resize_window

Resize the browser window containing a specified tab by setting its width and height, so you can control viewport dimensions for testing or layout checks.

Instructions

Resize the browser window containing a tab.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID, from tabs_list or tab_create
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.7/5.0
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 behavioral burden and does not meet it. The phrase 'containing a tab' hints that resizing is window-scoped and may affect sibling tabs, but it never states that consequence, nor whether the tab must be foregrounded, what permissions are needed, or what happens on invalid or out-of-range dimensions.

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

Conciseness4/5

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

One front-loaded sentence with zero filler, and the key object (the window containing the tab) appears immediately. It is efficient rather than padded, though the brevity leaves gaps captured under other dimensions.

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 three-required-parameter mutation with no annotations and no output schema, the description should specify units and side effects on other tabs in the same window. Those omissions mean an agent could call it correctly in form but incorrectly in effect.

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

Parameters2/5

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

Schema coverage is only 33%: tabId is documented in the schema, but width and height have no descriptions at all. The description does not compensate by giving units (CSS pixels? device pixels?), constraints, or default/limit behavior, so an agent cannot reliably choose values.

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 states a specific verb and resource: resize the browser window that holds a given tab. That is distinguishable from siblings such as navigate, scroll, or screenshot, none of which change window geometry. It stops short of 5 because it says nothing about viewport vs. outer window size.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. an active/attached tab), and no exclusions or alternatives. The only implied usage is 'call this when you want a particular window size', which the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.