cdp_targetsScan localhost ports 9222-9229 to list live Chrome, Edge, Brave, and Electron CDP endpoints, so you can discover browser debugging targets for automation.
List live CDP endpoints on localhost (Chrome/Edge/Brave + Electron apps).
| Name | Required | Description | Default |
|---|---|---|---|
| ports | No | Ports to scan (default 9222-9229). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description usefully adds what gets scanned (localhost, the specific browser families plus Electron), but omits scan timing, timeouts, or the shape of a discovered target.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence with the verb, resource, host, and scanning scope; no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a zero-parameter read-only discovery tool, but with no output schema it leaves the return format unspecified and does not explain how discovered endpoints feed into cdp_launch/cdp_switch, which is the main reason an agent would call it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single 'ports' parameter, including its 9222-9229 default, so the schema does the heavy lifting. The description adds no port syntax or override guidance beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb+resource: 'List live CDP endpoints on localhost', with parenthetical scope for Chrome/Edge/Brave and Electron apps. It reads distinctly from sibling discovery tools like cdp_launched, though it never explicitly contrasts itself 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to reach for this versus cdp_launched, cdp_tabs, or cdp_launch, and no prerequisites or follow-up guidance. Usage is only implied by the tool name and the word 'live'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.