Skip to main content
Glama

List Browser Targets

list_browser_targets
Idempotent

List page targets exposed by a loopback Chrome DevTools Protocol endpoint and optionally filter by exact origin to inspect available browser pages.

Instructions

List page targets exposed by the selected loopback Chrome DevTools Protocol endpoint. Optionally filter by exact origin. URLs preserve query values and fragments; only URL userinfo credentials are removed.

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:9222"
    },
    "name": "list_browser_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdp_endpointYesLiteral loopback Chrome DevTools Protocol endpoint.
allowed_originsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful data-handling behavior: URLs keep query values and fragments, and only userinfo credentials are stripped — a privacy-relevant fact an agent could not derive from the schema. It also bounds the tool to loopback endpoints. The notable gap is that readOnlyHint=false is never reconciled with an operation described purely as 'List', and no return shape is given.

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?

Two tight sentences with the core purpose front-loaded and no filler; the credential-stripping note is appended where it belongs. It could have been slightly more economical by folding the origin filter note into the parameter discussion, but nothing is wasted.

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?

For a simple two-parameter read tool this is largely sufficient, and the endpoint scope plus origin filter are covered. With no output schema, the description would ideally say what a 'target' record contains (id, URL, title, type) or whether results are paginated, and the readOnlyHint=false signal stays unexplained.

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 50%: cdp_endpoint is documented in the schema, while allowed_origins has no description at all. The description partially compensates by stating the origin filter is optional and matches exactly, but it does not clarify whether the list acts as an allowlist that restricts results or merely narrows them, nor what 'origin' means relative to the page URL.

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 gives a specific verb and resource — 'List page targets exposed by the selected loopback Chrome DevTools Protocol endpoint' — which is far more precise than the name alone. It scopes the tool to page targets on a loopback CDP endpoint, implicitly separating it from device/runtime-oriented siblings, but never names an alternative tool to confirm the distinction.

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?

'Optionally filter by exact origin' communicates the one usage decision available, and 'the selected loopback Chrome DevTools Protocol endpoint' implies prerequisite context. However, there is no explicit statement of when to choose this tool over list_electron_targets, list_javascript_runtime_targets, or the capture/scenario siblings, so the routing is left to inference.

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