Skip to main content
Glama

Outil.io

Convert group

convert_group

TRANSFORMER un groupe statique (cartes, colonnes, lignes de textes et images) en composant natif, en gardant son contenu et sa place : carousel (une diapositive par carte), tabs (un onglet par carte), faq (titre → question, textes → réponse) ou collection (LISTE DYNAMIQUE : les cartes deviennent des articles du blog, la première carte devient le modèle relié aux champs titre/résumé/image/date/catégorie/lien ; source products = produits du projet). Les cartes sont les sous-groupes du groupe ; sans sous-groupes, les colonnes puis les lignes. Le titre de section hors des cartes reste en place. Une version, brouillon ; ne pas reconstruire le composant à la main avec apply_page_changes.

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": {
      "pageId": "<pageId>",
      "snapshot": "<snapshot>",
      "refs": "<refs>",
      "target": "<target>"
    },
    "name": "convert_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
refsYesblocs du groupe à transformer (tous ses blocs) ; une seule ref = le groupe de cartes le plus proche autour de ce bloc
blogIdNocollection/articles : blog qui reçoit les articles ; absent = nouveau blog (blogName)
pageIdYes
sourceNocollection : articles (cartes importées comme articles) ou products (produits existants du projet, aucun import)articles
targetYescarousel (une diapositive par carte), tabs (un onglet par carte), faq (titre = question, reste = réponse), collection (liste dynamique : les cartes deviennent des articles du blog)
blogNameNo
snapshotYessnapshot de get_page_structure / get_page_elements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this is a non-destructive, non-open-world mutation. The description adds meaningful behavior: the result is a draft version, existing content and placement are preserved, and manual rebuilding is discouraged. It does not cover permissions or failure behavior, but it adds real context beyond the annotations.

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 main verb and resource are front-loaded, and the detail is largely earned by the four conversion modes. However, the single dense paragraph repeats some enum detail already present in the schema, so it could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter transformation tool with no output schema, the description covers the main modes, draft status, and the apply_page_changes alternative. It still omits what the tool returns, whether the original group is replaced or preserved separately, and how the draft is subsequently published.

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 description explains the semantics of target modes and of refs as the group's cards or subgroups, and clarifies that source=products uses existing project products rather than importing. With 71% schema coverage, the schema already documents several parameters, and the description usefully complements that for the conversion logic.

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?

The description states a specific action, 'transformer un groupe statique', and names exactly what it becomes: carousel, tabs, faq, or collection. It distinguishes itself from apply_page_changes by explicitly warning not to rebuild the component manually with that sibling.

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?

The conversion use case is clear, and the description explicitly routes the agent away from apply_page_changes for manual reconstruction. It does not give broader when-not-to-use conditions or compare against other conversion siblings, but the core guidance is present.

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.