Skip to main content
Glama
Lokii0911
by Lokii0911

set_window_size

Adjust the browser window size to exact width and height values, enabling precise viewport control for responsive design testing.

Instructions

Set the browser window size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYes
heightYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration for 'set_window_size' – the @mcp.tool() decorator registers this function as a tool, and it delegates to browser.set_window_size via _run.
    @mcp.tool()
    def set_window_size(width: int, height: int) -> dict[str, Any]:
        """Set the browser window size."""
        return _run("set_window_size", browser.set_window_size, width, height)
  • Actual implementation of set_window_size in BrowserManager – acquires the thread lock, calls Selenium's driver.set_window_size(width, height), and returns the current browser state.
    def set_window_size(self, width: int, height: int) -> BrowserState:
        with self._lock:
            self._require_driver().set_window_size(width, height)
            return self.state()
  • Initial window size is set during driver configuration in _configure_driver using the configured window_width and window_height settings (suppressing errors).
    with suppress(WebDriverException):
        driver.set_window_size(self._settings.window_width, self._settings.window_height)
  • Settings schema defining window_width and window_height with default values and validation constraints used when configuring initial window size.
    window_width: int = Field(default=1440, ge=320, le=7680)
    window_height: int = Field(default=1000, ge=240, le=4320)
  • BrowserState model – the return type of set_window_size, containing session info, URL, title, and window handles.
    class BrowserState(BaseModel):
        session_id: str | None
        current_url: str | None
        title: str | None
        window_handles: list[str]
        active_window_handle: str | None
Behavior2/5

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

With no annotations, the description carries the full burden but only states the action. It does not disclose if the resize is animated, if it waits for completion, or if it affects all windows.

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 a single sentence, very concise and front-loaded. However, it may be too brief to be fully useful, balancing brevity with informativeness.

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 existence of an output schema, the description could omit return values, but it does not mention whether the tool affects the current window or returns success status. With many sibling tools, its role is clear but incomplete.

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 description coverage is 0%, yet the description adds no information about parameter units, valid ranges, or behavior. The parameter names are self-explanatory but the text does not compensate for the lack of schema explanation.

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 clearly states the verb 'Set' and the resource 'browser window size', making the purpose unambiguous. It distinguishes the tool from siblings like 'browser_start' or 'browser_reset'.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to resize vs. open a new window. The description lacks context for appropriate usage.

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/Lokii0911/SeleniumMCP'

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