Skip to main content
Glama
Sign In
agent-browser-mcp

agent-browser-mcp

by zy2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_scroll

Scroll a web page or a specific scrollable container by direction and pixel amount, using an element ref to target containers when needed.

Instructions

滚动页面或指定滚动容器(带 ref 时滚动该容器)。方向 + 像素量。

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": "browser_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo滚动该容器(快照中带 [可滚动] 标记的元素)
amountNo滚动像素(默认 600)
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals the two scroll targets but says nothing about whether the call waits for scrolling to settle, whether lazy-loaded content is triggered, what is returned (no output schema exists), or whether a fresh snapshot is needed afterward — meaningful gaps for a state-changing browser interaction.

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?

Two short, front-loaded clauses with no filler; the page-versus-container rule appears first. The trailing 'direction + pixel amount' fragment is close to redundant with the schema but does signal the required inputs quickly.

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?

For a browser-mutating tool with zero annotations and no output schema, the definition is thin: it omits return behavior, completion semantics, and the snapshot/ref lifecycle an agent needs before calling it. Three parameters at 67% coverage mostly self-document, but the behavioral side is under-described.

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 67%, with ref and amount already documented in the schema, including the 600 default. The description restates the ref-as-container semantics and 'direction + pixel amount' but adds no format or edge-case meaning beyond the structured fields, so baseline 3 applies.

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 page or a designated scroll container, and it explicitly conditions the container case on providing a ref. It is clearly separable from siblings like browser_click or browser_hover, though it never names an alternative.

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?

Usage is only implied: pass a ref to scroll inside a container, omit it to scroll the page, and always supply a direction. There is no guidance on prerequisites (e.g., needing a snapshot to obtain a ref) or on when scrolling is preferable to other navigation approaches.

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