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. 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 &…

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

NameRequiredDescriptionDefault
kitNoA design kit: a name from iwork_list_design_kits (preset or saved, e.g. "executive", "Acme") 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.1
    • changedInput schema / properties / kit / description
      Previous 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."New value: +"A design kit: a name from iwork_list_design_kits (preset or saved, e.g. \"executive\", \"Acme\") or your own {\"fonts\": {...}, \"colors\": {\"title\": \"#RRGGBB\", ...}}. Contrast is checked."
  2. 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\"."
  3. First observedv2.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description adds what the annotations cannot: every slide is read back and verified, mismatches cause removal of the new file, the target path must not already exist ('Never overwrites'), and it requires macOS + Keynote. This is the behavioral context an agent needs before a destructive write.

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 tightly compressed with inline schemas, so every clause carries load. It is nonetheless a very dense single block, and the chart/table/kit material could be structured more scannably rather than run together.

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 complex, destructive creation tool it covers the environment prerequisite, non-overwrite guarantee, verification/rollback behavior, payload structure for all three slide kinds, and the recommended follow-up tool. With an output schema present it need not explain return values, and nothing essential 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?

Even at 100% schema coverage, the description adds semantics the schema defers to it for: slide object shape (title/body/layout/notes/image), default layouts (first slide title layout, rest Title & Bullets), chart and table sub-schemas with their defaults, and kit vs theme interaction. Substantively more than the schema provides.

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?

Opens with a specific verb+resource: 'Build a new Keynote deck from an outline,' and names the scope (new deck creation). It explicitly distinguishes itself from sibling slide/text editing tools in the closing sentence, so an agent can route correctly without opening schemas.

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?

States when to use it ('Use for a new deck from an outline, including chart and table slides'), the follow-up step ('then run keynote_review_deck'), and the exclusion ('To change an existing deck use the slide and text tools instead'). Alternatives and boundaries are 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