Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

list_targets

Read-onlyIdempotent

Lists Chrome DevTools Protocol targets with role classification (page, worker, browser, other) to help you identify debuggable processes. Optionally filter by process ID or list targets across all running apps.

Instructions

List Chrome DevTools Protocol targets with role classification (page/worker/browser/other)

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": "list_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
processIdNoOptional process id; omit to list targets for all running apps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds that returned targets are bucketed into page/worker/browser/other, which is genuine output context. It does not mention that omitting the filter spans all running apps, nor anything about result volume or ordering.

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?

One compact phrase with the enumeration of role categories front-loaded and no filler. It borders on under-specification rather than verbosity, which does not hurt its structure.

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

Completeness4/5

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

This is a simple read-only, single-optional-parameter list tool with no output schema, and the description conveys the resource plus the shape of the classification. Only minor gaps remain, such as the all-apps default scope, which the schema itself covers.

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 coverage is 100% and the single parameter processId is fully documented in the schema, including the omit-to-list-all behavior. The description adds nothing about the parameter, which is acceptable at this coverage level.

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?

States a specific verb (List) and resource (Chrome DevTools Protocol targets) and adds that results are classified by role (page/worker/browser/other). It is distinguishable from list_apps by naming CDP targets rather than applications, though it never explicitly contrasts with that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the tool name and verb; there is no statement of when to prefer this over list_apps or list-oriented siblings, and no prerequisites or exclusions are given. An agent can infer intent, but nothing routes it deliberately.

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