browser_mouse_move
Move the mouse cursor to exact x/y coordinates on the web page. Use to simulate hovering and mouse-based interactions in browser automation.
Instructions
移动鼠标
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | ||
| y | Yes | ||
| steps | No |
Move the mouse cursor to exact x/y coordinates on the web page. Use to simulate hovering and mouse-based interactions in browser automation.
移动鼠标
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | ||
| y | Yes | ||
| steps | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It only states 'move mouse' with no details about absolute/relative movement, whether hover events are triggered, or how the 'steps' parameter affects behavior. The description is not misleading but omits critical behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but brevity here results from under-specification rather than economy. It lacks any structure and leaves out essential details, making it less useful than a concise but complete description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 3 parameters, no annotations, and no output schema, the description is inadequate. It should at least mention coordinates and the role of 'steps' to be minimally complete. As provided, it only conveys the basic action.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage and the tool description does not explain any of the parameters. 'Move mouse' does not clarify that x and y are coordinates or how 'steps' influences the action. The description adds no value beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '移动鼠标' clearly states the action: move the mouse. It distinguishes from mouse-specific siblings like click, down, up, and wheel, though it does not mention coordinates explicitly. The verb+resource is specific enough for basic understanding.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not indicate when to use this tool versus other mouse-related tools, nor does it mention any context or prerequisites. There is no support for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/91fapiao-cn/playwright-browser-skill'
If you have feedback or need assistance with the MCP directory API, please join our Discord server