Skip to main content
Glama

Add objects

add_objects

Add text boxes, shapes and images on top of one slide of a saved template, up to 50 per call and 50 per slide. Requires a Pro account. Use this instead of update_template to place objects: it never touches slots, other slides or other objects. Each item is {type:"text", text, ...}, {type:"shape", shape, text?, ...} or {type:"image", asset, ...}; position and size are optional (a text box or shape lands near the middle, an image is centered and fitted). Shapes: shape is "rect", "roundRect", "ellipse", "line" or "arrow". A new shape starts with a look of its own (an accent fill and centred text for a box; an ink line 4 px wide for a line), so send only what differs. A box shape takes fill, fillOpacity, borderColor, borderWidth, dash, shadow, roundRect also radius (px), and text with the text fields. A line or arrow runs left to right through the middle of its box (turn it with rotate; the arrowhead is at the right end) and takes lineColor, lineWidth, dash; it holds no text. Shapes are native shapes in the PPTX. Coordinates are pixels on a 1920x1080 slide and are kept inside it. A text box's style takes theme colours, "palette:" or "#rrggbb", plus italic, underline, line spacing, fill, border, radius and shadow (see style). Images come only from list_media ids. Set behind:true to put an object under the layout's own title and text (a background picture behind the default title); it is hidden wherever a layout card or panel has a solid fill. All items are added or none. Returns the slide's objects with their ids and the new draft_version. The edit is saved to the template's draft; call publish_template to publish it. Errors: pro_required, not_found, conflict (read again with get_template(draft: true) and retry), invalid_input.

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": {
      "template_id": "<template_id>",
      "slide_id": "<slide_id>",
      "objects": "<objects>"
    },
    "name": "add_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectsYesText boxes, shapes and images to add to the slide.
