Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Export presentation

export_presentation
Read-only

Exporter une présentation. pptx : renvoie un lien de téléchargement signé, valable 1 h. mp4 : lance le rendu vidéo (une diapositive par plan, voix off quand elle est configurée, sinon le temps de lire les notes) et renvoie jobId ; suivez-le avec presentation_job, qui donne le lien signé (1 h) quand la vidéo est prête.

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": {
      "id": "<id>",
      "format": "<format>"
    },
    "name": "export_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
voiceNomp4 : voix de la voix off (F1…F5, M1…M5 ou prénom), si la synthèse vocale est configurée.
formatYespptx : PowerPoint modifiable (lien immédiat) ; mp4 : vidéo des diapositives avec la voix off (tâche de fond).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the signed link expires after 1 hour, mp4 is a background task identified by jobId, and the render uses one slide per shot with voice-over when configured, otherwise note-reading duration. It also discloses the async handoff to presentation_job rather than implying an immediate result.

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?

Three short sentences, front-loaded with the purpose, then format-specific behavior, then the polling handoff — no filler. It is dense and slightly run-on inside the mp4 clause, but every clause carries information an agent needs.

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

Completeness5/5

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

There is no output schema, so the description must explain returns, and it does: a signed link for pptx, a jobId for mp4, and where the final link comes from. For a 3-parameter tool with one enum and async behavior, nothing an agent needs in order to call it and follow up is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents id, format and voice. The description adds meaning the schema does not: pptx yields an immediate link while mp4 is a background job, and the voice parameter only matters when speech synthesis is configured, with note-reading timing as the fallback. That is real semantic value on top of the structured fields.

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+resource ("Exporter une présentation") and then splits the behavior by format: pptx returns a signed download link, mp4 launches a video render and returns a jobId. It explicitly distinguishes itself from the sibling presentation_job, which handles polling, so an agent can pick the right tool without opening either schema.

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?

Usage is clear from the format split: choose pptx for an editable file with an immediate link, mp4 for a video render. It also routes the agent to presentation_job for tracking the async case, which is the key alternative. It never states exclusions (e.g. what to do if voice synthesis is not configured beyond a fallback), so it falls just short of fully explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Outil.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources