Skip to main content
Glama
Sign In
BrowserMCP Extended

BrowserMCP Extended

by NEO10111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_scroll

Scroll a web page or a specific element to exact coordinates or into view using CSS selectors, enabling precise navigation and element visibility in automated browser tasks.

Instructions

Scroll the page or a specific element to given coordinates or into view

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoHorizontal scroll position in pixels (default: 0)
yNoVertical scroll position in pixels
behaviorNoScroll behavior
selectorNoCSS selector to scroll into view (takes priority over x/y)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.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 behavioral disclosure. It does not state whether scrolling is animated, whether it waits for completion, how selector priority works, or what the observable result is beyond the short purpose statement.

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, front-loaded sentence with no wasted language. It is appropriately sized for a simple tool, though its brevity leaves behavioral gaps unaddressed.

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?

The tool is simple and the schema is well described, so minimal prose is defensible. However, with no annotations and no output schema, the description should do more to explain observable behavior and selector priority rather than relying entirely on the schema.

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 all four parameters are already documented in the schema. The description adds no parameter-level detail beyond the schema, such as default behavior when both selector and coordinates are provided.

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 and resource: scrolling the page or a specific element, either to coordinates or into view. It is clear what the tool does, though it does not explicitly differentiate itself from related navigation tools such as browser_navigate or browser_wait.

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 use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer that this is for scrolling after navigation or before interacting with off-screen elements.

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