Skip to main content
Glama
Sign In
keynote-mcp

keynote-mcp

by ByAxe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_text_box

Add a text box to a specific slide in Keynote presentations. Specify slide number, text content, position, and formatting options to insert custom text elements.

Instructions

Add a text box to 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>",
      "text": "<text>"
    },
    "name": "add_text_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_numberYesSlide number
textYesText content
xNoX coordinate in pixels (optional). Origin (0,0) is top-left. Suggested: 50-950px
yNoY coordinate in pixels (optional). Origin (0,0) is top-left. Suggested: 50-650px
font_sizeNoFont size (optional)
font_nameNoFont name (optional)
colorNoText color as 'r,g,b' with values 0-65535 (optional, e.g. '65535,65535,65535' for white)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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 for behavioral disclosure. 'Add' implies a write/mutation operation, but the description doesn't cover critical aspects like whether this requires specific permissions, if it modifies an existing slide permanently, what happens on failure, or typical response behavior. For a mutation tool with zero annotation coverage, this is a significant gap.

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 that front-loads the core purpose without any wasted words. It's appropriately sized for a straightforward tool, making it easy to parse quickly.

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 (a mutation tool with 7 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral traits, error conditions, or return values, leaving the agent with insufficient context for reliable invocation beyond basic parameter passing.

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%, with all parameters well-documented in the schema itself (e.g., coordinates, color format). The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting but doesn't compensate with additional context.

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 ('text box to a slide'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other content-adding siblings like add_bullet_list or add_shape, which would require specifying what makes a text box unique (e.g., editable text container vs. other elements).

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an open presentation), exclusions, or comparisons with similar tools like add_title or add_subtitle that might also involve text. This leaves the agent to infer usage from context alone.

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