Skip to main content
Glama

browser_scroll

Read-onlyIdempotent

Scroll. With ref (aria-ref or CSS selector; frame = iframe selector): by default scrolls that element into view; with delta_x/delta_y it wheel-scrolls over it. With no ref: to = 'top' | 'bottom' scrolls the page to its end, otherwise the page is wheel-scrolled by delta_x/delta_y pixels (positive y = down). Returns the resulting scroll position.

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": {
      "page_id": "<page_id>"
    },
    "name": "browser_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
refNo
frameNo
delta_xNo
delta_yNo
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds genuinely new behavioral facts: the two scrolling strategies, the sign convention (positive y = down), and that the resulting scroll position is returned. It does not mention any timing, animation or wait behavior, but the added context is substantive for a read-only tool.

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 content is dense and organized by mode (with `ref` first, then without), with zero filler sentences. The one-word opener 'Scroll.' is minimal but the conditional branches that follow are front-loaded and easy to scan.

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

Completeness4/5

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

With seven parameters, no output schema, and low schema coverage, the description covers the mode logic, parameter meanings and the return value, which is sufficient for correct invocation. Remaining gaps are minor (no note on scroll timing or whether the page must be settled first).

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

Parameters4/5

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

Schema coverage is only 14%, so the description carries most of the burden and does so well — it defines `to` values, what `ref` accepts (aria-ref or CSS selector), that `frame` is an iframe selector, and how delta_x/delta_y behave in each mode. Only `page_id` and `in_workspace` go unexplained, and `in_workspace` is already documented in 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 opens with a concrete verb and then spells out two distinct modes: element-targeted scrolling (into view or wheel-scroll over `ref`) and page-level scrolling (`to` top/bottom or pixel deltas). It is unambiguous about what the tool does and implicitly differentiates from siblings like browser_mouse and browser_press_key, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

It gives clear branching guidance: use `ref` (+ `frame` for iframes) to act on an element, omit `ref` and use `to` for page ends, or omit `ref` and use deltas for pixel scrolling. What is missing is any exclusion guidance — nothing says when to prefer browser_navigate or browser_mouse instead — so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.