Skip to main content
Glama

Add a slide

add_slide

Add a slide to a presentation you may edit, at the end or at "position" (1-based), optionally with its blocks right away. Returns the new slide (ids only unless "response" is "full").

Input Schema

NameRequiredDescriptionDefault
hNoCanvas height in px (default 720).
wNoCanvas width in px (200-4000, default 1280).
bgNoBackground colour, #rrggbb.
fitNoHow the background picture fits.
nameNoSlide name (at most 100 characters), in the language of the presentation.
slugYesThe presentation's slug (its address: /movie/<slug>/).
name_trNoThe slide name in the other languages of the site: {"en": "..."}.
objectsNoBlocks of the slide, bottom to top: [{"type": "text"|"shape"|"button"|"line"|"image"|"code", "props": {...}}]. Missing props take the presentation theme's defaults (every prop is described in the block format reference). A link to a slide of the same presentation may be given as {"kind": "slide", "slide_number": N}.
positionNo1-based place; default: the end.
responseNo"brief" (default): only the ids, numbers and types of the slides and blocks; "full": every prop of every block too.
backgroundNoBackground picture: the "src" of an uploaded picture; null removes it.
transitionNoEntrance effect of this incoming slide (default: none).none
transition_durationNoAnimation duration in milliseconds (100-3000, default 500); not auto advance. Values outside the range are clamped.

Output Schema

