Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: duplicate slide

keynote_duplicate_slide
Destructive

Duplicate a specified Keynote slide, placing the copy right after the original. Use dry_run to preview the change on a copy without touching the file.

Instructions

Duplicate slide number slide (1-based); the copy lands right after it. dry_run=true previews the change on a copy without touching the file. Use to copy an existing slide (layout and content). For a blank slide use keynote_add_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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the mutating/non-idempotent profile is covered. The description adds the useful copy-placement behavior, but says nothing about permissions, what happens on an out-of-range slide number, or reversibility/undo. Adequate but not rich beyond what the annotations carry.

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?

Two tight sentences, front-loaded with the core effect and immediate placement, followed by the dry_run caveat and the sibling redirect. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and an output schema covering return values, the description need only explain the operation, placement, and sibling routing — all present. Minor gap: no guidance on invalid slide numbers or the effect of duplicating a skipped/hidden slide.

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 coverage is 100%, so path, slide (1-based), and dry_run semantics are all documented in the schema already; the description only restates the 1-based numbering and the dry_run preview. Baseline 3 applies when the schema does the heavy lifting.

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 ('duplicate slide number `slide`') plus the exact effect ('the copy lands right after it'), and explicitly names the sibling it is not for ('For a blank slide use keynote_add_slide'). An agent can distinguish it from keynote_add_slide and keynote_move_slide 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?

Gives explicit when-to-use ('Use to copy an existing slide (layout and content)') and a named alternative with its selecting condition ('For a blank slide use keynote_add_slide'). It also advises the dry_run-first workflow, leaving nothing to inference.

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