slide_idYesThe slide's id from get_template.
template_idYesFrom list_templates.
expected_versionNoOlder callers: the published version from get_template. Given, the call fails with conflict if the template was published since.
expected_draft_versionNoThe draft_version from get_template(draft: true) or your last save (0: no draft yet). Given, the call fails with conflict if the draft changed since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / expected_draft_version
      Added value: +{
      +  "description": "The draft_version from get_template(draft: true) or your last save (0: no draft yet). Given, the call fails with conflict if the draft changed since.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / expected_version / description
      Previous value: -"The version from get_template. Given, the call fails with conflict if the template changed since."New value: +"Older callers: the published version from get_template. Given, the call fails with conflict if the template was published since."
  2. Changed28 schema fields changed
    • changedInput schema / properties / objects / description
      Previous value: -"Text boxes and images to add to the slide."New value: +"Text boxes, shapes and images to add to the slide."
    • addedInput schema / properties / objects / items / properties / group
      Added value: +{
      +  "description": "Objects with the same group id are picked, moved and copied together in the web editor (1 to 40 letters, digits, \"_\" or \"-\"). Has no effect on how the slide looks or exports.",
      +  "type": "string"
      +}
    • addedInput schema / properties / objects / items / properties / locked
      Added value: +{
      +  "description": "true: the web editor will not move, resize, change or delete it until it is unlocked. A locked object also refuses update_objects and remove_objects until a change sends locked:false. Has no effect on how the slide looks or exports.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / objects / items / properties / runs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "end": {
      +            "type": "number"
      +          },
      +          "start": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "start",
      +          "end"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Formatting of part of the text: [{ start, end, bold?, italic?, underline?, color?, link? }]. start and end are UTF-16 offsets into the text (JavaScript string indices: a Korean syllable counts 1, an emoji outside the basic plane 2), end exclusive, start < end. bold, italic, underline are true or false (false undoes a look the whole text has); color takes the colour forms below; link is kept for a later version and not drawn yet. The text itself stays plain. Ranges must fit the text, else the call fails with invalid_input. Shown in the editor, the PPTX (one text run per piece) and the HTML export. Changing the text without sending runs moves the stored runs with it (text before a range shifts it; a range whose characters are all deleted is dropped); send runs with the text to set them yourself, null (update_objects) or [] to remove them. Fields you do not know on a run are kept."
      +}
    • addedInput schema / properties / objects / items / properties / shape
      Added value: +{
      +  "description": "Shape only (required for type \"shape\"). Shapes: shape is \"rect\", \"roundRect\", \"ellipse\", \"line\" or \"arrow\". A new shape starts with a look of its own (an accent fill and centred text for a box; an ink line 4 px wide for a line), so send only what differs. A box shape takes fill, fillOpacity, borderColor, borderWidth, dash, shadow, roundRect also radius (px), and text with the text fields. A line or arrow runs left to right through the middle of its box (turn it with rotate; the arrowhead is at the right end) and takes lineColor, lineWidth, dash; it holds no text. Shapes are native shapes in the PPTX.",
      +  "enum": [
      +    "rect",
      +    "roundRect",
      +    "ellipse",
      +    "line",
      +    "arrow"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / objects / items / properties / style / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / objects / items / properties / style / description
      Previous value: -"Text box look. Only the fields you send change."New value: +"Text box or shape look. Only the fields you send change; null takes a field away. Look fields (all optional; send null to take one away and go back to the default): text: size (8-400 px; in an override entry it is called fontSize), weight (400 or 700), italic, underline, strike (true/false), align (\"left\", \"center\", \"right\"), lineHeight (multiple of the size, 0.5-4), vAlign (\"top\", \"middle\", \"bottom\"; text boxes only), color. box: fill (a colour or \"none\"), fillOpacity (0-1), borderColor, borderWidth (0-40 px), radius (0-540 px), shadow (\"none\", \"sm\", \"md\", \"lg\"). line (strokes of a drawn line or icon): lineColor, lineWidth (0.5-40 px), dash (\"solid\", \"dash\", \"dot\"; also the border's style). A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme. Some layout elements are drawn as a picture in the PPTX; colours stored for them are ignored on every output."
    • changedInput schema / properties / objects / items / properties / style / properties / align / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / objects / items / properties / style / properties / borderColor
      Added value: +{
      +  "description": "A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / borderWidth
      Added value: +{
      +  "description": "0 to 40 px; 0 is no border.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / objects / items / properties / style / properties / color / description
      Previous value: -"A theme token such as \"ink\", \"ink-soft\", \"accent\", \"bg\", \"danger\". Not a color value."New value: +"A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme."
    • changedInput schema / properties / objects / items / properties / style / properties / color / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / objects / items / properties / style / properties / dash
      Added value: +{
      +  "description": "Border or line style: \"solid\", \"dash\" or \"dot\".",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / fill
      Added value: +{
      +  "description": "Box fill: a colour, or \"none\".",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / fillOpacity
      Added value: +{
      +  "description": "0 to 1, the fill only.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / italic
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / lineColor
      Added value: +{
      +  "description": "A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / lineHeight
      Added value: +{
      +  "description": "Line spacing as a multiple of the size, 0.5 to 4. Default 1.3.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / lineWidth
      Added value: +{
      +  "description": "Line and arrow shapes: 0.5 to 40 px.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / radius
      Added value: +{
      +  "description": "Corner radius, 0 to 540 px.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / shadow
      Added value: +{
      +  "description": "\"none\", \"sm\", \"md\" or \"lg\".",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / objects / items / properties / style / properties / size / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • addedInput schema / properties / objects / items / properties / style / properties / strike
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / underline
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / objects / items / properties / style / properties / vAlign
      Added value: +{
      +  "description": "\"top\" (default), \"middle\" or \"bottom\" inside the box.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / objects / items / properties / style / properties / weight / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedInput schema / properties / objects / items / properties / text / description
      Previous value: -"Text box only. Up to 1000 characters."New value: +"Text box (required) or a rect, roundRect or ellipse shape (the text inside it). Up to 1000 characters."
    • changedInput schema / properties / objects / items / properties / type / enum
      Previous value: -[
      -  "text",
      -  "image"
      -]New value: +[
      +  "text",
      +  "image",
      +  "shape"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / objects / description
      Added value: +"Text boxes and images to add to the slide."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds substantial context beyond that: the operation is all-or-nothing, it writes to the template's draft and requires publish_template to go live, behind:true hides under solid-fill layout cards, coordinates are clamped to 1920x1080, and it enumerates error codes (pro_required, not_found, conflict, invalid_input).

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?

The definition is dense but front-loaded: scope, limits, alternative, then item shapes, then defaults, then atomicity/return, then errors. Some sentences (the shape-defaults and shape enumeration blocks) are repeated nearly verbatim from the schema, which is redundancy an agent doesn't need twice.

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?

For a 5-parameter mutation tool with no output schema, the description covers everything needed to call it correctly: account requirement, per-call/per-slide caps, item typing, default positioning and styling, layering via behind, atomicity, what is returned (objects with ids plus new draft_version), publish step, and the error/retry path.

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 100%, so baseline is 3, but the description adds real meaning: object item shapes ({type:"text"|"shape"|"image"}), that position/size are optional with per-type default placement, how line/arrow shapes are oriented (left-to-right, arrowhead at right end), and default styling so callers only send differences. Minor duplication with the schema's own shape/style descriptions limits it to 4.

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 opens with a precise verb and resource (add text boxes, shapes and images to one slide of a saved template) and immediately names the sibling it replaces for this job (update_template). An agent can distinguish it from update_objects/update_template without opening any 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?

It states when to use this tool instead of update_template ("it never touches slots, other slides or other objects") and gives operational bounds: up to 50 per call and 50 per slide, Pro account required. Conflict handling guidance is also explicit: re-read with get_template(draft: true) and retry.

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