Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_get_attributes

Retrieves the attributes of a specified DOM node using its node ID and DevTools session ID, enabling Edge browser DOM inspection and manipulation.

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": {
      "nodeId": "<nodeId>",
      "sessionId": "<sessionId>"
    },
    "name": "edge_get_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes节点ID
sessionIdYesDevTools会话ID

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?

No annotations are supplied, so the description carries the full disclosure burden and provides almost none. It does not say whether the call is read-only, what happens if the sessionId is stale or the nodeId is invalid, or what shape of attribute data is returned.

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 six-character phrase is certainly front-loaded and free of padding, but it is terse to the point of under-specification rather than efficient communication. Brevity here costs information rather than saving it.

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 annotations and no output schema, the description is the only source of behavioral information, and it says nothing about return values, error conditions, or session requirements. For a two-parameter DOM inspection tool that is a meaningful gap.

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%, with both nodeId (节点ID) and sessionId (DevTools会话ID) documented inline, so the schema already does the parameter work. The description adds no further meaning about expected ID formats or how a node is located, which is acceptable at full coverage but leaves nothing extra.

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 (获取) and a resource (元素属性), so the basic action is identifiable. However, it gives no hint of how this differs from sibling tools such as edge_get_element or edge_dom_query, leaving the agent to guess whether it returns attributes, property values, or a DOM subtree.

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 preconditions (e.g. an active DevTools session must exist), no statement of when to prefer this over edge_get_element or edge_evaluate, and no exclusions. The agent must infer usage purely from the tool name.

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