Skip to main content
Glama

Outil.io

Create personalized pages

create_personalized_pages

Dupliquer une page modèle pour chaque prospect (1 à 50) avec ses variables remplies dans tous les textes, textes alternatifs et liens : {{prospect.company}}, {{prospect.city}}, {{prospect.name}}, {{prospect.website}}, {{prospect.jobTitle}}, {{contact.firstName}}, et {{custom.clé}} via variables {"":{"clé":"valeur"}}. La page modèle n’est jamais modifiée ; chaque copie reste en BROUILLON par défaut (publish:true pour la publier, masquée des moteurs de recherche, après accord du client) à une adresse unique ; un prospect dont une variable est vide est ignoré avec la raison. Mettre ensuite l’url retournée dans le message de prospection (clics suivis par prospect dans les e-mails). IDEMPOTENT : rappeler avec la même page modèle et les mêmes prospects met à jour leurs copies existantes (même pageId, même URL, reused:true) au lieu d’en créer de nouvelles ; duplicate:true force une copie supplémentaire.

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": {
      "templatePageId": "<templatePageId>"
    },
    "name": "create_personalized_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
publishNo
duplicateNo
variablesNo
contactIdsNo
slugPrefixNo
prospectIdsNo
templatePageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / duplicate
      Added value: +{
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes far beyond the annotations: states the template is never modified, that copies default to BROUILLON, that publish:true publishes them hidden from search engines after client approval, that each copy gets a unique address, that prospects with empty variables are skipped with a reason, and that the operation is idempotent with reused:true. This is exactly the mutation/approval/retry context an agent needs and that readOnlyHint=false / destructiveHint=false cannot convey.

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?

Dense but front-loaded: the batch/duplicate action comes first, then safety and idempotency. It is one long run-on paragraph with several clauses chained by semicolons, which could be broken into scannable segments, but no sentence is filler.

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 7-parameter nested-object mutation with no output schema, it covers the lifecycle (draft vs published, unique URL, reuse on retry) and the skip-with-reason outcome. Remaining gaps are the meaning of slugPrefix and when contactIds should be used instead of prospectIds.

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?

Schema coverage is 0% on 7 parameters, and the description compensates well for the important ones: it spells out the nested variables shape ({"<prospectId>":{"clé":"valeur"}}), the placeholder syntax, publish:true, duplicate:true, and the role of templatePageId. It leaves slugPrefix and contactIds (as distinct from prospectIds) unexplained, so not a 5.

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 ('Dupliquer une page modèle pour chaque prospect') plus the mechanism (variable substitution in texts, alt texts and links) and the batch bound (1 à 50). An agent can tell this apart from create_page or create_site_from_template purely from the description.

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?

Gives a clear usage context — build prospect landing pages, then put the returned URL into the prospecting message — and explicitly describes the recall/idempotency path ('rappeler avec la même page modèle') plus the duplicate:true escape hatch. It does not name any sibling alternative, so it stops short of a 5.

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.