Skip to main content
Glama

set_slide

Add, replace, or insert slides in a presentation with precise positional control. Use expected_slide_count to prevent concurrent edit conflicts.

Instructions

Add, replace, or insert a slide.

insert=False (default): index < slide count -> replace in place; index >= slide count -> append. insert=True: inserts at index, shifting that slide and everything after it later (index >= slide count still appends). Combine with delete_slide to move a slide to a new position.

content is raw Pandoc Markdown -- also supports speaker notes by name alone. Exact syntax for three Beamer-specific conventions: Incremental bullets : > - item Section divider : content is ONLY "# Section Title", nothing else Two-column layout : :::: {.columns}\n::: {.column width="50%"}\nLeft\n:::\n::: {.column width="50%"}\nRight\n:::\n::::

expected_slide_count : optional. If a concurrent call already changed the deck since you last checked, this fails with a clear error instead of silently landing at an unintended position -- get_presentation to refresh, then retry. Recommended when issuing several set_slide calls for the same presentation without waiting for each result first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes
titleYes
insertNo
contentYes
presentation_idYes
expected_slide_countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavior: default append/replace logic, shift semantics for insert, and the concurrency failure behavior when expected_slide_count mismatches. It also details content format constraints for Pandoc Markdown and Beamer-specific syntax, which is critical for correct invocation.

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?

The description is dense but every sentence adds value—no filler. It is well-structured with clear sections for operational modes, content format, and concurrency guidance, making it easy to parse without sacrificing important details.

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 tool of this complexity, the description covers all essential aspects: operation semantics, content format specifics, concurrency handling, and related tools. The presence of an output schema means return values don't need to be explained, and the description is otherwise complete for safe and correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all parameters. It thoroughly explains insert, content (with examples), expected_slide_count, and index behavior relative to slide count. Presentation_id and title are self-evident from their names, so the description sufficiently compensates for the lack of schema descriptions.

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 'Add, replace, or insert a slide,' which clearly states the tool's function with a specific verb and resource. It further distinguishes itself from siblings like delete_slide and get_slide by detailing the different insertion/replacement modes, making the purpose unambiguous.

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 explicitly explains when to use insert=True vs insert=False, including edge cases like index >= slide count. It also recommends combining with delete_slide to move slides and suggests using expected_slide_count for concurrent calls, providing clear when-to-use guidance and pointing to get_presentation as an alternative for refreshing state.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mariolpantunes/crepe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server