Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: build deck

keynote_build_deck
Destructive

Build a new Keynote deck from an outline with slides, charts, tables, and themes. Verifies each slide and removes the file on mismatch, never overwriting.

Instructions

Build a new Keynote deck from an outline. slides = [{"title": "…", "body": ["bullet", "bullet"], "layout": "Title & Bullets", "notes": "…", "image": "/path/pic.png"}, …]; the first slide defaults to a title layout, the rest to Title & Bullets. theme from keynote_list_themes; optional transition for every slide (e.g. dissolve). Every slide is read back and checked; on any mismatch the new file is removed. Never overwrites. kit = a design kit (iwork_list_design_kits) for a designed deck in one call. Chart slides: add "chart": {"type": "bar", "rows": ["2025", "2026"], "columns": ["Q1", "Q2"], "data": [[1, 2], [3, 4]]} or {"type": "line", "from": "/path/report.numbers", "columns": ["Q1", "Q2"]} (header row → column names, first column → row names); chart slides default to Title Only. Table slides: "table": {"rows": [["Region", "Q1"], ["Riyadh", 1200]]} or {"from": "/path/report.numbers", "columns": ["Q1"], "max_rows": 8}; with a kit the table is styled too. Needs macOS + Keynote. Use for a new deck from an outline, including chart and table slides; then run keynote_review_deck. To change an existing deck use the slide and text tools instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kitNoA 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.
pathYesWhere to create the new .key deck; it must not exist yet.
themeNoTheme name from keynote_list_themes; the kit's theme is used when omitted.
slidesYesThe outline: [{"title": "…", "body": ["bullet", …], "notes": "…", "layout": "…", "image": "/path.png", "chart": {…}, "table": {…}}, …]; see the tool description for chart and table.
transitionNoTransition for every slide, e.g. "dissolve".

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 / 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: +"Where to create the new .key deck; it must not exist yet."
    • addedInput schema / properties / slides / description
      Added value: +"The outline: [{\"title\": \"…\", \"body\": [\"bullet\", …], \"notes\": \"…\", \"layout\": \"…\", \"image\": \"/path.png\", \"chart\": {…}, \"table\": {…}}, …]; see the tool description for chart and table."
    • addedInput schema / properties / theme / description
      Added value: +"Theme name from keynote_list_themes; the kit's theme is used when omitted."
    • addedInput schema / properties / transition / description
      Added value: +"Transition for every slide, e.g. \"dissolve\"."
  2. First observedv2.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the verification loop ("every slide is read back and checked"), the rollback behavior ("on any mismatch the new file is removed"), the never-overwrite guarantee, and the macOS+Keynote runtime requirement. This is exactly the context needed for a destructiveHint=true tool.

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 purpose and safety, then examples. It is dense and semicolon-heavy, running a long way before the crucial routing sentence at the end, but almost every clause earns its place.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers safety, prerequisites, layout defaults, chart/table formats, kit usage, and next steps. 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.

Parameters5/5

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

Schema coverage is 100%, but the description supplies the nested chart and table object syntax that the flat schema (additionalProperties: true) leaves undocumented, plus the layout defaults and theme/transition sourcing. This is value the structured fields do not carry.

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 ("Build a new Keynote deck from an outline") and explicitly distinguishes itself from the slide/text mutation siblings, which operate on existing decks. An agent can select it without opening any 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?

Names the follow-up tool (keynote_review_deck), the design-kit sibling (iwork_list_design_kits), the theme source (keynote_list_themes), and the alternative set for editing existing decks. When-to-use and when-not-to-use are both explicit.

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