Skip to main content
Glama
Sign In
keynote-mcp

keynote-mcp

by ByAxe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_subtitle

Add subtitles to slides in Apple Keynote presentations by specifying slide number, text, and optional positioning or font settings.

Instructions

Add a subtitle 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>",
      "subtitle": "<subtitle>"
    },
    "name": "add_subtitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_numberYesSlide number
subtitleYesSubtitle text
xNoX coordinate in pixels (optional). Suggested for subtitle: 100-200
yNoY coordinate in pixels (optional). Suggested for subtitle: 120-180
font_sizeNoFont size (optional, default 24)
font_nameNoFont name (optional)

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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions adding a subtitle but doesn't clarify if this is a mutation (likely yes), what permissions are needed, whether it overwrites existing subtitles, or what happens on success/failure. This leaves significant gaps for a tool that modifies presentations.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward tool.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, or side effects (e.g., whether it modifies an existing subtitle). Given the complexity of modifying presentations, more context is needed.

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 6 parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples or edge cases), 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 target resource ('subtitle to a slide'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'add_title' or 'add_text_box' that also add text elements to slides, which prevents a perfect 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 like 'add_title' or 'add_text_box', nor does it mention prerequisites such as requiring an open presentation. It simply states what the tool does without context.

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