Skip to main content
Glama
Novpix

browsermcp-plus

by Novpix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_scroll

Scroll the page with the mouse wheel by pixel offsets or bring an element into view. Use it to reveal off-screen content, then optionally return a snapshot.

Instructions

Scroll the page with the mouse wheel by a number of pixels, or scroll an element from the snapshot into view

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoElement to scroll into view instead
deltaXNoHorizontal pixels; positive scrolls right
deltaYNoVertical pixels; positive scrolls down
elementNoHuman-readable element description used to obtain permission to interact with the element
snapshotNoAlso return the page snapshot after the action (default: no). Use it when you need to see the result right away.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / snapshot
      Added value: +{
+  "description": "Also return the page snapshot after the action (default: no). Use it when you need to see the result right away.",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral fact that there are two distinct modes (viewport pixel scroll vs. bringing a snapshot element into view), but says nothing about the permission flow for the element parameter, whether ref and deltaX/deltaY are mutually exclusive, or what happens on an empty call.

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?

A single well-formed sentence with zero filler, front-loading the primary action and immediately covering the secondary mode. Nothing to trim.

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?

For a 5-parameter tool with no required parameters, no output schema, and existing annotations, the description covers the two modes adequately but leaves gaps: it does not explain the default behavior when called with no arguments, how ref and delta values interact, or that ref/element derive from a prior snapshot. Complete enough to call, but not fully specified.

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 every parameter is already documented in the schema, including direction conventions and the snapshot default. The description adds no syntax or interaction detail beyond that, and notably omits that ref and deltaX/deltaY represent alternative modes. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb (scroll) and resource (the page / an element from the snapshot) and clearly distinguishes its two operating modes: pixel-based mouse-wheel scrolling and scroll-into-view. It does not explicitly differentiate itself from siblings like browser_click or browser_press_key, but the purpose is unambiguous.

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?

There is no explicit when-to-use/when-not guidance or mention of alternatives; usage is only implied (scroll when content is off-screen). The snapshot parameter's schema text carries a small usage hint ('Use it when you need to see the result right away'), but the top-level description offers no routing guidance.

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