Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: delete slide

keynote_delete_slide
Destructive

Delete a specific 1-based slide from a Keynote deck. Preview with dry_run, recover via backup; the last slide cannot be deleted.

Instructions

Delete slide number slide (1-based). Recoverable with iwork_restore_backup. dry_run=true previews the change on a copy without touching the file. Use to remove a slide for good (the last slide can't be deleted). To keep it but hide it in the slideshow use keynote_skip_slide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the .key deck (absolute, or starting with ~).
slideYesSlide number, 1-based (keynote_list_slides lists them).
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / path / description
      Added value: +"Path to the .key deck (absolute, or starting with ~)."
    • addedInput schema / properties / slide / description
      Added value: +"Slide number, 1-based (keynote_list_slides lists them)."
  2. First observedv2.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds context annotations cannot express: the deletion is recoverable via iwork_restore_backup, the last slide cannot be deleted, and dry_run works on a throwaway copy 'without touching the file'. These are the concrete consequences and limits an agent needs before mutating a deck.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each load-bearing: the action, the recovery path, the preview mode, and the alternative tool. Nothing is padded and the destructive action plus its guardrail are front-loaded.

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 annotations covering the safety profile, a full schema, and an output schema handling return values, the description only needs to cover constraints and alternatives, which it does completely (recoverability, last-slide limit, dry_run, skip_slide escape hatch).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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

Schema description coverage is 100%, so path, slide, and dry_run are already documented in structured form; the description largely restates what the schema says (1-based numbering, dry_run semantics). Baseline 3 is appropriate since the schema carries the parameter burden.

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?

It names a specific verb and resource ('Delete slide number `slide`') and immediately scopes it with 1-based indexing. It is cleanly distinguished from sibling tools by naming keynote_skip_slide as the non-destructive alternative, so an agent never confuses removal with hiding.

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?

The description gives explicit when-to-use and when-not-to-use guidance: use it 'to remove a slide for good', use keynote_skip_slide 'to keep it but hide it', and use iwork_restore_backup to recover. It also routes to dry_run for risky edits, which is exactly the decision an agent must make before calling.

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