Skip to main content
Glama
Sign In
Selenium MCP Server

Selenium MCP Server

by zulfiqar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

execute_script

Execute JavaScript code in the browser via Selenium WebDriver to manipulate web pages, extract data, or trigger actions that are not possible with standard interactions.

Instructions

Execute JavaScript in the browser

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": {
      "script": "<script>"
    },
    "name": "execute_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptYesJavaScript code to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Execute JavaScript' without mentioning return values, side effects, security implications, or whether execution is synchronous or asynchronous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While only one sentence, it is under-specified and lacks essential details. Conciseness should not come at the cost of completeness; the description is too minimal to be helpful.

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 simplicity of the tool (one parameter, no output schema), the description should still cover basic aspects like return value, execution scope, and potential consequences. It fails to do so.

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

Parameters2/5

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

The description adds no information beyond the input schema's own description of the 'script' parameter. The schema already states 'JavaScript code to execute', so the description is redundant.

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 (Execute) and the target (JavaScript in the browser), which is a distinct capability from sibling tools that focus on UI interactions. However, it does not elaborate on the scope or context of execution.

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 guidance is given on when or why to use this tool versus others, nor are any prerequisites or limitations mentioned. The agent receives no context for appropriate usage.

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