Skip to main content
Glama

Outil.io

Create personalized videos

create_personalized_videos

Copier un montage vidéo modèle pour chaque prospect (1 à 20) avec ses variables remplies dans les textes à l’écran et les sous-titres : {{prospect.company}}, {{prospect.city}}, {{prospect.name}}, {{contact.firstName}}, {{custom.clé}} (variables {"":{"clé":"valeur"}}). Le modèle n’est pas modifié, les médias sont partagés ; un prospect dont une variable est vide est ignoré avec la raison. La voix off n’est pas régénérée : écrire les textes variables à l’écran, pas dans la voix. Ensuite exporter les copies une à une (start_video_export, get_video_export) et mettre le lien dans le message.

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": {
      "templateProjectId": "<templateProjectId>"
    },
    "name": "create_personalized_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
variablesNo
contactIdsNo
prospectIdsNo
templateProjectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses that the template itself is not modified and media is shared, that prospects with an empty variable are skipped with a stated reason, and that voiceover is not regenerated so variable text must go in on-screen text. These are genuinely useful side-effect and limitation details. It stops short of describing the response payload beyond the skip reason.

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?

One dense paragraph, front-loaded with the core action and followed by placeholder and workflow detail; there is little wasted wording. The closing export instructions are useful but slightly dilutes focus by describing a downstream tool's job.

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 non-read-only, nested-object tool with no output schema, the description covers side effects, skip conditions, and the follow-up export path, which is most of what an agent needs. The remaining gap is the semantics of the two ID arrays and what the creation call returns (copies created vs skipped).

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?

Schema description coverage is 0%, so the description carries the burden and does explain the variables structure ({"<prospectId>":{"clé":"valeur"}}) and the placeholder syntax. However, it never clarifies the relationship between contactIds and prospectIds, nor that templateProjectId is the UUID of the source project to copy. Half the parameters remain semantically thin.

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 names a specific verb and resource: copy a video template montage once per prospect (1 to 20) with variables injected into on-screen text and subtitles. It enumerates the exact placeholders ({{prospect.company}}, {{prospect.city}}, {{contact.firstName}}, {{custom.clé}}) and the expected variables map shape, so an agent knows precisely what the tool produces.

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?

It gives concrete sequencing guidance: after creation, export each copy one by one via start_video_export and get_video_export, then place the link in the message. It also implicitly scopes input size (1 to 20). It does not explicitly say when to prefer this over create_video_project or create_personalized_pages, so sibling routing is left partly to inference.

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.