Skip to main content
Glama
Rainmen-xia

Chrome Debug MCP Server

by Rainmen-xia

scroll_down

Scrolls down a web page by one viewport height to view content below the current screen position during browser automation.

Instructions

向下滚动页面一个视口高度

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function scrollDown that executes the downward scrolling by calling doAction with scrollPage.
    async scrollDown(): Promise<BrowserActionResult> {
    	return this.doAction(async (page) => {
    		await this.scrollPage(page, "down");
    	});
    }
  • Tool schema definition in the listTools response, including name, description, and empty input schema.
    {
    	name: "scroll_down",
    	description: "向下滚动页面一个视口高度",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    },
  • src/index.ts:203-205 (registration)
    Registration and dispatch in the CallToolRequestSchema handler switch statement.
    case "scroll_down":
    	result = await this.browserSession.scrollDown();
    	break;
  • Helper function scrollPage that performs the actual scrolling logic using page.evaluate and window.scrollBy.
    private async scrollPage(page: Page, direction: "up" | "down"): Promise<void> {
    	const { height } = this.getViewport();
    	const scrollAmount = direction === "down" ? height : -height;
    
    	await page.evaluate((scrollHeight) => {
    		window.scrollBy({
    			top: scrollHeight,
    			behavior: "auto",
    		});
    	}, scrollAmount);
    
    	await delay(300);
    }
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 states the action but doesn't describe what happens if no page is loaded, whether scrolling is smooth or instant, if it respects page boundaries, or what visual/state changes occur. For a browser interaction tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence in Chinese that directly states the tool's function without any wasted words. It's appropriately sized for a simple action tool and front-loads the essential information.

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?

Given this is a browser interaction tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the tool returns (e.g., success status, new page position), error conditions, or dependencies on other tools like 'launch_browser' or 'navigate_to'. For a tool that modifies browser state, more context is needed.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the schema fully documents the empty parameter set. The description appropriately doesn't add parameter information beyond what's already covered, maintaining focus on the tool's purpose without redundancy.

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 down) and the target ('页面' - page) with specific scope ('一个视口高度' - one viewport height). It distinguishes from siblings like 'scroll_up' by direction, but doesn't fully differentiate from other navigation tools like 'navigate_to' beyond the scrolling action.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for scrolling down a page, but doesn't specify when to choose this over 'scroll_up' or other navigation methods, nor does it mention prerequisites like requiring an active browser session.

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/Rainmen-xia/chrome-debug-mcp'

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