Mithwire MCP

browser_scroll

Scroll a browser page to the top, bottom, or a specific selector, enabling precise viewport control during web automation.

Instructions

Scroll page, to top, to bottom, or to selector.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_scroll"
  }
}

Input Schema

Name	Required	Description	Default
`to_top`	No
`delta_y`	No
`selector`	No
`to_bottom`	No
`session_id`	Yes
`wait_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about the wait_seconds settle behavior after scrolling, what happens if to_top and to_bottom are both set, whether scrolling is smooth or instant, or whether the call blocks until the page stabilizes.

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?

A single short sentence with the primary verb front-loaded and the mode list immediately following. It is efficient, though the brevity tips into under-specification rather than pure economy.

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?

An output schema exists so return values need not be explained, but for a six-parameter tool with zero schema description coverage and no annotations, the description is far too thin. An agent cannot determine precedence among the four scroll modes or the role of delta_y versus to_bottom from this text.

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 description coverage is 0% across six parameters, and the description only obliquely accounts for three of them (to_top, to_bottom, selector). It adds no meaning for delta_y, wait_seconds, or the required session_id, and does not explain interaction or precedence between the mode flags.

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 (page) and enumerates the modes: to top, to bottom, or to selector. No sibling tool performs scrolling, so sibling differentiation is not really needed here, but the phrasing is terse and never names the session context it operates on.

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?

The description gives no when-to-use guidance, no prerequisites, and no indication of how to choose between to_top, to_bottom, delta_y, and selector modes. The agent must infer all routing logic from the schema defaults.

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

Deploy Server