Skip to main content
Glama

scroll

Move the active or specified browser tab up, down, to the top, or to the bottom by a chosen number of screens to reveal off-screen content.

Instructions

Scroll the page.

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

Input Schema

NameRequiredDescriptionDefault
pagesNoScreens to scroll for up/down. Default 1.
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It does not say whether scrolling is smooth or instant, how far it scrolls, whether it waits, or what is returned; only the basic action is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence is front-loaded and waste-free, but it is under-specified for a three-parameter tool rather than appropriately sized. The brevity reflects missing detail, not efficient structure.

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 three parameters, the definition is too thin. It omits direction semantics, page count behavior, tab targeting, and return or side-effect information.

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 coverage is 67%, and the description adds no meaning for direction, pages, or tabId. The schema documents pages and tabId, but direction's enum values are only in the schema, and the description does not compensate for the remaining gap.

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 ('Scroll') and resource ('the page'), so the action is clear. It does not distinguish from siblings or clarify scope such as viewport versus element, so it is not a 5.

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?

Provides no guidance on when to use this tool versus click, navigate, or other page tools, and gives no exclusions. The description only states the action.

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