Skip to main content
Glama
zillow
by zillow

scroll

Scrolls within mobile app containers to navigate content or locate specific elements by text or selector during automated testing.

Instructions

Scroll in a direction on a scrollable container, optionally to find an element (supports text and selectors)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containerElementIdYesElement ID to scroll until visible
directionYesScroll direction
lookForNoWhat we're searching for while scrolling
speedNoScroll speed
platformYesPlatform of the device

Implementation Reference

  • The scrollHandler function implements the core logic for scrolling within a specified container element. It supports simple directional scrolling or scrolling until a target element (by ID or text) becomes visible, using repeated observe-swipe cycles with a timeout.
    // Scroll handler
    const scrollHandler = async (device: BootedDevice, args: ScrollArgs, progress?: ProgressCallback) => {
      // Element-specific scrolling
      const observeScreen = new ObserveScreen(device);
      const swipe = new SwipeOnElement(device);
      const observeResult = await observeScreen.execute();
    
      if (!observeResult.viewHierarchy) {
        throw new ActionableError("Could not get view hierarchy for element scrolling");
      }
    
      // Find the element by resource ID
      const element = elementUtils.findElementByResourceId(
        observeResult.viewHierarchy,
        args.containerElementId,
        args.containerElementId,
        true // partial match
      );
    
      if (!element) {
        throw new ActionableError(`Container element not found with ID: ${args.containerElementId}`);
      }
    
      const containerElement = element;
    
      if (!args.lookFor) {
        const duration = elementUtils.getSwipeDurationFromSpeed(args.speed);
        const result = await swipe.execute(
          containerElement,
          elementUtils.getSwipeDirectionForScroll(args.direction), {
            duration: duration,
            easing: "accelerateDecelerate",
            fingers: 1,
            randomize: false,
            lift: true,
            pressure: 1
          },
          progress
        );
    
        return createJSONToolResponse({
          message: `Scrolled ${args.direction} within element ${args.containerElementId}`,
          observation: result.observation
        });
    
      } else if (!args.lookFor.text && !args.lookFor.elementId) {
        throw new ActionableError("Either text or element id must be specified to look for something in a scrollable list.");
      } else {
        let lastObservation = await observeScreen.execute();
        if (!lastObservation.viewHierarchy || !lastObservation.screenSize) {
          throw new Error("Failed to get initial observation for scrolling until visible.");
        }
    
        const direction = args.direction;
        const maxTime = 120000; // args.lookFor.maxTime ?? 120000;
        const startTime = Date.now();
        let foundElement = null;
    
        while (Date.now() - startTime < maxTime) {
          // Re-observe the screen to get current state
          lastObservation = await observeScreen.execute();
          if (!lastObservation.viewHierarchy) {
            throw new Error("Lost observation during scroll until visible.");
          }
    
          // Check if target element is now visible
          if (args.lookFor.text) {
            foundElement = elementUtils.findElementByText(
              lastObservation.viewHierarchy,
              args.lookFor.text,
              args.containerElementId, // Search within the specific container
              true, // fuzzy match
              false // case-sensitive
            );
          } else if (args.lookFor.elementId) {
            foundElement = elementUtils.findElementByResourceId(
              lastObservation.viewHierarchy,
              args.lookFor.elementId,
              args.containerElementId, // Search within the specific container
              true // partial match
            );
          }
    
          if (foundElement) {
            logger.info(`Found element after scrolling for ${Date.now() - startTime}ms.`);
            break;
          }
    
          // Use the specific container element to swipe, not any scrollable element
          const result = await swipe.execute(
            containerElement,
            elementUtils.getSwipeDirectionForScroll(direction),
            { duration: 600 },
            progress
          );
    
          // Update observation from swipe result
          if (result.observation && result.observation.viewHierarchy) {
            lastObservation = result.observation;
          } else {
            throw new Error("Lost observation after swipe during scroll until visible.");
          }
        }
    
        if (!foundElement) {
          const target = args.lookFor.text ? `text "${args.lookFor.text}"` : `element with id "${args.lookFor.elementId}"`;
          throw new ActionableError(`${target} not found after scrolling for ${maxTime}ms.`);
        }
    
        const target = args.lookFor.text ? `text "${args.lookFor.text}"` : `element with id "${args.lookFor.elementId}"`;
        return createJSONToolResponse({
          message: `Scrolled until ${target} became visible`,
          found: !!foundElement,
          observation: lastObservation
        });
      }
    };
  • Zod schema defining the input parameters for the scroll tool, including container element, direction, optional lookFor criteria, speed, and platform.
    export const scrollSchema = z.object({
      containerElementId: z.string().describe("Element ID to scroll until visible"),
      direction: z.enum(["up", "down", "left", "right"]).describe("Scroll direction"),
      lookFor: z.object({
        elementId: z.string().optional().describe("ID of the element to look for while scrolling"),
        text: z.string().optional().describe("Optional text to look for while scrolling"),
        maxTime: z.number().optional().describe("Maximum amount of time to spend scrolling, (default 10 seconds)")
      }).optional().describe("What we're searching for while scrolling"),
      speed: z.enum(["slow", "normal", "fast"]).optional().describe("Scroll speed"),
      platform: z.enum(["android", "ios"]).describe("Platform of the device")
    });
  • Registration of the 'scroll' tool with ToolRegistry, linking the name, description, schema, and handler function.
    "scroll",
    "Scroll in a direction on a scrollable container, optionally to find an element (supports text and selectors)",
    scrollSchema,
    scrollHandler,
    true // Supports progress notifications
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions scrolling 'to find an element' but doesn't describe what happens when found/not found, error conditions, performance characteristics, or side effects. The agent must infer behavior from the tool name and parameters alone.

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?

The description is a single, efficient sentence that communicates the core functionality. However, it could be more front-loaded by explicitly stating the primary purpose before the optional capabilities.

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 tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how errors are handled, or the interaction between scrolling and element-finding. The agent lacks critical context for proper invocation.

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%, so the schema fully documents all 5 parameters. The description adds marginal value by mentioning 'supports text and selectors' which relates to the 'lookFor' parameter, but doesn't provide additional semantic context beyond what's already in the schema descriptions.

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 ('scrollable container'), and mentions the optional element-finding capability. It distinguishes from siblings like 'swipe' or 'swipeOnElement' by focusing on scrolling within containers, but doesn't explicitly contrast with similar tools.

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 provides no guidance on when to use this tool versus alternatives like 'swipe' or 'swipeOnElement', nor does it mention prerequisites or contextual constraints. It simply states what the tool does without usage context.

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/zillow/auto-mobile'

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