keynote-mcp

Overview Schema Source Related Servers Discussions Admin

edit_text_item

Modify text content on specific slides in Keynote presentations by specifying slide number, text item index, and new text.

Instructions

Edit a text item's content by index on a slide

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slide_number": "<slide_number>",
      "item_index": "<item_index>",
      "new_text": "<new_text>"
    },
    "name": "edit_text_item"
  }
}

Input Schema

Name	Required	Description
`slide_number`	Yes	Slide number
`item_index`	Yes	Text item index (1-based)
`new_text`	Yes	New text content
`doc_name`	No	Document name (optional, defaults to front document)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Edit'), but doesn't disclose behavioral traits such as whether changes are saved automatically, if it requires specific permissions, what happens on invalid indices, or error handling. The description is minimal and lacks crucial operational context for a write operation.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy or fluff.

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

Completeness2/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, leaving significant gaps for an AI agent to understand how to use it correctly in context.

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 schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema, such as explaining 'item_index' as 1-based (already in schema) or interactions between parameters. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Edit') and resource ('text item's content'), specifying it operates 'on a slide'. It distinguishes from siblings like 'add_text_box' or 'delete_element' by focusing on modifying existing text items. However, it doesn't explicitly contrast with tools like 'move_element' or 'resize_element' that might also affect text items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this should be used instead of 'delete_element' followed by 'add_text_box', or clarify prerequisites like needing an open presentation. The description only states what it does, not when it's appropriate.

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