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 table to a slide (1-based). rows = [["Region", "Q1"], ["Riyadh", 1200], …]: text, numbers, or null; text starting with "=" is a formula.

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

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", "Acme") 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

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. 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)."
  3. 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 declare the safety profile (destructive, non-idempotent), and the description layers on real behavioral context beyond them: the 50×15 row/column cap, macOS+Keynote platform requirement, verification that every cell/font/colour is read back and other slides/tables are checked untouched, and precise dry_run semantics ('on a copy without touching the file'). That is exactly the kind of non-obvious operational detail annotations cannot carry.

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-loads the core verb and the tricky 'rows' format first, then constraints, then sibling routing. Dense and information-rich, but the inline rows-format restatement duplicates the schema's own description of the same parameter, costing a little efficiency.

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?

Given an output schema exists, the description need not explain return values, yet it proactively notes the read-back verification and untouched-check behavior. Limits, platform prerequisite, dry_run escape hatch, and sibling routing are all covered, so an agent has everything required to call it correctly and safely.

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. The description still adds meaning beyond the schema for the styling behavior of 'kit' (header band, Arabic-aware fonts, banding, right-aligned numbers) and clarifies x/y are 'points from top-left', which the schema only partially conveys. The rows format is largely duplicated from the schema, keeping this short of a 5.

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 ('Add a table to a slide') with row indexing (1-based) and even clarifies what 'rows' means semantically. It distinguishes itself from siblings by naming keynote_build_deck (new decks) and keynote_add_chart (trends) as the alternatives an agent might confuse it with.

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') plus when-not and routed alternatives ('In a new deck, put it in keynote_build_deck's outline; to show a trend use keynote_add_chart'). The dry_run guidance ('Use it before broad or risky edits') adds a second actionable usage rule.

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