Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: set slide layout

keynote_set_slide_layout
Destructive

Change a single Keynote slide's layout (master) while leaving other slides untouched. Use dry_run=true to preview changes on a copy without modifying the file.

Instructions

Change one slide's layout (master), e.g. "Title & Bullets". Other slides are verified untouched. dry_run=true previews the change on a copy without touching the file. Use to change one slide's layout (names from keynote_inspect_style). Not for text styling: use keynote_format_text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the .key deck (absolute, or starting with ~).
slideYesSlide number, 1-based (keynote_list_slides lists them).
layoutYesLayout (master slide) name from keynote_inspect_style.
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. Changed4 schema fields changedv2.4.1
    • 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 / layout / description
      Added value: +"Layout (master slide) name from keynote_inspect_style."
    • 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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds blast-radius context beyond them: "Other slides are verified untouched" and dry_run runs "on a throwaway copy" without touching the file. It still does not say whether content that no longer fits the new layout is lost, or how to undo the change.

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-loaded with the core action and short overall, but the third sentence restates the first sentence's purpose ("Use to change one slide's layout") instead of only adding the exclusion, which is mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and the description covers scope, verification, naming source, alternatives, and safe-preview behavior. The only gap is recovery/undo guidance for a destructive, non-idempotent operation, though dry_run mitigates much of that risk.

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 real meaning: dry_run's preview semantics and the source of valid layout names. The "Title & Bullets" example also illustrates the layout parameter's expected value shape.

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 with scope ("Change one slide's layout (master)") and gives a concrete example layout name. It also implicitly separates itself from deck-level and text-level tools by calling out the singular slide and the master concept.

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?

Explicitly says where layout names come from ("names from keynote_inspect_style") and names the exclusion with its alternative ("Not for text styling: use keynote_format_text"). It also gives a usage recommendation for dry_run ("Use it before broad or risky edits and show the user").

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