Skip to main content
Glama
Sign In
BrowserPilot

BrowserPilot

by soulxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_resize

Resize the browser window to specified pixel dimensions to adapt viewport for responsive testing or screen capture. Provide width and height inputs to set exact window size.

Instructions

Resize browser window

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": "browser_resize"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesWindow width in pixels
heightYesWindow height in pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.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 provided, so the description carries the full burden of disclosing behavior. It only states the primary action and does not mention side effects such as viewport changes, page reloads, or responsive-layout impacts. The agent is left to infer the operational consequences.

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?

The description is extremely concise at six words with no filler or repetition. It is easy to scan and front-loads the action and target resource, though it sacrifices behavioral detail for brevity.

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?

For a simple two-parameter tool, the schema covers the inputs and the description names the target resource. However, with no annotations and no output schema, the description does not fully convey the tool's scope or side effects, making it minimally viable but not fully self-sufficient.

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?

The input schema already documents both parameters with descriptions and pixel units, so schema coverage is 100%. The tool description adds no parameter meaning beyond what the schema provides, which is acceptable given the schema's completeness.

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 a specific verb and resource: resize the browser window. It is distinct from the sibling browser tools, which focus on navigation, input, and inspection, so an agent can recognize the intended operation. It stops short of clarifying whether the viewport or the entire OS window is resized, but the core purpose is unambiguous.

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 or when an alternative would be more appropriate. The intended use is implied by the name, but no context, prerequisites, or exclusions are given.

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

Deploy Server

Other Tools