Skip to main content
Glama

browser_scroll

browser_scroll

Scroll a browser tab by a pixel delta and report whether the top or bottom boundary is reached.

Instructions

Scroll the document by a pixel delta, reporting whether it reached the top or bottom.

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": {
      "tab_id": "<tab_id>",
      "delta_x": "<delta_x>",
      "delta_y": "<delta_y>"
    },
    "name": "browser_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
delta_xYes
delta_yYes
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, which is consistent with a repeatable viewport mutation. The description adds the useful behavioral detail that the call returns edge-reached state, but omits sign conventions for deltas, scroll settling/animation behavior, and lazy-load network side effects implied by openWorldHint=true.

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?

One sentence, front-loaded with the action and ending with the return-value behavior. Nothing redundant or buried.

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?

With five parameters, three required, no output schema and openWorldHint=true, the description does cover the action and a key return signal, which is more than most. However, it leaves the most consequential ambiguities (delta sign/units semantics, document-vs-element scope, repeated-call behavior for infinite scroll) unaddressed.

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 60%: tab_id, session_id and session_name are documented, but delta_x and delta_y have no descriptions beyond 'number'. The phrase 'pixel delta' supplies units and implicitly ties the deltas to top/bottom detection, but direction conventions (negative = up/left) and zero-delta behavior remain undocumented.

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 ('scroll the document by a pixel delta') and previews the result ('reporting whether it reached the top or bottom'), which clearly separates it from siblings like browser_click or browser_get_page. It stops short of naming a sibling or scoping the target (document only, not elements), so it is clear but not maximally differentiating.

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 versus alternatives (e.g., browser_wait_for_element or browser_get_interactives for reaching a specific element), no advice on delta magnitude, and no note on whether repeated calls are needed to trigger lazy loading. The agent gets purpose but no decision context.

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