keynote-mcp

by ByAxe

Overview Schema Source Related Servers Discussions Admin

Python

Local

add_slide

Insert a new slide into a Keynote presentation, specifying layout and position to organize content effectively.

Instructions

Add a new slide to the presentation

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_slide"
  }
}

Input Schema

Name	Required	Description
`doc_name`	No	Document name (optional, defaults to front document)
`position`	No	Insert position (optional, 0 = append at end)
`layout`	No	Layout type (optional)

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?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether this requires write permissions, if it modifies the presentation in real-time, what happens on errors, or if there are rate limits. This leaves significant gaps for a mutation tool.

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, front-loaded sentence that directly states the tool's function without any wasted words. It's appropriately sized for a simple tool and earns its place efficiently.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., slide ID, success status), error conditions, or dependencies like needing an open presentation, which are critical for effective use.

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?

The schema description coverage is 100%, so the schema already documents all three parameters (doc_name, position, layout) with their types and optional status. The description adds no additional meaning beyond what's in the schema, such as examples or constraints, meeting the baseline for high coverage.

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 ('Add') and resource ('new slide to the presentation'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'duplicate_slide' or 'set_slide_layout', which could also involve slide creation or modification, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an open presentation), exclusions, or comparisons to tools like 'create_presentation' for initial setup or 'duplicate_slide' for copying existing slides.

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