Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: set slide text

keynote_set_slide_text
Destructive

Fill or rewrite one Keynote slide's title and body, using bullet lists when needed. Preview edits on a copy with dry_run before touching the file.

Instructions

Fill a slide's title and/or body box (body may be a list of bullet lines). The title box is the top-most text box, the body the largest other one. Other slides and text boxes are verified untouched. dry_run=true previews the change on a copy without touching the file. Use to fill or rewrite one slide's title and body. To change the same words across the deck use keynote_replace_text; for speaker notes use keynote_set_presenter_notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoNew body: a string, or a list of bullets; omit to leave it.
pathYesPath to the .key deck (absolute, or starting with ~).
slideYesSlide number, 1-based (keynote_list_slides lists them).
titleNoNew title text; omit to leave it.
dry_runNotrue = make the change on a throwaway copy, run every check, and return what would change; the file itself is not touched. Use it before broad or risky edits and show the user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.4.1
    • addedInput schema / properties / body / description
      Added value: +"New body: a string, or a list of bullets; omit to leave it."
    • addedInput schema / properties / dry_run / description
      Added value: +"true = make the change on a throwaway copy, run every check, and return what would change; the file itself is not touched. Use it before broad or risky edits and show the user."
    • addedInput schema / properties / path / description
      Added value: +"Path to the .key deck (absolute, or starting with ~)."
    • addedInput schema / properties / slide / description
      Added value: +"Slide number, 1-based (keynote_list_slides lists them)."
    • addedInput schema / properties / title / description
      Added value: +"New title text; omit to leave it."
  2. First observedv2.4.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds useful context beyond them: only title/body boxes change, other slides and text boxes are verified untouched, and dry_run previews on a copy. It stops short of describing return shape or error conditions, but it meaningfully supplements the destructive-write profile.

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?

Front-loads the core action, then scoping, then safety/dry_run, then alternatives. Every sentence carries distinct information with no filler or repetition of the name.

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 destructive single-slide text edit with an output schema present, the description covers scope limits, mutation impact, dry_run semantics, and sibling alternatives. Nothing an agent needs 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 schema already documents all five parameters (baseline 3). The description adds genuine meaning beyond the schema by defining what 'title' and 'body' boxes physically are (top-most text box / largest other one) and noting body accepts bullet lists.

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?

States a specific verb+resource ('fill/rewrite one slide's title and body') and clarifies the target semantics (title = top-most text box, body = largest other one). It explicitly distinguishes itself from keynote_replace_text and keynote_set_presenter_notes, so the agent can route 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 Guidelines5/5

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

Gives explicit when-to-use ('fill or rewrite one slide') and names two alternatives with the conditions that select them (same words across deck -> keynote_replace_text; speaker notes -> keynote_set_presenter_notes). Also advises when to use dry_run for risky edits.

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

Deploy Server

Other Tools