Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_click_element

Clicks a page element in Microsoft Edge using a CSS selector, enabling automated browser interaction and UI testing through the DevTools protocol.

Instructions

点击页面元素

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": {
      "selector": "<selector>"
    },
    "name": "edge_click_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS选择器

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether the click waits for the element, scrolls it into view, triggers navigation, fires JavaScript, requires an attached target via edge_connect, or what errors occur when the selector matches nothing.

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

Conciseness3/5

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

It is a single front-loaded fragment with no wasted words, but it is under-specified rather than concise; the length reflects missing information rather than efficient phrasing.

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?

For a mutation-style browser action with no annotations and no output schema, an agent needs to know the target context and post-click behavior. The description supplies neither, leaving the agent to infer everything from the sibling names and the single selector parameter.

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

Parameters3/5

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

Schema description coverage is 100% — the sole parameter 'selector' is documented as 'CSS选择器' — so the schema already does the work. The description adds nothing beyond implying an element is targeted, which earns the baseline 3.

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 phrase '点击页面元素' gives a clear verb (click) plus resource (page element), so an agent knows exactly what action is performed. However, it offers zero differentiation from siblings such as edge_get_element, edge_type_text, or edge_wait_for_selector, and gives no hint about which page/target/session the click applies to.

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?

There is no when-to-use guidance at all: nothing about when a click is appropriate versus alternatives like edge_evaluate or edge_type_text, no preconditions such as the element needing to exist or be visible, and no mention of any prerequisites.

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