Skip to main content
Glama

safari_scroll_to

Scroll to specific coordinates on a webpage using Safari automation. Set X and Y positions to navigate content precisely.

Instructions

Scroll to a specific position on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position (default: 0)
yNoY position (default: 0)

Implementation Reference

  • Logic for scrolling to a specific coordinate when finding an element by reference (mcpFindRef). This is a core part of the scroll functionality implemented in the helpers.
    if (m.cx !== undefined && m.cy !== undefined) {
      try {
        window.scrollTo(window.scrollX, Math.max(0, m.cy - window.innerHeight / 2));
      } catch (e) {}
      el = window.mcpElementFromPoint(m.cx - window.scrollX, m.cy - window.scrollY);
      if (el) return window.mcpPickActionable(el) || el;
    }
Behavior2/5

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

No annotations are provided, yet the description fails to disclose behavioral traits like scroll animation (smooth vs instant), coordinate system reference (viewport vs document), or whether this triggers scroll events. Carries minimal burden.

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?

Single sentence with no redundancy. While efficient, the extreme brevity contributes to gaps in behavioral transparency and sibling differentiation; however, the sentence itself earns its place.

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?

Adequate for a simple 2-parameter tool with no output schema, but significant gaps remain regarding behavioral specifics and differentiation from similar scroll operations. Minimum viable for function.

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%, documenting both x and y positions with defaults. The description implies these are coordinate parameters by mentioning 'position', but adds no semantic context about units (pixels) or coordinate space beyond what the schema provides.

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 action (scroll) and target (specific position on the page). However, it does not distinguish from siblings like 'safari_scroll' (likely relative) or 'safari_scroll_to_element', which is critical given the semantic similarity.

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 provided on when to use this coordinate-based scrolling versus alternatives like 'safari_scroll_to_element' or 'safari_scroll'. The agent must infer usage from parameter names alone.

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/achiya-automation/safari-mcp'

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