Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

resize_window

Adjust the browser viewport to a specified pixel width and height, optionally targeting a specific tab.

Instructions

Resize the browser viewport

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
widthYesViewport width in pixels
heightYesViewport height in pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not say whether the resize applies to the current tab only or all tabs, what happens when tabId is omitted, whether the resize persists across navigation, or whether the change is reversible. For a mutation of browser session state, this leaves the agent guessing.

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?

A single front-loaded clause with zero waste. It is efficient, though its brevity overlaps with under-specification rather than pure conciseness.

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?

The tool is simple and the schema is fully documented, but with no annotations and no output schema, the description should at minimum state the scope of the resize and the default target tab. Those behavioral essentials are absent, so the definition is not complete enough for confident invocation.

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 coverage is 100%, so width and height are already documented as pixel dimensions and tabId as optional. The description adds no meaning beyond the schema, such as units, defaults, or how tabId resolves. Baseline 3 is appropriate when the schema does the work.

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 gives a specific verb and resource: 'Resize the browser viewport'. An agent knows exactly what the tool does. However, it does not distinguish from the sibling 'emulate', which may also alter viewport/device dimensions, so the boundary between the two is left to inference.

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 or when-not-to-use guidance, and no named alternative. The agent must guess why it would resize the viewport instead of using 'emulate' or 'take_screenshot' at a different size.

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