Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_get_targets

Retrieves all available DevTools targets so you can locate the Edge page, frame, or worker you need to inspect or automate.

Instructions

获取所有可用的DevTools目标

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edge_get_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about prerequisites (e.g., whether edge_connect or edge_enable_devtools must run first), whether the call is read-only, or what happens when no targets exist. Only the word '可用' hints at filtering to available targets.

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

Conciseness4/5

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

A single short sentence with no filler, which is appropriately front-loaded. Its brevity borders on under-specification rather than verbosity, but nothing needs trimming.

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 zero-param, no-annotation, no-output-schema tool in a browser-automation suite, the description leaves out the two things an agent most needs: connection prerequisites and what a returned 'target' contains. The definition is not complete enough to invoke with confidence without trial and error.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. No misleading parameter hints are given.

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 description names a specific verb and resource ('获取所有可用的DevTools目标' — get all available DevTools targets), which is clearer than a bare title. However, 'targets' is undefined jargon: it could mean pages, frames, or workers, and nothing distinguishes it from siblings like edge_get_page_content or edge_get_element that also retrieve state.

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 on when to call this instead of edge_connect, edge_enable_devtools, or edge_get_page_content. The agent must guess whether a connection must exist first and how this differs from the other retrieval tools.

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