Skip to main content
Glama
Sign In
Ruishu MCP

Ruishu MCP

by markx520
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Execute Page Action

execute_page_action
Destructive

Executes custom JavaScript in a live browser page to simulate clicks, scrolling, or input, triggering the requests required for page interactions and structured data retrieval.

Instructions

Auxiliary action: allows executing specified JS in the page (simulate click/scroll/input, etc.) to trigger requests.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "js_script": "<js_script>"
    },
    "name": "execute_page_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
js_scriptYesJavaScript code to execute in the page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already signal destructive potential and non-read-only behavior, and the description adds context that it simulates user actions to trigger requests. The description does not contradict annotations, but it does not go beyond them to explain risks or side effects of executing arbitrary JS.

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?

One sentence with clear structure, front-loaded with the key verb, and includes examples without redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with annotations and no output schema, the description covers the what, the examples, and the purpose. It could mention return values or error behavior, but that is not required given the absence of an output schema.

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 schema describes js_script as 'JavaScript code to execute in the page', and the description enriches this with examples like simulate click/scroll/input, giving the agent concrete ideas of valid scripts. Since schema coverage is 100%, the baseline is met, and the additional examples justify a higher score.

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 uses a specific verb ('executes') and identifies the resource ('JS in the page'), with concrete examples (click/scroll/input) and the intent to trigger requests. This clearly distinguishes it from sibling tools like init_ruishu_hook and get_intercepted_traffic.

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?

It explicitly frames the tool as an 'Auxiliary action' for triggering requests, which gives clear context on when to use it. However, it does not name alternatives or specify when not to use it, so it stops short of full exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools