Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

scroll

Move the page or a selected element by specified horizontal and vertical pixel amounts to reach off-screen content in a browser tab.

Instructions

Scroll the page or a specific element

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": {
      "y": "<y>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoHorizontal scroll amount in pixels
yYesVertical scroll amount in pixels
tabIdNoTab ID (optional)
selectorNoCSS selector to scroll (optional, defaults to page)

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 it discloses almost nothing: not whether the scroll is instant or smooth, whether it waits for completion, whether it triggers lazy-loading, what happens if the selector matches nothing, or what is returned. For a tool with zero annotation coverage this is a substantial gap, though the operation is conceptually simple and low-risk.

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 eight-word sentence with zero padding and the core action front-loaded. It is efficient, though the brevity edges into under-specification rather than tightness, which is penalized in the 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?

With no annotations, no output schema, and a required y parameter, the definition should say at minimum whether scrolling is awaited and what a selector miss does. The schema covers parameter meaning well, but the behavioral context an agent needs to call this correctly is missing.

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 description coverage is 100%, so x, y, tabId, and selector are already documented, and the baseline of 3 applies. The phrase "a specific element" loosely reinforces the selector parameter's role (target element versus whole page), but adds no format, unit, sign, or default detail beyond the schema.

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 ("Scroll") and two target resources ("the page or a specific element"), which is enough for an agent to know exactly what the tool does. It does not differentiate itself from any sibling, though among the listed tools scrolling is a distinct action, so the lack of explicit differentiation costs little.

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 guidance on when to reach for scroll versus alternatives such as click, press_key, or take_snapshot, nor any prerequisite or exclusion. The only implied usage cue is the phrase "or a specific element," which hints that a selector targets an element rather than the page but never says so directly.

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