Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: format text

keynote_format_text
Destructive

Change the font, size, or color of one text item on a Keynote slide by index or matching text, with dry-run preview.

Instructions

Font (PostScript name, e.g. "HelveticaNeue-Bold"), size (pt) and/or colour ("#RRGGBB") of one text item on a slide — pick it by item index (from keynote_inspect_style) or by a unique piece of its text (match). Alignment and shape fill are not scriptable. dry_run=true previews the change on a copy without touching the file. Use for one text item's font, size or colour. To restyle the whole deck consistently use keynote_apply_design.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fontNoPostScript font name, e.g. "HelveticaNeue-Bold".
itemNoText item index on the slide (from keynote_inspect_style); or use match.
pathYesPath to the .key deck (absolute, or starting with ~).
sizeNoFont size in points.
colorNoText colour "#RRGGBB".
matchNoA unique piece of the item's text, to pick it instead of item.
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. Changed8 schema fields changedv2.4.1
    • addedInput schema / properties / color / description
      Added value: +"Text colour \"#RRGGBB\"."
    • 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 / font / description
      Added value: +"PostScript font name, e.g. \"HelveticaNeue-Bold\"."
    • addedInput schema / properties / item / description
      Added value: +"Text item index on the slide (from keynote_inspect_style); or use match."
    • addedInput schema / properties / match / description
      Added value: +"A unique piece of the item's text, to pick it instead of item."
    • addedInput schema / properties / path / description
      Added value: +"Path to the .key deck (absolute, or starting with ~)."
    • addedInput schema / properties / size / description
      Added value: +"Font size in points."
    • addedInput schema / properties / slide / description
      Added value: +"Slide number, 1-based (keynote_list_slides lists them)."
  2. First observedv2.4.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the mutation risk is covered structurally. The description adds that dry_run previews on a copy without touching the file, but that behavior is already fully spelled out in the dry_run schema entry, so the added value beyond structured fields is modest.

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 core action and parameters in the first clause, then terse notes on limits, dry_run, and the sibling alternative. Efficient overall, though the parenthetical e.g. examples make it dense.

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 an output schema present and annotations carrying the safety profile, the description covers the necessary ground for a single-item mutation tool. It names both target-selection methods and the preview escape hatch, leaving no blocking gap.

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 the baseline is 3. The description adds a little meaning by explaining the item-vs-match selection relationship, but otherwise paraphrases the schema's font/colour examples rather than adding new semantics.

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: it sets font/size/colour of one text item on a slide, and immediately scopes it to a single item. It clearly distinguishes itself from keynote_apply_design, which restyles the whole deck, so an agent can route between them without opening schemas.

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?

Explicitly says 'Use for one text item's font, size or colour' and routes whole-deck work to keynote_apply_design. It also names exclusions ('Alignment and shape fill are not scriptable') and gives the safe-preview instruction for dry_run, which is real when-to-use guidance.

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