Skip to main content
Glama

get_presentation_info

Retrieve detailed information about a Google Slides presentation using its unique ID to access presentation content and structure.

Instructions

Get information about a Google Slides presentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentationIdYesThe ID of the Google Slides presentation

Implementation Reference

  • The main handler function for the 'get_presentation_info' tool. It calls the slidesService to get the presentation details and formats a text response with title, slide count, and page size.
    private async handleGetPresentationInfo(args: {
      presentationId: string;
    }): Promise<CallToolResult> {
      const info = await this.slidesService.getPresentationInfo(args.presentationId);
    
      return {
        content: [
          {
            type: 'text',
            text: `Presentation: ${info.title}\nSlide count: ${info.slideCount}\nPage size: ${info.pageSize.width.magnitude} x ${info.pageSize.height.magnitude} ${info.pageSize.width.unit}`,
          },
        ],
      };
    }
  • src/index.ts:110-123 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema for 'get_presentation_info'.
    {
      name: 'get_presentation_info',
      description: 'Get information about a Google Slides presentation',
      inputSchema: {
        type: 'object',
        properties: {
          presentationId: {
            type: 'string',
            description: 'The ID of the Google Slides presentation',
          },
        },
        required: ['presentationId'],
      },
    },
  • Input schema for the 'get_presentation_info' tool, specifying the required 'presentationId' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        presentationId: {
          type: 'string',
          description: 'The ID of the Google Slides presentation',
        },
      },
      required: ['presentationId'],
    },
  • Supporting utility method in GoogleSlidesService that interacts with the Google Slides API to retrieve presentation information including title, slide count, and page size.
    async getPresentationInfo(presentationId: string) {
      await this.auth.refreshTokenIfNeeded();
      const slides = this.auth.getSlidesClient();
    
      try {
        const response = await slides.presentations.get({
          presentationId
        });
    
        return {
          title: response.data.title,
          slideCount: response.data.slides?.length || 0,
          pageSize: response.data.pageSize
        };
      } catch (error) {
        console.error('Error getting presentation info:', error);
        throw new Error(`Failed to get presentation info: ${error}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get information'), but doesn't specify whether it requires authentication, what permissions are needed, whether there are rate limits, what format the information comes in, or if there are any side effects. The description is minimal and leaves critical behavioral aspects unspecified.

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 wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately. Every word earns its place in this concise formulation.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned (metadata, slide count, permissions, etc.), doesn't mention authentication requirements despite sibling tools including authentication-related tools, and provides no behavioral context. The agent would be left guessing about critical aspects of tool usage.

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 the single 'presentationId' parameter adequately. The description doesn't add any additional meaning about the parameter beyond what's in the schema (it doesn't explain where to find presentation IDs, format requirements, or examples). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Get information') and resource ('Google Slides presentation'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'list_slides' or specify what type of information is retrieved (metadata, content, structure, etc.).

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 (like needing authentication first), when this tool is appropriate versus 'list_slides' for browsing presentations, or any limitations on what presentations can be accessed.

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