Skip to main content
Glama

Site audit

get_site_audit
Read-onlyIdempotent

Result of the latest finished crawl audit of the property's own site (HTML only, no JavaScript): audit date, pages crawled, the plan's per-audit page limit and whether the crawl was cut by it, two health scores (0–100) with the formula written out (page health: share of crawled pages with no error; traffic health: share of Search Console impressions of the last 28 days that land on pages with no error), pages counted per severity (error, warning, notice), issues sorted by impressions of the affected pages (code, severity, title, fix, pages, impressions, clicks), site-wide issues (robots.txt, sitemap, llms.txt, AI bots) and the health trend over the previous audits. Without a finished audit it states the state of the last one and points to request_site_audit. Use it for "how healthy is the site" or "what should I fix first"; get_audit_issue lists the pages of one issue. / Última auditoria concluída do site: nota por páginas e por tráfego com a fórmula, problemas por impressões afetadas, problemas do site inteiro e tendência.

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": {
      "site": "<site>"
    },
    "name": "get_site_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesProperty: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.
limitNoIssues listed (default 30), ordered by impressions of the affected pages.
languageNoLanguage of issue titles and fixes (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: the crawl is HTML-only with no JavaScript, results can be truncated by the plan's per-audit page limit (and says so in the output), and the no-finished-audit case degrades to a state report plus a pointer to request_site_audit. The explicit health-score formulas also prevent misreading the 0–100 numbers.

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 purpose, then the return contract, then usage — a sensible order. It is a dense near-run-on sentence, but the enumeration substitutes for a missing output schema, so most of the length earns its place; the mirrored Portuguese sentence is the only clearly duplicated content.

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 full return-value burden and does so: field-by-field contents, severity taxonomy, issue record shape, site-wide checks, and trend. Combined with the annotations and the fully documented three-parameter schema, nothing an agent needs to call or interpret this tool is missing.

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% and each parameter (site, limit, language) is fully documented in the schema, so the baseline is 3. The description mentions the ordering by impressions and the per-audit page limit, but both are already stated in the schema, so it adds little parameter-level meaning beyond structured fields.

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?

Opens with a specific verb+resource+scope: the latest finished crawl audit of the property's own site, HTML-only. It then enumerates exactly what is returned (audit date, pages crawled, health scores with formulas, severity counts, issue list, site-wide issues, trend), which lets an agent tell it apart from get_audit_issue and request_site_audit 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 Guidelines5/5

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

Gives explicit trigger questions ('how healthy is the site', 'what should I fix first') and names the two relevant alternatives with their distinct roles: get_audit_issue for the pages of one issue, request_site_audit when no finished audit exists. It also describes the fallback behavior when the precondition is unmet, which is unusually complete routing guidance.

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.