Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_site_audit_summary

Summarize a site crawl’s technical health, including health score change, pages crawled, issue severity/category breakdowns, and category scores.

Instructions

Technical-health summary of the latest crawl: health_score (current plus prev and delta), pages_crawled, crawl_date, issues_by_severity (critical / warning / notice, each with issue_types and pages_affected vs the previous crawl), issues_by_category (OnPage, Links, International, Robots, Social) and per-area category_scores. Defaults to the 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": "get_site_audit_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full disclosure burden. It does well on output semantics by naming every returned field and noting the previous-crawl comparison dimension, but it never states that this is a read-only, non-destructive operation, nor anything about permissions, freshness guarantees, or what happens when no crawl exists.

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?

One dense but front-loaded sentence: the purpose leads, and the field enumeration follows in a readable grouped order (score, pages, date, severity, category, area scores). Every clause names a real returned field, so nothing is filler, though the nested parenthetical structure is slightly hard to parse at a glance.

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?

With no output schema, the description must carry the return-value burden and it largely does, naming all major fields and the previous-crawl comparison. What is missing is only the surrounding decision context: no read-only reassurance and no routing guidance to the many overlapping site-audit siblings.

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?

The tool takes zero parameters (schema is an empty object), which sets a baseline of 4. The sentence 'Defaults to the most recent crawl' adds useful meaning about which crawl is implicitly selected, though it also hints at an optional crawl selector that the schema does not actually expose.

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 opens with a specific verb-and-resource framing ('Technical-health summary of the latest crawl') and then enumerates exactly what the summary contains (health_score with prev/delta, pages_crawled, crawl_date, issues_by_severity, issues_by_category, per-area category_scores). An agent knows precisely what it gets back. It does not, however, distinguish itself from siblings like compare_site_audit_crawls or get_site_audit_page, so it stops short of a 5.

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?

The only usage-ish statement is 'Defaults to the most recent crawl,' which is a behavior note rather than when-to-use guidance. There is no guidance on when to pick this over compare_site_audit_crawls (historical comparison) or list_site_audit_issues (detailed issue lists), both of which overlap with the data this tool summarizes.

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