Skip to main content
Glama

scroll_down

Scrolls down web pages by a specified pixel amount or one full page to view content below the current viewport.

Instructions

Scroll down the page by a pixel amount - if no pixels are specified, scrolls down one page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pixelsNoThe number of pixels to scroll down. If not specified, scrolls down one page.

Implementation Reference

  • The main handler function that executes the scroll_down tool. It scrolls the page down by the specified number of pixels using window.scrollBy, or presses PageDown if no pixels are provided.
    async function handleScrollDown(
      page: Page,
      args: any
    ): Promise<CallToolResult> {
      const { pixels } = args;
      if (pixels !== undefined) {
        await page.evaluate((scrollAmount) => {
          window.scrollBy(0, scrollAmount);
        }, pixels);
      } else {
        await page.keyboard.press("PageDown");
      }
    
      return {
        isError: false,
        content: [
          { type: "text", text: `Scrolled down by ${pixels ?? "one page"}` },
        ],
      };
    }
  • The tool definition including name, description, and input schema for the scroll_down tool. Pixels is an optional integer parameter.
    {
      name: "scroll_down",
      description:
        "Scroll down the page by a pixel amount - if no pixels are specified, scrolls down one page",
      inputSchema: {
        type: "object",
        properties: {
          pixels: {
            type: "integer",
            description:
              "The number of pixels to scroll down. If not specified, scrolls down one page.",
          },
        },
        required: [],
      },
    },
  • src/index.ts:928-929 (registration)
    The switch case in the main tool dispatcher (handleToolCall) that routes scroll_down calls to the handleScrollDown function.
    case "scroll_down":
      result = await handleScrollDown(page, args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the default behavior (scrolls down one page if no pixels specified) but doesn't address important behavioral aspects like what constitutes 'one page' (viewport height?), whether scrolling is smooth or instant, error handling for invalid pixel values, or visual feedback. This leaves significant gaps for a mutation 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 perfectly concise - a single sentence that communicates both the primary action and the default behavior. Every word earns its place with zero redundancy, and the information is front-loaded with the core functionality stated first.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'success' looks like, whether there's visual feedback, what happens at page boundaries, or error conditions. The agent would need to guess about important behavioral aspects of this scrolling operation.

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 already fully documents the single parameter. The description adds minimal value beyond the schema by restating the default behavior, but doesn't provide additional context about pixel ranges, scrolling behavior, or practical usage examples. This meets the baseline for high schema coverage.

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 the specific action ('scroll down the page') and resource ('page'), distinguishing it from sibling tools like 'scroll_up' by specifying direction. It provides a complete verb+resource+scope statement that leaves no ambiguity about what the tool does.

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?

The description provides clear context about when to use the tool (to scroll down a page) and includes the default behavior when no pixels are specified. However, it doesn't explicitly mention when NOT to use it or name alternatives among siblings like 'scroll_up' for upward scrolling, which prevents a perfect score.

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/steel-dev/steel-mcp-server'

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