Skip to main content
Glama

create_slide

Add a new slide to your Google Slides presentation by specifying the presentation ID and optional position for insertion.

Instructions

Create a new slide in a Google Slides presentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
insertionIndexNoPosition where to insert the slide (optional, defaults to 0)
presentationIdYesThe ID of the Google Slides presentation

Implementation Reference

  • Core handler implementing the create_slide tool logic: creates a new blank slide via Google Slides API batchUpdate.
    async createSlide(presentationId: string, insertionIndex?: number): Promise<SlideInfo> {
      await this.auth.refreshTokenIfNeeded();
      const slides = this.auth.getSlidesClient();
    
      const requests = [{
        createSlide: {
          objectId: `slide_${Date.now()}`,
          insertionIndex: insertionIndex || 0,
          slideLayoutReference: {
            predefinedLayout: 'BLANK'
          }
        }
      }];
    
      try {
        const response = await slides.presentations.batchUpdate({
          presentationId,
          requestBody: {
            requests
          }
        });
    
        const createdSlide = response.data.replies[0].createSlide;
        return {
          slideId: createdSlide.objectId,
          title: 'New Slide'
        };
      } catch (error) {
        console.error('Error creating slide:', error);
        throw new Error(`Failed to create slide: ${error}`);
      }
    }
  • MCP server handler for create_slide tool: delegates to slidesService.createSlide and formats response.
    private async handleCreateSlide(args: {
      presentationId: string;
      insertionIndex?: number;
    }): Promise<CallToolResult> {
      const slideInfo = await this.slidesService.createSlide(
        args.presentationId,
        args.insertionIndex
      );
    
      return {
        content: [
          {
            type: 'text',
            text: `Successfully created new slide with ID: ${slideInfo.slideId}`,
          },
        ],
      };
    }
  • src/index.ts:58-75 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema.
    {
      name: 'create_slide',
      description: 'Create a new slide in a Google Slides presentation',
      inputSchema: {
        type: 'object',
        properties: {
          presentationId: {
            type: 'string',
            description: 'The ID of the Google Slides presentation',
          },
          insertionIndex: {
            type: 'number',
            description: 'Position where to insert the slide (optional, defaults to 0)',
          },
        },
        required: ['presentationId'],
      },
    },
  • Type definition for the return value of createSlide (SlideInfo).
    export interface SlideInfo {
      slideId: string;
      title?: string;
    }
  • Dispatch case in CallToolRequestSchema handler for routing create_slide calls.
    case 'create_slide':
      return await this.handleCreateSlide(args as {
        presentationId: string;
        insertionIndex?: number;
      });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a slide, implying a write operation, but doesn't cover critical aspects like required permissions, whether the action is reversible, rate limits, or what the output looks like (since there's no output schema). This leaves significant gaps for safe and effective use.

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 that directly states the tool's purpose without any wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 of a write operation (creating a slide) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, output format, and usage context, which are essential for an agent to use this tool correctly in a real-world scenario.

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 input schema has 100% description coverage, clearly documenting both parameters (presentationId and insertionIndex). The description adds no additional parameter semantics beyond what the schema provides, such as format details or examples, so it meets the baseline for high schema coverage without compensating value.

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 ('Create a new slide') and resource ('in a Google Slides presentation'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'add_rectangle' or 'list_slides', which might also involve slide manipulation, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a presentation ID), exclusions, or how it relates to sibling tools like 'add_rectangle' or 'list_slides', leaving the agent to infer usage context.

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/vamsikiran353-gif/google-slides-mcp'

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