Skip to main content
Glama

Black SEO Analyzer

issues_summary

Read-only

Summarize a crawl: total issue count, counts by severity and by category, and every distinct issue key with how many pages it affects plus up to five example URLs. Always call this before query_issues - it is small, it tells you which keys are worth drilling into, and it is what you should base a prioritized fix plan on. Omit session_id to summarize the account's most recent crawl.

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

Input Schema

NameRequiredDescriptionDefault
session_idNoCrawl session id from list_crawls. Omit to use the most recent crawl in the database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 safety is covered structurally. The description adds genuine value beyond that by disclosing the shape of the returned data and the fallback behavior when session_id is omitted, plus a size hint ('it is small') that informs sequencing. It stops short of stating pagination or limits on the counts, which keeps it below a 5.

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?

Front-loaded with the payload description, then the usage rationale, then the default argument behavior; each sentence carries a distinct job and nothing is buried. Minor redundancy between the description's session_id note and the schema's identical note, and 'it is small' is conversational rather than precise.

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, so the description carries the burden of describing return values and does so concretely: totals, severity and category counts, per-key affected page counts, and capped example URLs. Combined with the ordering guidance relative to query_issues, an agent has everything needed to call it correctly and interpret the result.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents the omit-to-use-latest default and where the id comes from. The description restates the same default behavior rather than adding new semantics such as validity rules for stale session ids. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (summarize) and resource (a crawl) and enumerates the exact payload: total issue count, severity and category breakdowns, and every distinct issue key with affected page counts plus up to five example URLs. It explicitly positions itself against the sibling query_issues, so an agent can distinguish the two 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?

Gives an explicit ordering rule ('Always call this before query_issues'), a rationale for that rule (it is small and tells you which keys are worth drilling into), and a stated purpose for the output (base a prioritized fix plan on it). It also covers the no-argument case: omit session_id to summarize the most recent crawl.

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.