Skip to main content
Glama

keynote_list_presentations

List all currently open Keynote presentations with their index, name, slide count, and file path.

Instructions

List all currently open Keynote presentations. Returns index, name, slide count, and file path for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • JXA handler for 'list_presentations' operation: iterates open Keynote documents and returns index, name, slideCount, modified, and filePath for each.
    case 'list_presentations': {
      var count = safeCall(function() { return app.documents.length; }, 0);
      var result = [];
      for (var i = 0; i < count; i++) {
        var d = app.documents[i];
        result.push({
          index: i,
          name:       safeCall(function() { return d.name(); }, 'Untitled'),
          slideCount: safeCall(function() { return d.slides.length; }, 0),
          modified:   safeCall(function() { return d.modified(); }, false),
          filePath:   safeCall(function() { return d.file.posixPath(); }, '')
        });
      }
      return result;
    }
  • src/index.ts:90-93 (registration)
    MCP handler routing: case 'keynote_list_presentations' calls bridge.execute('list_presentations', {}) and returns JSON result.
    case 'keynote_list_presentations': {
      const result = await bridge.execute('list_presentations', {});
      return jsonResult(result);
    }
  • Tool definition with name 'keynote_list_presentations', description, and empty inputSchema (no params required).
    {
      name: 'keynote_list_presentations',
      description: 'List all currently open Keynote presentations. Returns index, name, slide count, and file path for each.',
      inputSchema: { type: 'object', properties: {}, additionalProperties: false },
    },
  • KeynoteBridge.execute() method that spawns osascript with KEYNOTE_OPERATION='list_presentations' and parses the JXA envelope result.
        throw new Error(`'${field}' values must be numbers`);
      }
      return [r, g, b];
    }
    
    function optionalColor(value: unknown): [number, number, number] | undefined {
      if (!value) return undefined;
      if (!Array.isArray(value) || value.length !== 3) return undefined;
      return value as [number, number, number];
    }
    
    // ── Server ────────────────────────────────────────────────────────────────────
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states it lists all open presentations, implying a read operation, but does not disclose behavior on empty state, performance, or any side effects. Adequate but minimal.

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 sentence with 13 words, front-loaded with the action, and no superfluous content. It earns its place.

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

Completeness4/5

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

For a tool with no parameters and no output schema, the description is largely complete: it states what it does and what it returns. It could mention edge cases (e.g., no open presentations) but is otherwise sufficient.

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?

There are no parameters. Schema coverage is 100% by default. The description adds no parameter info because none exist, which is acceptable per the baseline of 4 for zero parameters.

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 the verb 'list', the resource 'currently open Keynote presentations', and the returned fields (index, name, slide count, file path). It is specific and distinguishes itself from sibling tools that perform other actions.

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

Usage Guidelines3/5

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

The description implies usage when the agent needs to know open presentations, but provides no explicit guidance on when to use alternatives. No exclusions or context for when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tszaks/keynote-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server