Skip to main content
Glama

Outil.io

Import HTML page

import_html_page

Convertir une page HTML complète en canevas Outil éditable (rendu PC, tablette, téléphone). CLONAGE : utiliser d’abord clone_website {url,mode} (capture et conversion côté serveur, site entier ou page, puis check_site_completeness). clone_page_in_outil côté client, quand il est disponible, capture le DOM complet du navigateur du client et transmet directement html + sourceUrl + fidelity=source + sourceCapture sans faire transiter le HTML par le contexte du modèle. Ne pas télécharger le document source côté serveur à la place. Ne pas réécrire le design ni utiliser un modèle approximatif. Le mode source conserve la navigation capturée, les liens et la composition, sans formulaire, popup ni animation inventés. Comparer les captures source/résultat aux trois formats et corriger avant de prétendre au pixel perfect ; vérifier warnings et failedAssets. CRÉATION ORIGINALE : fidelity=design (défaut sans sourceUrl), HTML autonome avec CSS responsive, images publiques ; form règle le formulaire Outil ajouté. La conversion ne reproduit pas automatiquement le backend ou les scripts métier de la source. Après un import source : prepare_clone_improvement fournit déjà la structure légère et le snapshot ; lire get_page_elements avec refs/fields ciblés, corriger en un lot apply_page_changes, puis vérifier par capture_page_images groupée et record_clone_review. Réserver apply_clone_repairs/compose_page aux changements de structure. Si la demande porte sur un modèle de bibliothèque, appeler create_template_draft avec la page créée, puis suivre get_template_review : aucune publication du modèle avant les contrôles natifs et visuels.

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": {
      "name": "<name>",
      "slug": "<slug>",
      "html": "<html>"
    },
    "name": "import_html_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoOption de formulaire complémentaire, avec placement explicite. Préférer un vrai formulaire HTML dessiné à l’emplacement voulu, converti en composant natif avec son style. Choisir consciemment page ou popup ; aucun formulaire générique en bas ni minuterie par défaut. Les CTA vidéo, paiement et liens externes ne sont pas détournés vers le formulaire.
htmlYes
kindNo
nameYes
slugYes
pageIdNoRemplacer le brouillon existant plutôt que créer une nouvelle page ; historique conservé
siteIdNo
fidelityNosource = clonage fidèle sans ajouts génériques (défaut avec sourceUrl) ; design = création originale avec navigation/formulaire Outil
funnelIdNo
sourceUrlNoURL finale de la page source, pour résoudre ses CSS/images/polices relatifs ; fournir le HTML complet dans html
sourceCaptureNoPreuve de transfert calculée par clone_page_in_outil côté client ; ne jamais la fabriquer à la main
expectedVersionNoObligatoire avec pageId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the supplied annotations (readOnlyHint=false, destructiveHint=false): it discloses that source mode preserves navigation/links without inventing forms, popups or animations, that backend/business scripts are not reproduced, that sourceCapture must never be fabricated, and that warnings/failedAssets must be checked. Rich behavioral context; only minor gaps in what gets overwritten.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and segmented into CLONAGE / CRÉATION ORIGINALE blocks, but the body is dense and long, packing many workflow steps into few sentences; it earns most of its length yet could be tightened.

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 12-parameter, nested-object tool with no output schema, the description covers the key behavioral and workflow semantics (clone vs create, fidelity modes, sourceCapture integrity, post-import verification loop). Only a few parameters lack prose explanation.

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?

Adds meaning for the complex params — fidelity source vs design default, form placement rules, sourceUrl usage for resolving relative assets, and sourceCapture as client-computed proof. However with 50% coverage it leaves kind, slug, siteId, funnelId and expectedVersion unexplained in prose, relying on the schema for those.

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 and resource ('Convertir une page HTML complète en canevas Outil éditable') with PC/tablet/phone rendering scope, and explicitly distinguishes the tool from clone_website and clone_page_in_outil so an agent can route 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 ordering: use clone_website/clone_page_in_outil for cloning first, fidelity=design for original creation, reserve apply_clone_repairs/compose_page for structural changes, and use create_template_draft for library templates. Both when-to-use and when-not-to-use are named with alternatives.

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.