Skip to main content
Glama

get_issues

Lists browser-diagnosed tab issues hidden by the console, including cookie blocks, CORS/CSP errors, mixed content, deprecated features, and Chrome DevTools Issues codes with affected elements.

Instructions

Lists the problems the browser diagnosed in the tab that the console hides or words vaguely: blocked or warned cookies and why, CORS and Content-Security-Policy blocks, mixed content, deprecated features, and on Chrome every code of its DevTools Issues panel (form fields without id, name or label, LazyLoadImageIssue...). One line each, oldest first: [code] title: summary @ url [xN] (a title for the common Chrome codes; N distinct reports, one per element or request), then on Chrome its elements (selector [ref=eN], refs as snapshot's, at most 10). For console messages use get_console_logs. Firefox has no Issues panel: its security and deprecation console messages are read as issues (cookies, CSP, mixed content, CORS, DeprecationIssue; needs its debugger port).

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

Input Schema

NameRequiredDescriptionDefault
codeNoOnly the issues whose code contains this (case-insensitive), e.g. 'Cookie'.
clearNoRemove the returned issues. Default: false.
tab_idNoDefault: the active tab.
instance_idNoDefault: 'default'.
include_detailsNoThe browser's details of each issue, as JSON. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the exact line format, ordering (oldest first), the [xN] aggregation semantics, the 10-element cap, and the platform-specific behavior including the debugger-port requirement. The notable gap is that it never mentions that the clear flag removes issues, a mutating side effect the agent only learns from the schema.

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?

It is front-loaded with the purpose and packs a lot of information into three long sentences with no filler, but the middle sentence is a dense run of format notation that takes effort to parse. Nothing is truly redundant, though the output-format explanation could be separated for readability.

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?

There is no output schema, so the description correctly takes on explaining return values in detail, and it covers the Chrome/Firefox split and element refs. The main missing piece for a tool of this complexity is the destructive nature of clear, which is behavioral information an agent needs before invoking.

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%, so all five parameters are already documented in structured fields, and the baseline is 3. The description adds context around the returned line format and the N-per-element aggregation but does not explain code matching, tab_id/instance_id defaults, or clear semantics beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Lists) and a precisely scoped resource: problems the browser diagnosed in the tab that the console hides or words vaguely, then enumerates the concrete categories (cookies, CORS/CSP, mixed content, deprecation, DevTools Issues codes). It also draws its own boundary against get_console_logs, so an agent can separate it from its closest sibling without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule ('For console messages use get_console_logs') and a platform caveat that changes expectations (Firefox has no Issues panel; its security/deprecation console messages are surfaced as issues and require the debugger port). That is enough for an agent to decide when this tool applies and when the alternative does.

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