Skip to main content
Glama

Update slideshow run

update_slideshow_run

Partially update an existing Slideshow Run by runId to patch slide copy, layout, styling, or brand settings while preserving unspecified fields; include baseRevision to prevent overwrite conflicts.

Instructions

Partially update slide copy, slot bindings, layout, styling, or brand settings of an existing Slideshow Run by runId. Call get_slideshow_run first to obtain current revision and slide data. Do NOT use to create new runs (use create_slideshow_run) or delete runs (use delete_slideshow_run). Safe partial patch: unspecified fields are preserved. Requires baseRevision for optimistic concurrency locking; on revision mismatch returns 409 Conflict (no auto-merge), requiring a fresh get_slideshow_run. To patch a single slide, provide pageIndex (0-indexed) with slots, layout, or style. To update entire deck, provide pack. Returns updated SlideshowRun with incremented revision number.

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": {
      "runId": "<runId>"
    },
    "name": "update_slideshow_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoUpdated complete content-pack.v1 structure. Overrides entire slide deck when provided.
postNoThe post text beside the images: { title?, description? }. Only the fields in the Run's postLimits exist on its platform; keep within those limits.
runIdYesThe unique Slideshow Run identifier to update.
slotsNoKey-value map of slot text/image overrides for the specified pageIndex.
styleNoStyle token adjustments for the specified pageIndex.
layoutNoLayout adjustments for the specified pageIndex.
brandIdNoUpdated Brand ID styling reference applied across slides.
pageIndexNoIndex of a single slide page to patch (0-indexed). Must be paired with slots, layout, style, or decorations.
contentSlugNoUpdated content topic slug.
decorationsNoVisual decorations list for the specified pageIndex.
baseRevisionNoCurrent revision number for optimistic concurrency locking to prevent overwrite races. Must match latest revision from get_slideshow_run.
brandProfileIdNoOptional legacy brand profile ID.

Output Schema

NameRequiredDescriptionDefault
runIdNoRun identifier.
revisionNoIncremented revision number.
studioUrlNoStudio review URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.46
    • addedInput schema / properties / post
      Added value: +{
      +  "description": "The post text beside the images: { title?, description? }. Only the fields in the Run's postLimits exist on its platform; keep within those limits.",
      +  "type": "object"
      +}
  2. Changed6 schema fields changedv0.1.17
    • changedInput schema / properties / baseRevision / description
      Previous value: -"Current revision number for optimistic concurrency locking to prevent overwrite races."New value: +"Current revision number for optimistic concurrency locking to prevent overwrite races. Must match latest revision from get_slideshow_run."
    • changedInput schema / properties / brandId / description
      Previous value: -"Updated Brand ID styling reference."New value: +"Updated Brand ID styling reference applied across slides."
    • changedInput schema / properties / pack / description
      Previous value: -"Updated complete content-pack.v1 structure."New value: +"Updated complete content-pack.v1 structure. Overrides entire slide deck when provided."
    • changedInput schema / properties / pageIndex / description
      Previous value: -"Index of a single slide page to patch (0-indexed)."New value: +"Index of a single slide page to patch (0-indexed). Must be paired with slots, layout, style, or decorations."
    • changedInput schema / properties / slots / description
      Previous value: -"Key-value map of slot overrides for the specified pageIndex."New value: +"Key-value map of slot text/image overrides for the specified pageIndex."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "revision": {
      +      "description": "Incremented revision number.",
      +      "type": "number"
      +    },
      +    "runId": {
      +      "description": "Run identifier.",
      +      "type": "string"
      +    },
      +    "studioUrl": {
      +      "description": "Studio review URL.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed11 schema fields changedv0.1.16
    • addedInput schema / properties / baseRevision / description
      Added value: +"Current revision number for optimistic concurrency locking to prevent overwrite races."
    • addedInput schema / properties / brandId / description
      Added value: +"Updated Brand ID styling reference."
    • addedInput schema / properties / brandProfileId / description
      Added value: +"Optional legacy brand profile ID."
    • addedInput schema / properties / contentSlug / description
      Added value: +"Updated content topic slug."
    • addedInput schema / properties / decorations / description
      Added value: +"Visual decorations list for the specified pageIndex."
    • addedInput schema / properties / layout / description
      Added value: +"Layout adjustments for the specified pageIndex."
    • addedInput schema / properties / pack / description
      Added value: +"Updated complete content-pack.v1 structure."
    • addedInput schema / properties / pageIndex / description
      Added value: +"Index of a single slide page to patch (0-indexed)."
    • addedInput schema / properties / runId / description
      Added value: +"The unique Slideshow Run identifier to update."
    • addedInput schema / properties / slots / description
      Added value: +"Key-value map of slot overrides for the specified pageIndex."
    • addedInput schema / properties / style / description
      Added value: +"Style token adjustments for the specified pageIndex."
  4. First observedv0.1.13

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses that this is a safe partial patch (unspecified fields preserved), that baseRevision drives optimistic concurrency, that a mismatch yields 409 Conflict with no auto-merge and requires a fresh get_slideshow_run, and that the returned run has an incremented revision. These are exactly the non-obvious behaviors an agent needs; the only omission is what happens when neither pageIndex nor pack is supplied.

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?

Despite covering purpose, prerequisites, exclusions, concurrency, and the two patch modes, every sentence carries distinct information and the critical constraint (get first, baseRevision) is front-loaded. No redundant restatement of the title or the schema field list.

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 12-parameter mutation tool with nested objects and an output schema, the description covers prerequisites, partial-patch semantics, concurrency failure mode, and single-slide versus whole-deck targeting. Return-value details are correctly left to the output schema, and nothing needed to invoke it correctly 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 coverage is 100%, so the baseline is 3, but the description adds relational meaning the schema cannot convey: pageIndex is 0-indexed and must be paired with slots/layout/style, while pack overrides the entire deck. It does not clarify the interaction between brandId, brandProfileId, or contentSlug, which remain schema-only.

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 specific verb and scope: 'Partially update slide copy, slot bindings, layout, styling, or brand settings of an existing Slideshow Run by runId.' It enumerates the mutable surfaces and names the sibling operations (create_slideshow_run, delete_slideshow_run) that it is not, so an agent can select it without opening the 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 gives explicit preconditions ('Call get_slideshow_run first to obtain current revision'), explicit exclusions ('Do NOT use to create new runs... or delete runs'), and routes to the correct alternatives by name. It also splits the two usage modes: pageIndex+slots/layout/style for a single slide versus pack for the entire deck.

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