Skip to main content
Glama

List Electron Targets

list_electron_targets
Idempotent

Retrieves every Electron file:// page target from a loopback CDP endpoint and returns canonicalized local path metadata for inspection.

Instructions

List every Electron file:// page target from a selected loopback CDP endpoint. Local file paths are canonicalized after symlink resolution. Selecting an endpoint exposes every eligible target and its local path metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cdp_endpoint": "http://127.0.0.1:9223"
    },
    "name": "list_electron_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdp_endpointYesLiteral loopback Chrome DevTools Protocol endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The description discloses real behavior beyond the annotations: symlink resolution with canonicalized local paths, and that the result includes local path metadata per target. However, it does not explain why readOnlyHint is false for a 'list' operation (e.g., that it attaches to or opens a CDP session), leaving a notable behavioral ambiguity unaddressed.

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?

Three sentences with the purpose front-loaded, but the final sentence largely restates the first (every eligible target plus local path metadata) and the word 'selected'/'Selecting' is vague. It could be tightened without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries some of the return-value burden by mentioning local path metadata, and it covers the symlink/canonicalization nuance. It does not define what makes a target 'eligible' or describe the shape or size of the returned list, leaving a gap for a list-style tool.

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% and the single cdp_endpoint parameter is documented as a literal loopback CDP endpoint. The description repeats the 'loopback CDP endpoint' constraint but adds no format, port, or validation detail beyond the schema, so baseline 3 applies.

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 description states a specific verb and resource: list Electron file:// page targets from a loopback CDP endpoint. The 'Electron file://' qualifier reasonably distinguishes it from generic browser or JS-runtime listing tools, though it never names those siblings explicitly.

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 explicit when-to-use guidance and no comparison against the closely overlapping siblings list_browser_targets and list_javascript_runtime_targets. The only implied condition is that the caller already has a selected loopback CDP endpoint, which a reader must infer.

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

Deploy Server

Other Tools