iWork Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

Keynote: apply design

keynote_apply_design

Destructive

Restyle a Keynote deck by applying a design kit's theme, fonts, sizes, and contrast-checked colors. Use dry_run to preview changes on a copy without altering the original.

Instructions

Make a deck look designed: the kit's theme (optional), then every slide's title and body fonts (Arabic-aware), sizes from a type scale, and colours from a contrast-checked palette. kit = a name from iwork_list_design_kits or your own {"fonts": {...}, "colors": {...}}. Text is verified unchanged. dry_run=true previews the change on a copy without touching the file. Use to restyle a whole deck from a kit. For one text item use keynote_format_text. Preview with dry_run, then run keynote_review_deck.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kit`	No	A design kit: a name from iwork_list_design_kits (preset or saved, e.g. "executive", "Resal") or your own {"fonts": {...}, "colors": {"title": "#RRGGBB", ...}}. Contrast is checked.	executive
`path`	Yes	Path to the .key deck (absolute, or starting with ~).
`dry_run`	No	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.
`set_theme`	No	true = also switch to the kit's theme first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.4.1Oct 4, 2026

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 / kit / description

Added value: +"A design kit: a name from iwork_list_design_kits (preset or saved, e.g. \"executive\", \"Resal\") or your own {\"fonts\": {...}, \"colors\": {\"title\": \"#RRGGBB\", ...}}. Contrast is checked."

addedInput schema / properties / path / description

Added value: +"Path to the .key deck (absolute, or starting with ~)."

addedInput schema / properties / set_theme / description

Added value: +"true = also switch to the kit's theme first."

First observedv2.4.0Oct 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=true, idempotentHint=false), and the description adds real context beyond them: text is verified unchanged, contrast is checked, and dry_run runs on a throwaway copy without touching the file. It does not contradict the destructive annotation (content is preserved, formatting is replaced). It stops short of noting reversibility or backup behaviour, keeping it below 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?

Purpose is front-loaded in the first clause and every sentence carries information (kit format, verification, dry_run semantics, routing). The paragraph is dense and multi-idea, which slightly hurts scannability, but there is no filler.

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 multi-effect mutation tool with an output schema already present, the description covers what changes, how to preview safely, what is preserved, and which sibling to use instead. Nothing an agent needs to call 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 meaning beyond the schema: kit accepts a preset name from iwork_list_design_kits or a user-supplied fonts/colors object, and dry_run is characterized as a copy-based preview to show the user. It adds value but doesn't fully re-document every parameter's constraints.

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 concrete verb and scope ('restyle a whole deck from a kit') and enumerates exactly what gets changed: theme, title/body fonts, sizes, colours. It explicitly distinguishes itself from the sibling keynote_format_text ('For one text item use...'), so an 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 ('restyle a whole deck'), a named alternative with its own trigger condition ('For one text item use keynote_format_text'), and a workflow prescription ('Preview with dry_run, then run keynote_review_deck'). 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