Skip to main content
Glama

scroll

Moves the viewport or a scrollable area to reveal content, and brings a referenced element into view when no direction is given.

Instructions

Scroll the page or a scrollable area. With ref and no direction, scrolls that element into view.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement reference from read_page or find, e.g. "e12"
tabIdYesTab ID, from tabs_list or tab_create
amountNoPixels, default 600
directionNo
coordinateNoScroll the scrollable area under this point

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations the description carries the full burden and it does disclose the non-obvious branch: ref without direction becomes an element-into-view scroll rather than a pixel scroll. It does not say whether scrolling is animated or instant, whether it waits for scroll to settle before returning, or what happens when the page is already at the boundary.

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?

Two sentences, zero filler, with the primary mode stated first and the special case immediately after. Nothing needs to be trimmed.

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?

For a five-parameter browser tool with no annotations and no output schema, the description covers both operating modes and the element-into-view edge case that an agent would otherwise get wrong. The remaining gaps — return value and post-scroll settling behavior — are minor for this tool class.

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 coverage is 80%, so the schema already documents ref, tabId, amount default of 600, and the coordinate semantics, which sets the baseline at 3. The description adds the interaction rule between ref and direction, but the coordinate-based scroll path is left entirely to 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?

States a specific verb and resource ("Scroll the page or a scrollable area") and distinguishes two modes: directional scrolling versus element-into-view when ref is supplied without direction. That is enough to separate it from siblings like hover, click, or read_page, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The one conditional it gives — "with ref and no direction, scrolls that element into view" — is genuinely useful routing logic, but there is no guidance on when to scroll at all versus using find/read_page first, and no exclusions or prerequisites.

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