Skip to main content
Glama
Sign In
Debug Web MCP

Debug Web MCP

by AYUSHchouhaan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_list_targets

Discover and list localhost development tabs from a loopback Chrome CDP endpoint to identify debuggable pages before attaching.

Instructions

List localhost development tabs exposed by a loopback Chrome CDP endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cdp_endpoint": "<cdp_endpoint>"
    },
    "name": "browser_list_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdp_endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a read-only listing and scopes the endpoint to loopback, but says nothing about permissions, error behavior, pagination, or return format. This is a significant gap for a tool with zero annotation coverage.

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

Conciseness5/5

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

A single sentence that is front-loaded and free of filler. Every clause contributes to identifying the action, target, and endpoint constraint.

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?

Given the tool's low complexity and single parameter, the description is adequate for identifying purpose, but with no output schema it does not describe what a target contains. The missing return information leaves an agent guessing about the result shape.

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 0%, so the description must compensate. It names the parameter's semantic domain ('loopback Chrome CDP endpoint'), which adds meaning beyond a bare URI string, but it does not explain expected format, ports, or examples.

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 (List) and resource (localhost development tabs) and clarifies the endpoint type (loopback Chrome CDP). It is immediately distinguishable from siblings like browser_list_network_requests or browser_open_session, but it does not explicitly contrast itself with those alternatives.

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 guidance on when to use this tool instead of a sibling, nor any mention of prerequisites or conditions. The purpose is implied by the description, but an agent receives no explicit routing information.

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