Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_get_element

Retrieves information about a page element using a CSS selector, helping inspect DOM content during Edge browser automation and debugging.

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_get_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS选择器

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 supplied, the description carries the full disclosure burden and delivers almost nothing: it doesn't state whether a missing selector errors or returns null, whether the call waits for the element, or what the response shape looks like. It is not misleading, but for an unannotated tool this is a substantial gap.

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?

A single short phrase with no filler or wasted words, so it is certainly concise and front-loaded. But the brevity comes at the cost of under-specification rather than efficient density — nothing is packed in.

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?

There is no output schema, so the description is the only place the agent could learn what element information is returned — and it doesn't say. For a read tool invoked with a bare selector, the critical details (return shape, missing-element behavior) are absent.

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?

One parameter, the selector, already has a schema description covering 100% of the input schema ("CSS选择器"). The description adds no further meaning about selector syntax, scoping, or matching behavior, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"获取页面元素信息" states a verb (get) and a resource (page element), so the general intent is clear. However, "信息" (information) is undefined — it doesn't say whether this returns text, bounding box, visibility, or a serialized node — and it doesn't distinguish itself from sibling edge_get_attributes, which also retrieves element data.

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: no indication of when this is preferable to edge_get_attributes or edge_dom_query, no prerequisites (element must exist / be attached), and no exclusions. The agent must infer selection purely from sibling names.

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