Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: add table

keynote_add_table
Destructive

Add a formatted table to an existing Keynote slide from row data, with optional design-kit styling, positioning, and dry-run preview before changes.

Instructions

Add a table to a slide (1-based). rows = [["Region", "Q1"], ["Riyadh", 1200], …]: text, numbers, or null; text starting with "=" is a formula. kit (iwork_list_design_kits name or your own) styles it: header band, fonts (Arabic-aware), banding, numbers right-aligned. Optional x, y (points from top-left) and width. Every cell, font and colour is read back; other slides and tables are checked untouched. At most 50 rows × 15 columns. dry_run=true previews the change on a copy without touching the file. Needs macOS + Keynote. Use for a table on an existing slide. In a new deck, put it in keynote_build_deck's outline; to show a trend use keynote_add_chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoLeft edge in points (give with y); omit to let Keynote place it.
yNoTop edge in points (give with x).
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.
pathYesPath to the .key deck (absolute, or starting with ~).
rowsYesThe table, header first: [["Region", "Q1"], ["Riyadh", 1200]]; text, numbers or null; "=…" is a formula.
slideYesSlide number, 1-based (keynote_list_slides lists them).
widthNoTable width in points; omit for Keynote's default.
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.
header_rowsNoHow many rows at the top are headers (styled and kept on top).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / header_rows / description
      Added value: +"How many rows at the top are headers (styled and kept on top)."
    • 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 / rows / description
      Added value: +"The table, header first: [[\"Region\", \"Q1\"], [\"Riyadh\", 1200]]; text, numbers or null; \"=…\" is a formula."
    • addedInput schema / properties / slide / description
      Added value: +"Slide number, 1-based (keynote_list_slides lists them)."
    • addedInput schema / properties / width / description
      Added value: +"Table width in points; omit for Keynote's default."
    • addedInput schema / properties / x / description
      Added value: +"Left edge in points (give with y); omit to let Keynote place it."
    • addedInput schema / properties / y / description
      Added value: +"Top edge in points (give with x)."
  2. First observedv2.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructive=true, non-idempotent, closed-world; the description goes well beyond them by disclosing verification behavior ('every cell, font and colour is read back; other slides and tables are checked untouched'), hard limits (50 rows × 15 columns), platform requirements, and dry_run semantics.

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 action and the rows format, and nearly every clause carries load-bearing detail. It is dense and slightly run-on, packing constraints, styling, verification and routing into long sentences, but there is little pure 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?

An output schema exists so return values need no explanation. For a destructive multi-parameter mutation, the description covers safety (dry_run), limits, prerequisites, styling, and alternative tools — everything an agent needs to invoke it 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 the baseline is 3, but the description adds real meaning: rows cell typing (text/numbers/null, '=' prefix means formula), kit styling effects (header band, Arabic-aware fonts, banding, right-aligned numbers), and the pairing constraint on x/y.

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 ('Add a table to a slide') with the indexing convention made explicit (1-based). It routes clearly against siblings by naming keynote_add_chart and keynote_build_deck as the alternatives for different intentions.

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?

Explicit when-to-use ('Use for a table on an existing slide') and when-not ('In a new deck, put it in keynote_build_deck's outline; to show a trend use keynote_add_chart'). Prerequisites (macOS + Keynote) and the dry_run workflow are also spelled out.

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