Skip to main content
Glama
Rainmen-xia

Chrome Debug MCP Server

by Rainmen-xia

scroll_up

Scrolls a webpage up by one viewport height in Chrome during debugging sessions, enabling automated navigation without manual interaction.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the scroll_up tool. It uses doAction to execute the scrollPage helper with 'up' direction on the current page.
    async scrollUp(): Promise<BrowserActionResult> {
    	return this.doAction(async (page) => {
    		await this.scrollPage(page, "up");
    	});
    }
  • Tool schema definition in the list of tools returned by ListToolsRequestSchema handler, specifying name, description, and empty input schema (no parameters required).
    {
    	name: "scroll_up",
    	description: "向上滚动页面一个视口高度",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    },
  • src/index.ts:207-209 (registration)
    Dispatch/registration in the CallToolRequestSchema switch statement, invoking the browserSession.scrollUp() handler.
    case "scroll_up":
    	result = await this.browserSession.scrollUp();
    	break;
  • Supporting helper function that performs the actual page scrolling by one viewport height in the specified direction, used by both scrollUp and scrollDown.
    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?

No annotations are provided, so the description carries the full burden. It states the action ('scroll up one viewport height') but lacks behavioral details such as whether it requires a loaded page, handles errors (e.g., if at the top), or interacts with page elements. This is a significant gap for a tool with zero annotation coverage.

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 waste. It is appropriately sized and front-loaded, making it easy to understand quickly.

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 the tool has no annotations, no output schema, and 0 parameters, the description is minimal. It explains the basic action but lacks context on prerequisites, error handling, or integration with sibling tools (e.g., 'launch_browser' must be used first). For a browser interaction tool, this is incomplete and could lead to misuse.

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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description adds no parameter information, which is acceptable here as there are no parameters to explain. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 ('向上滚动' meaning 'scroll up') and the resource ('页面' meaning 'page'), specifying it scrolls by one viewport height. It distinguishes from sibling 'scroll_down' by direction, though not explicitly. However, it doesn't fully differentiate from other navigation tools like 'navigate_to' beyond the scroll 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 up a page, but it doesn't mention prerequisites (e.g., requires an active browser session), exclusions, or comparisons to other tools like 'scroll_down' or 'navigate_to' for different navigation needs.

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