Skip to main content
Glama

Black SEO Analyzer

query_issues

Read-only

List individual issues from a crawl, filtered by severity, issue key, category or URL prefix, as bseoa.issue/v1 records with the affected URL, the localized message, a fix hint and a docs link. Returns at most 100 issues per call: when the response has a non-null next_offset there are more, so call again with offset set to that value. Narrow with min_severity or key from issues_summary rather than paging through everything.

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

Input Schema

NameRequiredDescriptionDefault
keyNoOnly return issues with this exact key, e.g. "metadata.missing_meta_description". Get keys from issues_summary.
limitNoHow many issues to return. Capped at 100 per call.
offsetNoZero-based index of the first issue to return. Pass the `next_offset` from the previous response to page through a large result set.
categoryNoOnly return issues in this category, e.g. "metadata", "links", "images".
session_idNoCrawl session id from list_crawls. Omit to use the most recent crawl.
url_prefixNoOnly return issues for URLs starting with this prefix, e.g. "https://example.com/blog/".
min_severityNoOnly return issues at this severity or above: "low", "medium", "high", or "critical".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds behavior the annotations do not: a hard cap of 100 issues per call, the next_offset handshake for detecting more results, and the fact that omitting session_id falls back to the most recent crawl is implied via the schema. No auth or error behavior, but the paging contract is the operationally important part and it is disclosed.

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?

Three sentences, each carrying distinct load: what is returned, how paging works, how to avoid paging. The return shape and the filter list are front-loaded before the pagination mechanics, so an agent skimming the first clause still gets the purpose.

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

Completeness5/5

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

There is no output schema, yet the description fully specifies the return payload (affected URL, localized message, fix hint, docs link) and the paging sentinel. For a read-only, well-documented 7-parameter query tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by tying offset to the response field next_offset and by framing key/min_severity as the preferred narrowing levers sourced from issues_summary. That explains the intended workflow, not just the parameter types.

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?

States a specific verb and resource ("List individual issues from a crawl") plus the filter dimensions (severity, key, category, URL prefix) and the exact record shape returned (bseoa.issue/v1 with URL, message, fix hint, docs link). This is far more precise than the sibling name issues_summary, so the agent can tell the two apart without opening a schema.

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

Usage Guidelines4/5

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

"Narrow with min_severity or key from issues_summary rather than paging through everything" gives an explicit routing preference and names the sibling to consult first, and the pagination instructions say exactly what to do on a non-null next_offset. It stops short of stating when this tool is the wrong choice versus page_report or compare_crawls, so it is clear guidance without full exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.