NameRequiredDescriptionDefault
hNo
wNo
bgNo
idYesStable id of the slide.
fitNo
urlNoThe address people open in a browser.
nameNo
notesNoThe speaker notes (for those who may edit; only when there are some).
numberYes1-based position; changes when slides are reordered.
name_trNoThe same text in the other languages of the site: {"en": "..."}.
objectsYesBlocks, bottom to top ("props" only in the full form).
versionNoStamp of the content as it is now: give it back as "base_version" to change it only if nobody else did meanwhile.
backgroundNoThe "src" of the background picture, or null.
transitionNoEntrance effect of this incoming slide.
layout_warningsNoHow the changed slides will probably look: texts too long for their blocks, blocks outside the slide, texts over each other (estimated -- look at them).
transition_durationNoAnimation milliseconds, not auto advance.
missing_translationsNoWhat is not translated yet into the other languages of the site (add it): the first ones; "missing_translations_count" says how many there are.
missing_translations_countNoHow many texts are not translated yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / objects / items / properties / type / description
      Previous value: -"text, shape, button, line, image or code."New value: +"text, shape, button, line, image, code or table."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / layout_warnings / items / properties / lang
      Added value: +{
      +  "description": "Only the text in this language has the problem.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / missing_translations / items / properties / outdated
      Added value: +{
      +  "description": "There is a translation, written for an earlier text.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / notes
      Added value: +{
      +  "description": "The speaker notes (for those who may edit; only when there are some).",
      +  "type": "string"
      +}
  4. Changed4 schema fields changed
    • addedOutput schema / properties / layout_warnings
      Added value: +{
      +  "description": "How the changed slides will probably look: texts too long for their blocks, blocks outside the slide, texts over each other (estimated -- look at them).",
      +  "items": {
      +    "properties": {
      +      "block_id": {
      +        "type": "integer"
      +      },
      +      "detail": {
      +        "type": "string"
      +      },
      +      "problem": {
      +        "description": "overflow, cut, outside or overlap.",
      +        "type": "string"
      +      },
      +      "slide_id": {
      +        "type": "integer"
      +      },
      +      "slide_number": {
      +        "type": "integer"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / missing_translations / description
      Previous value: -"What is not translated yet into the other languages of the site (add it)."New value: +"What is not translated yet into the other languages of the site (add it): the first ones; \"missing_translations_count\" says how many there are."
    • addedOutput schema / properties / missing_translations_count
      Added value: +{
      +  "description": "How many texts are not translated yet.",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "Stamp of the content as it is now: give it back as \"base_version\" to change it only if nobody else did meanwhile.",
      +  "type": "string"
      +}
  5. Changed4 schema fields changed
    • addedInput schema / properties / transition
      Added value: +{
      +  "default": "none",
      +  "description": "Entrance effect of this incoming slide (default: none).",
      +  "enum": [
      +    "none",
      +    "fade",
      +    "slide-left",
      +    "slide-right",
      +    "zoom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / transition_duration
      Added value: +{
      +  "default": 500,
      +  "description": "Animation duration in milliseconds (100-3000, default 500); not auto advance. Values outside the range are clamped.",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / transition
      Added value: +{
      +  "description": "Entrance effect of this incoming slide.",
      +  "enum": [
      +    "none",
      +    "fade",
      +    "slide-left",
      +    "slide-right",
      +    "zoom"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / transition_duration
      Added value: +{
      +  "description": "Animation milliseconds, not auto advance.",
      +  "maximum": 3000,
      +  "minimum": 100,
      +  "type": "integer"
      +}
  6. Changed4 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Slide name (at most 100 characters)."New value: +"Slide name (at most 100 characters), in the language of the presentation."
    • addedInput schema / properties / name_tr
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "The slide name in the other languages of the site: {\"en\": \"...\"}.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / missing_translations
      Added value: +{
      +  "description": "What is not translated yet into the other languages of the site (add it).",
      +  "items": {
      +    "properties": {
      +      "block_id": {
      +        "type": "integer"
      +      },
      +      "lang": {
      +        "type": "string"
      +      },
      +      "slide_id": {
      +        "type": "integer"
      +      },
      +      "slide_number": {
      +        "type": "integer"
      +      },
      +      "what": {
      +        "description": "title, slide name or block.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / name_tr
      Added value: +{
      +  "description": "The same text in the other languages of the site: {\"en\": \"...\"}.",
      +  "type": "object"
      +}
  7. Changed6 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Slide name (at most 30 characters)."New value: +"Slide name (at most 100 characters)."
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / response
      Added value: +{
      +  "description": "\"brief\" (default): only the ids, numbers and types of the slides and blocks; \"full\": every prop of every block too.",
      +  "enum": [
      +    "brief",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / description
      Added value: +"A slide; the brief form (the default of the tools that change slides) has only id, number, name, url and the id and type of every block."
    • changedOutput schema / properties / objects / description
      Previous value: -"Blocks, bottom to top."New value: +"Blocks, bottom to top (\"props\" only in the full form)."
    • changedOutput schema / properties / objects / items / required
      Previous value: -[
      -  "id",
      -  "type",
      -  "props"
      -]New value: +[
      +  "id",
      +  "type"
      +]
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "background": {
      +      "description": "The \"src\" of the background picture, or null.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "bg": {
      +      "type": "string"
      +    },
      +    "fit": {
      +      "type": "string"
      +    },
      +    "h": {
      +      "type": "integer"
      +    },
      +    "id": {
      +      "description": "Stable id of the slide.",
      +      "type": "integer"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "number": {
      +      "description": "1-based position; changes when slides are reordered.",
      +      "type": "integer"
      +    },
      +    "objects": {
      +      "description": "Blocks, bottom to top.",
      +      "items": {
      +        "properties": {
      +          "id": {
      +            "type": "integer"
      +          },
      +          "props": {
      +            "description": "Every prop of the block (see the block format reference).",
      +            "type": "object"
      +          },
      +          "type": {
      +            "description": "text, shape, button, line, image or code.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "type",
      +          "props"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "url": {
      +      "description": "The address people open in a browser.",
      +      "type": "string"
      +    },
      +    "w": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "number",
      +    "objects"
      +  ],
      +  "type": "object"
      +}
  9. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real value: it discloses the edit-permission requirement and the return shape (the new slide, ids only unless response="full"), which annotations do not.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and placement, then the return contract. No filler, and the parenthetical qualifiers are load-bearing.

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 13-parameter mutation tool with nested objects and an output schema, the description covers placement, optional inline blocks, and response verbosity — the decisions an agent must make. Minor gaps remain around whether creating a slide shifts existing slide numbers and any limits on slide count, but nothing essential to a correct call is missing.

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 coverage is 100%, so all 13 parameters including enums and the nested objects structure are already documented in the schema. The description restates position semantics and the response enum but adds no format, constraint, or interaction detail beyond what the schema provides. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource ("Add a slide") plus scope details: append or at a 1-based position, optionally with blocks. It clearly conveys what gets created. It does not, however, distinguish itself from the sibling add_slides (plural/batch), which an agent must otherwise infer from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"a presentation you may edit" implies the prerequisite permission, and the default placement (end) is stated, so usage is partially framed. But there is no explicit when-to-use guidance versus add_slides (batch insert), copy_slides, or edit_slides when adding blocks to an existing slide, and no stated failure conditions.

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.

Resources