Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: set transition

keynote_set_transition
Destructive

Set the transition effect, duration, delay, or auto-advance for a single Keynote slide, and preview changes safely with a dry run.

Instructions

Transition into a slide: effect such as dissolve, push, wipe, magic move, cube, flip, move in, reveal, "none"; duration/delay in seconds; automatic=true advances on its own. Other slides verified untouched. dry_run=true previews the change on a copy without touching the file. Use for one slide's transition. For the same transition on every slide of a new deck, pass transition= to keynote_build_deck.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the .key deck (absolute, or starting with ~).
delayNoDelay before it starts, in seconds.
slideYesSlide number, 1-based (keynote_list_slides lists them).
effectYesTransition effect, e.g. "dissolve", "push", "magic move", or "none".
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.
durationNoDuration in seconds.
automaticNotrue = advance to the next slide on its own.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.4.1
    • addedInput schema / properties / automatic / description
      Added value: +"true = advance to the next slide on its own."
    • addedInput schema / properties / delay / description
      Added value: +"Delay before it starts, in seconds."
    • 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 / duration / description
      Added value: +"Duration in seconds."
    • addedInput schema / properties / effect / description
      Added value: +"Transition effect, e.g. \"dissolve\", \"push\", \"magic move\", or \"none\"."
    • 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)."
  2. First observedv2.4.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds real behavioral context on top: dry_run previews on a throwaway copy without touching the file, and other slides are verified untouched. It does not address idempotentHint=false (repeat-call behavior), so it stops short of a 5.

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?

Front-loads the core action and the effect list, then appends the dry_run and sibling-routing notes. Semicolon-heavy and slightly packed, but every clause carries information and nothing is wasted.

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?

An output schema exists, so return values need not be explained. With annotations covering the safety profile and 100% schema coverage, plus the description's dry_run and sibling guidance, an agent has everything needed to invoke this correctly.

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 meaning the schema lacks: it enumerates effect values (compensating for zero enums) and clarifies the units and semantics of duration/delay ('in seconds') and automatic ('advances on its own').

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 and resource ('Transition into a slide'), enumerates the effect values, and scopes itself to a single slide. It explicitly separates itself from keynote_build_deck, which handles deck-wide transitions.

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?

'Use for one slide's transition' plus the explicit alternative — 'For the same transition on every slide of a new deck, pass transition= to keynote_build_deck' — gives a clear when-to-use and when-not-to-use routing rule. Nothing is left to inference.

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