Skip to main content
Glama

Outil.io

Get site SEO

get_site_seo
Read-only

État SEO des pages du site Outil courant, sans exploration réseau : title effectif, description, H1 (après promotion automatique du premier titre), images sans alt (blockIds), image de partage, langue, manques (gaps) et suggestions de titre/description calculées depuis le contenu. À lire avant fix_seo_issues.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, openWorldHint=false, destructiveHint=false. The description adds meaningful context beyond that: 'sans exploration réseau' (no network exploration) and the automatic promotion of the first heading to H1, which affects how results should be interpreted.

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 purpose, then a dense but purposeful enumeration of returned fields and the ordering hint. It is a single long sentence, slightly heavy, but nearly every clause carries information.

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 must convey return values, and it does so thoroughly by listing the SEO fields, gaps, and computed suggestions. Combined with the annotations, an agent has enough to call it correctly and interpret results.

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?

Zero parameters, so the baseline is 4. The description correctly adds no parameter detail because none exist, and instead spends its words on return content.

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+resource ('État SEO des pages du site') and enumerates exactly what it returns (title, description, H1, images without alt, share image, language, gaps, suggestions). It also distinguishes itself from the sibling fix_seo_issues by framing itself as the read step before fixing.

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?

Explicitly says 'À lire avant fix_seo_issues', giving clear sequencing guidance relative to the alternative. It does not state when-not-to-use, but the ordering instruction is concrete and actionable.

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.