iWork Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

Keynote: replace text

keynote_replace_text

Destructive

Find and replace text across all slides in a Keynote .key deck. Set dry_run=true to preview changes on a copy before editing the same names, dates, or numbers everywhere.

Instructions

Find/replace text across every slide of a .key deck (literal unless regex=true). Formatting and structure are verified unchanged. dry_run=true previews the change on a copy without touching the file. Use to change the same text everywhere in a deck (names, dates, numbers). To rewrite one slide's title or body use keynote_set_slide_text.

Input Schema

TableJSON Schema

Name	Required	Description
`find`	Yes	Text to find (literal unless regex=true).
`path`	Yes	Path to the .key deck (absolute, or starting with ~).
`regex`	No	true = treat find as a regular expression.
`dry_run`	No	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.
`replace`	Yes	Replacement text.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.4.1Oct 4, 2026

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 / find / description

Added value: +"Text to find (literal unless regex=true)."

addedInput schema / properties / path / description

Added value: +"Path to the .key deck (absolute, or starting with ~)."

addedInput schema / properties / regex / description

Added value: +"true = treat find as a regular expression."

addedInput schema / properties / replace / description
```
Added value: +"Replacement text."
```

First observedv2.4.0Oct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered. The description adds real value beyond them: formatting/structure are verified unchanged, and dry_run previews on a copy without touching the file, which tells the agent how to de-risk a destructive edit.

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 tight sentences, front-loaded with the core behavior and constraint, then the dry-run affordance, then the sibling routing. No 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 not be described. The description covers scope, safety-relevant behavior (verification, dry_run), and sibling differentiation, which is everything an agent needs to invoke this correctly.

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 all five parameters are already documented, including regex and dry_run semantics. The description's 'literal unless regex=true' largely restates the schema, so baseline 3 is appropriate.

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?

Specific verb (find/replace) plus resource and scope ('across every slide of a .key deck'), and it explicitly names the sibling it is not for one-slide edits. An agent can distinguish it from keynote_set_slide_text without opening either 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?

States the exact use case ('change the same text everywhere in a deck (names, dates, numbers)') and routes the alternative case explicitly to keynote_set_slide_text. Both when-to-use and the alternative are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server