Skip to main content
Glama
Sign In
Keynote MCP Server

Keynote MCP Server

by superdwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_slide_transition

Set a transition effect for a Keynote slide. Specify the effect name and duration to control slide changes during presentations.

Instructions

Sets the transition effect for a slide. Common effects: 'none', 'magic move', 'dissolve', 'push', 'reveal', 'cube', 'flip', 'wipe', 'shimmer', 'sparkle'. Use list_transition_types to see all available effects.

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": {
      "slideIndex": "<slideIndex>",
      "effect": "<effect>"
    },
    "name": "set_slide_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
effectYesTransition effect name (e.g. 'dissolve', 'magic move', 'push', 'none')
durationNoTransition duration in seconds (default: 1.0)
slideIndexYes1-based slide index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It lists common effects and points to the schema for parameters, but does not disclose what happens on success/failure, whether the transition replaces existing ones, or error behavior for invalid slideIndex. Some transparency is present, but lacking in depth.

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?

Two sentences with no fluff: first states purpose, second provides examples and a helpful reference. Information is front-loaded and every sentence earns its place.

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

Completeness3/5

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

For a simple tool with 3 parameters and no output schema, the description is moderately complete. It covers purpose and parameter hints but omits behavior details like default duration, error handling, and return value. The schema provides constraints, but the description could add more context for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline of 3. The description adds value by listing common transition effects and referencing list_transition_types, enhancing the 'effect' parameter beyond schema. No extra info for duration or slideIndex, but the schema descriptions are sufficient.

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?

The description clearly states 'Sets the transition effect for a slide', using a specific verb and resource. It distinguishes from siblings like add_build_animation and get_slide_transition by focusing on transitions. The list of common effects and reference to list_transition_types further clarify its purpose.

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

Usage Guidelines4/5

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

The description provides guidance on when to use this tool: to set a transition effect. It suggests using list_transition_types to see all available effects, which is helpful. However, it does not explicitly state when not to use it or mention prerequisites (e.g., slide must exist).

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