chatgpt-remote-browser-mcp

Scroll shared browser tab

scroll

Navigate a shared browser tab by moving up or down one or more pages at a time.

Instructions

Scroll a currently shared tab by one or more pages.

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

Input Schema

Name	Required	Description	Default
`pages`	No
`handle`	Yes
`direction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Sep 8, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations indicate non-read-only and non-destructive, which aligns with scrolling. However, the description does not disclose any side effects (e.g., state changes, animation, or limitation when the tab is not shared). It adds minimal behavioral context beyond the annotations.

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?

The description is a single clear sentence with no unnecessary words. It is concise and to the point, effectively communicating the core action in minimal space.

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?

The description is too sparse to be complete. It omits parameter details, expected behavior (e.g., what happens if the tab is not shared or if the end of the page is reached), and any output or return value. With no output schema, the description should provide more context but does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 3 parameters with 0% description coverage. The description only implicitly references 'pages' with 'one or more pages' but leaves 'handle' and 'direction' entirely unexplained. No effort is made to clarify parameter meaning or constraints, so the description fails to compensate for the schema gaps.

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 clearly states the verb 'scroll' and the object 'a currently shared tab', specifying the action of moving by pages. It distinguishes from navigation, typing, and clicking, though it could be slightly more explicit about the page increment semantics.

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?

No guidance is provided on when to use this tool versus alternatives like navigate, type, or click. The description does not mention prerequisites (e.g., tab must be shared) or situations where scrolling is appropriate, leaving the agent to infer context.

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

Deploy Server