Skip to main content
Glama
Sign In
keynote-mcp

keynote-mcp

by ByAxe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_element

Reposition slide elements by specifying new X and Y coordinates to adjust text, images, shapes, or tables within Apple Keynote presentations.

Instructions

Move an element to new coordinates 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>",
      "element_type": "<element_type>",
      "element_index": "<element_index>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "move_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_numberYesSlide number
element_typeYesElement type: text, image, shape, or table
element_indexYesElement index (1-based)
xYesNew X coordinate in pixels
yYesNew Y coordinate in pixels
doc_nameNoDocument name (optional, defaults to front document)

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 the full burden. It mentions moving an element but doesn't disclose behavioral traits like whether this is a destructive operation, what permissions are needed, how errors are handled (e.g., invalid coordinates), or what happens on success. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 (a mutation tool with 6 parameters), no annotations, and no output schema, the description is incomplete. It lacks information on behavioral context (e.g., effects, errors), usage prerequisites, and output expectations. For a tool that modifies presentations, this leaves significant gaps for an AI agent.

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 already documents all 6 parameters thoroughly. The description adds no additional meaning beyond implying coordinates are involved. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't need to heavily.

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 ('move') and resource ('an element'), specifying the target location ('to new coordinates on a slide'). It distinguishes from siblings like 'resize_element' (changes size) and 'delete_element' (removes), but doesn't explicitly differentiate from tools like 'edit_text_item' that might also reposition elements. The purpose is specific but could be more distinct.

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. It doesn't mention prerequisites (e.g., needing an open presentation), exclusions (e.g., not for moving slides), or comparisons to siblings like 'resize_element' or 'edit_text_item'. 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.

Deploy Server

Other Tools