Skip to main content
Glama

export_presentation

Export a finished presentation to PDF, PowerPoint, or a shareable link for delivery.

Instructions

Export a finished presentation to PDF, PowerPoint, or a shareable link. Use this after generation or editing when you need a deliverable artifact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYesPresentation to export.
formatsYesOne or more export formats to generate.

Implementation Reference

  • src/index.js:298-321 (registration)
    Registration of the 'export_presentation' tool via server.registerTool with its description and input schema.
    server.registerTool(
      "export_presentation",
      {
        description:
          "Export a finished presentation to PDF, PowerPoint, or a shareable link. Use this after generation or editing when you need a deliverable artifact.",
        inputSchema: {
          presentation_id: z
            .string()
            .min(1)
            .describe("Presentation to export."),
          formats: z
            .array(z.enum(["pdf", "ppt", "link"]))
            .min(1)
            .describe("One or more export formats to generate."),
        },
      },
      async (args) => {
        try {
          return await callRemoteTool("export_presentation", args);
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Input schema for 'export_presentation': requires presentation_id (string) and formats (array of 'pdf', 'ppt', 'link').
    {
      description:
        "Export a finished presentation to PDF, PowerPoint, or a shareable link. Use this after generation or editing when you need a deliverable artifact.",
      inputSchema: {
        presentation_id: z
          .string()
          .min(1)
          .describe("Presentation to export."),
        formats: z
          .array(z.enum(["pdf", "ppt", "link"]))
          .min(1)
          .describe("One or more export formats to generate."),
      },
    },
  • Handler function that calls callRemoteTool('export_presentation', args) and normalizes any errors.
      async (args) => {
        try {
          return await callRemoteTool("export_presentation", args);
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • The callRemoteTool helper function that connects to the remote MCP endpoint, invokes the tool by name, and returns the result.
    async function callRemoteTool(name, args) {
      const client = new Client(
        { name: "alai-mcp-wrapper", version: "1.0.2" },
        { capabilities: {} },
      );
      const transport = new StreamableHTTPClientTransport(new URL(REMOTE_MCP_URL), {
        requestInit: {
          headers: createRemoteHeaders(),
        },
      });
    
      try {
        await client.connect(transport);
        return await client.callTool({
          name,
          arguments: args,
        });
      } finally {
        await transport.close().catch(() => {});
        await client.close().catch(() => {});
      }
    }
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for transparency. It does not disclose whether the original presentation is modified, what permissions are required, rate limits, or behavior if the presentation is not finished. This is a significant gap for a tool that produces external artifacts.

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 consists of two concise sentences that front-load the action and outputs, then provide usage context. No unnecessary words.

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 2-parameter tool with no output schema, the description covers the basic purpose and usage context. However, it is incomplete regarding return values or side effects, which would be helpful for an 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%, and the description adds minimal extra meaning beyond the schema. It reiterates the formats but does not elaborate on parameter syntax or constraints. Baseline of 3 is appropriate.

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 tool exports a presentation to specific formats (PDF, PowerPoint, link), using a specific verb and resource. It distinguishes from sibling tools like create_slide or delete_presentation by focusing on the export action.

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 advises using the tool 'after generation or editing when you need a deliverable artifact,' providing clear usage context. However, it does not explicitly state when not to use it or mention alternatives, though none exist among siblings.

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/getalai/alai-mcp-server'

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