Skip to main content
Glama

create_slide

Add a slide to an existing presentation using a text prompt, with options for classic content or creative visual layouts.

Instructions

Add a new slide to an existing presentation. Use this for targeted edits after a deck already exists, including classic content slides or more creative visually led slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYesTarget presentation that will receive the new slide.
promptYesInstruction describing the content or intent of the new slide.
slide_typeNoChoose classic for structured content or creative for more visual exploration.
insert_after_slide_idNoExisting slide identifier after which the new slide should be inserted.
theme_idNoOptional theme override for the new slide.
vibe_idNoOptional vibe override for the new slide.

Implementation Reference

  • src/index.js:232-271 (registration)
    Registration of the 'create_slide' tool with the MCP server, including description and input schema using Zod validation.
    server.registerTool(
      "create_slide",
      {
        description:
          "Add a new slide to an existing presentation. Use this for targeted edits after a deck already exists, including classic content slides or more creative visually led slides.",
        inputSchema: {
          presentation_id: z
            .string()
            .min(1)
            .describe("Target presentation that will receive the new slide."),
          prompt: z
            .string()
            .min(1)
            .describe("Instruction describing the content or intent of the new slide."),
          slide_type: z
            .enum(["classic", "creative"])
            .optional()
            .describe("Choose classic for structured content or creative for more visual exploration."),
          insert_after_slide_id: z
            .string()
            .optional()
            .describe("Existing slide identifier after which the new slide should be inserted."),
          theme_id: z
            .string()
            .optional()
            .describe("Optional theme override for the new slide."),
          vibe_id: z
            .string()
            .optional()
            .describe("Optional vibe override for the new slide."),
        },
      },
      async (args) => {
        try {
          return await callRemoteTool("create_slide", args);
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Input schema for the create_slide tool, defining presentation_id, prompt, slide_type, insert_after_slide_id, theme_id, and vibe_id with Zod validations.
    inputSchema: {
      presentation_id: z
        .string()
        .min(1)
        .describe("Target presentation that will receive the new slide."),
      prompt: z
        .string()
        .min(1)
        .describe("Instruction describing the content or intent of the new slide."),
      slide_type: z
        .enum(["classic", "creative"])
        .optional()
        .describe("Choose classic for structured content or creative for more visual exploration."),
      insert_after_slide_id: z
        .string()
        .optional()
        .describe("Existing slide identifier after which the new slide should be inserted."),
      theme_id: z
        .string()
        .optional()
        .describe("Optional theme override for the new slide."),
      vibe_id: z
        .string()
        .optional()
        .describe("Optional vibe override for the new slide."),
    },
  • Handler function for create_slide that proxies the call to the remote Alai MCP endpoint via callRemoteTool.
    async (args) => {
      try {
        return await callRemoteTool("create_slide", args);
      } catch (error) {
        return normalizeError(error);
      }
    },
  • Generic helper function callRemoteTool that creates a temporary MCP client, connects to the remote Alai server, and calls the named tool with the provided arguments.
    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(() => {});
      }
    }
Behavior3/5

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

No annotations are provided, so the description must bear the full burden. It discloses the mutation (adding a slide) and mentions slide types, but lacks details on side effects, authentication, rate limits, or error behavior. Adequate but not rich.

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 concise with two clear sentences. It front-loads the main purpose and follows with usage context. No unnecessary words.

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?

Given 6 parameters with full schema descriptions and no output schema, the description provides adequate context for a creation tool. It mentions slide types and targeted edits, which is sufficient for most use cases.

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?

The schema covers all 6 parameters with descriptions (100% coverage). The description adds minimal extra meaning beyond the schema, such as explaining 'classic' vs 'creative' slide types. Baseline 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 action (Add a new slide), the target resource (existing presentation), and distinguishes from siblings like generate_presentation (creates whole deck) and delete_slide (removes). The scope is well-defined.

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 explicitly mentions using this for targeted edits after a deck already exists, which provides clear context. It does not explicitly state when not to use it or list alternatives, but the sibling tool names imply other use cases.

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