Skip to main content
Glama

Outil.io

Fix SEO issues

fix_seo_issues
Idempotent

CORRIGER LE SEO des pages du site Outil en un appel : seoTitle (30–60 car.), seoDescription (120–158), noindex, ogImage, lang par page ; headings [{blockId,level}] (1 = H1 unique, 2–6, 0 = texte simple) ; imageAlts [{blockId,alt}] ; site.lang / site.logo. auto=true remplit les titres et descriptions vides avec les suggestions (préférer écrire de vrais textes accrocheurs avec le mot-clé). publish=true publie les pages actives après les modifications de contenu. Retourne les manques restants.

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

Input Schema

NameRequiredDescriptionDefault
autoNoRemplir les titres et descriptions vides avec les suggestions calculées depuis le contenu
siteNo
pagesNo
publishNoPublier les pages actives après les corrections de contenu (titres Hn, alt)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say it is a non-readonly, idempotent, non-destructive write; the description goes beyond that by disclosing the publish side effect (active pages are published after content fixes) and by stating that remaining gaps are returned. It also warns that auto-filled text is lower quality than hand-written copy, which is genuine behavioral context. It omits any mention of permissions, scope limits (max 200 pages), or what happens to pages not listed, so it is not 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?

The core action is front-loaded and every clause about auto, publish, and return value carries information. It is a dense semicolon-chained run-on that partly duplicates the schema's own descriptions for auto and publish, which costs a little scannability, but nothing is padded.

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?

For a 4-parameter tool with nested objects and no output schema, the description covers all top-level inputs, the publish side effect, and the return value (remaining gaps). Missing are scope/cap behavior (max 200 pages) and any note on irreversibility or required permissions, but nothing an agent needs to call it is absent.

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?

With only 50% schema coverage, the description carries real weight: it supplies recommended character ranges the schema lacks (seoTitle 30–60 vs maxLength 191; seoDescription 120–158 vs maxLength 320) and explains heading level semantics (1 = single H1, 2–6, 0 = plain text). It also glosses the nested headings/imageAlts structures and site.lang/logo. Remaining gap: pageId and ogImage/noindex are named but get no extra guidance beyond 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?

"CORRIGER LE SEO des pages du site ... en un appel" gives a specific verb (fix) plus resource (site pages) and enumerates exactly which fields are written (seoTitle, seoDescription, noindex, ogImage, lang, headings, imageAlts, site.lang/logo). An agent can tell this is a bulk write tool, distinct from read-oriented siblings like audit_seo/get_seo_audit. It stops short of naming any sibling or contrasting with apply_page_changes/batch_update_pages, so it does not reach 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 Guidelines3/5

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

Usage is implied rather than spelled out: the note that auto=true fills empty titles/descriptions with suggestions, plus the parenthetical preference to write real keyword-rich texts instead, gives a usable decision rule for that one flag. publish=true is qualified as applying after content modifications. However there is no explicit statement of when to choose this tool over audit_seo/apply_page_changes, and no prerequisites or exclusions are given.

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.