Skip to main content
Glama

Outil.io

Get SEO audit

get_seo_audit
Read-only

Résultat d’un audit SEO : score global /100, score par catégorie, problèmes groupés par règle (gravité, conseil, URLs concernées, outil Outil qui corrige : outilFix), pages explorées (title, description, H1, mots, poids, temps de réponse), PageSpeed (scores, LCP/INP/CLS terrain et labo, opportunités chiffrées), Search Console. Filtrer avec category, severity ou page pour réduire la réponse. Sans id : liste des 30 derniers audits. En cours : progression.

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_seo_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
pageNo
categoryNo
severityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: a detailed inventory of returned sections, the fact that filters reduce response size, that no id yields the last 30 audits, and that running audits expose progress instead of a final result. Rate limits or error conditions for a stale id are not mentioned.

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?

The description is front-loaded with what is returned, then filtering, then the no-id fallback and the in-progress case, in a compact block with no filler sentences. The long comma-separated inventory of returned sections is dense but every item earns its place given there is no output schema.

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 properly enumerates the returned structure, which is the main gap for a read tool of this complexity. Filtering, list-mode and in-progress behavior are all covered. Remaining gaps are id semantics and how filters interact when combined, which leave an agent slightly under-briefed.

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 description coverage is 0%, so the description must carry parameter meaning. It does identify category, severity and page as response-reducing filters and explains that omitting id switches to list mode. It never explains what id identifies, its format, or what happens when page scope conflicts with an aggregate; enum values come from the schema.

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 gives a concrete verb-and-resource picture: it returns the result of an SEO audit (global score, per-category score, issues grouped by rule, crawled pages, PageSpeed, Search Console) and, when no id is supplied, lists the 30 most recent audits. That is specific enough for an agent to know what it fetches. It never distinguishes itself from an audit-triggering sibling such as audit_seo or audit_site_content, so the differentiation clause is missing.

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

Usage Guidelines3/5

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

It implies two modes (with id = one audit, without id = recent audit list) and recommends filtering via category, severity or page to shrink the response, and notes in-progress audits return progression. It does not state when to prefer this tool over audit_seo or fix_seo_issues, nor any exclusions or prerequisites. Usage is inferable but not routed.

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.