Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_dom_query

Queries DOM nodes in a specified Edge DevTools session by CSS selector, returning matching elements for inspection or automation.

Instructions

查询DOM节点

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>",
      "sessionId": "<sessionId>"
    },
    "name": "edge_dom_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS选择器
sessionIdYesDevTools会话ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing. It does not confirm the operation is read-only, does not say whether nodes are live references or snapshots, and does not mention what happens if the selector matches nothing or matches multiple nodes. For a query tool with zero annotation coverage, 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.

Conciseness2/5

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

The description is a single four-character phrase with no structure and no front-loaded detail beyond the bare action. Brevity here reflects under-specification rather than discipline, since critical information (return shape, scope, alternatives) is simply absent. There is nothing extraneous, but there is barely anything at all.

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?

With no output schema and no annotations, the description must explain what a 'query' returns—especially whether the result is a node reference usable by edge_click_element or edge_type_text, which is essential for chaining calls. It also omits session lifecycle expectations tied to sessionId. Relative to the tool's role in the edge_* family, the definition is too thin to support correct invocation.

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%, so both parameters (selector as CSS selector, sessionId as DevTools session ID) are already documented in the schema. The description adds no meaning beyond that—no selector syntax hints, no note on whether sessionId must come from edge_connect. Baseline 3 is appropriate when the schema does the work.

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?

The four-character phrase '查询DOM节点' states a verb (query) and a resource (DOM node), so the basic action is identifiable. However, it gives no scope: it does not say whether it returns one node or many, whether it returns node handles/DOM markup/serialized data, or how it differs from sibling tools such as edge_get_element or edge_get_attributes. The purpose is recognizable but the phrase is vague about what it does.

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?

The description contains no guidance on when to use this tool rather than alternatives like edge_get_element, edge_get_attributes, or edge_wait_for_selector. There are no prerequisites, no exclusions, and no stated context for invocation beyond the bare action. An agent must infer all routing decisions from sibling names alone.

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