Skip to main content
Glama
Zindaar

operagx-connector-plus

by Zindaar

Scroll

operagx_scroll

Simulates a real mouse-wheel scroll on a page, or scrolls a specific element into view, to load more content or reveal a desired part of the page.

Instructions

Scrolls the page with a real mouse-wheel event, or scrolls a specific element into view.

Args:

  • tabId / tabIndex / matchUrl / matchTitle (optional): which tab.

  • elementId / selector (optional): if given, scrolls that element into view instead of wheel-scrolling the page.

  • deltaX / deltaY (number, default 0): wheel scroll amount in CSS pixels, used only when no elementId/selector is given.

Returns: Either { "ok": true, "scrolledTo": { "x": number, "y": number, "selector"?: string } } or { "ok": true, "delta": { "x": number, "y": number } }

Examples:

  • Use when: "scroll down to load more results" -> scroll with deltaY=800.

  • Use when: "scroll the footer link into view" -> scroll with that link's elementId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab id from operagx_list_tabs. Omit to use the first open tab.
deltaXNo
deltaYNo
matchUrlNoPick the tab whose URL contains this substring.
selectorNo
tabIndexNoZero-based tab index, alternative to tabId.
elementIdNo
matchTitleNoPick the tab whose title contains this substring.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
deltaNo
scrolledToNo
Behavior4/5

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

Annotations convey non-read-only and non-destructive, but the description adds significant context: it uses a real mouse-wheel event, delta units are CSS pixels, and the exact return shapes differ by mode. This extra detail helps an agent predict behavior without invoking the tool.

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 well-structured with Args, Returns, and Examples. It is concise, with no filler, and the two examples are practical and directly informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 8 optional params and two behavior modes, the description covers tab selection, scroll mode precedence, return values, and example scenarios. Combined with an output schema, it provides a complete picture for an agent to select and call the tool correctly.

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

Parameters5/5

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

The schema covers only 50% of parameters with descriptions. The description compensates by grouping tab selectors, explaining the independent roles of elementId/selector vs deltaX/deltaY, and clarifying that delta applies only when no element target is given. This adds essential meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it scrolls the page with a real mouse-wheel event or scrolls a specific element into view. The two modes are distinct and well-defined, and the tool is easily differentiated from sibling interaction tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit conditional guidance: elementId/selector triggers element scrolling, otherwise deltaX/deltaY controls wheel scrolling. Includes practical 'Use when' examples. Does not explicitly name sibling tools as alternatives, but the guidance is clear enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zindaar/operagx-connector-plus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server