Skip to main content
Glama
seleniumbase

seleniumbase-mcp

Official
by seleniumbase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Manage Window

manage_window
Idempotent

Get or change browser window geometry and state: retrieve position and size, set exact coordinates, or maximize and minimize the window.

Instructions

Get or change browser window geometry or state.

Args: action: - "get_rect": Return the current window position and size. - "set_rect": Set x, y, width, and height. All four are required. - "maximize": Maximize the browser window. - "minimize": Minimize the browser window.

x: Horizontal screen position for "set_rect".

y: Vertical screen position for "set_rect".

width: Window width for "set_rect".

height: Window height for "set_rect".

Notes: Use this tool for browser-window geometry and state. Use manage_tabs for switching between browser tabs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
widthNo
actionNoget_rect
heightNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "type": "object"
+        }
+      ],
+      "title": "Result"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "manage_windowOutput",
+  "type": "object"
+}
  2. Addedv1.2.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds the key constraint that set_rect requires all four coordinates ('All four are required'), which is behavioral guidance beyond the schema. It also specifies the return for get_rect ('Return the current window position and size'). No contradiction with annotations; the description complements them.

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 well-organized with clear sections (Args, Notes) and a bulleted list for actions. Every sentence serves a purpose: the action list, parameter explanations, and the routing note. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters but none are required at the schema level; the description explains that action defaults to get_rect and that the other parameters are for set_rect. The output schema exists, so return values are handled elsewhere. The description covers all input semantics, usage guidance, and sibling differentiation—nothing an agent needs is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry full parameter semantics. It explains each action value in detail and clarifies that x, y, width, and height are only relevant to set_rect. The 'All four are required' note prevents misuse. This fully compensates for the lack of schema-side descriptions.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Get or change browser window geometry or state.' It immediately distinguishes itself from the sibling tool manage_tabs, and enumerates the four distinct actions (get_rect, set_rect, maximize, minimize) that map directly to the enum. An agent can clearly tell what this tool does and what it doesn't.

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

Usage Guidelines5/5

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

The Notes section explicitly states when to use this tool ('Use this tool for browser-window geometry and state') and when to use the alternative ('Use manage_tabs for switching between browser tabs'). This direct routing to a sibling tool leaves no ambiguity about selection.

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