Skip to main content
Glama
ZatesloFL

Google Workspace MCP Server

by ZatesloFL

create_presentation

Generate a new Google Slides presentation by specifying a title and user email. Returns presentation details including ID and URL for easy access and sharing.

Instructions

Create a new Google Slides presentation.

Args: user_google_email (str): The user's Google email address. Required. title (str): The title for the new presentation. Defaults to "Untitled Presentation".

Returns: str: Details about the created presentation including ID and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoUntitled Presentation
user_google_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @server.tool() that implements the create_presentation MCP tool. It creates a new Google Slides presentation via the API, using the provided title, and returns a formatted confirmation message with the new presentation's ID and URL.
    @server.tool()
    @handle_http_errors("create_presentation", service_type="slides")
    @require_google_service("slides", "slides")
    async def create_presentation(
        service,
        user_google_email: str,
        title: str = "Untitled Presentation"
    ) -> str:
        """
        Create a new Google Slides presentation.
    
        Args:
            user_google_email (str): The user's Google email address. Required.
            title (str): The title for the new presentation. Defaults to "Untitled Presentation".
    
        Returns:
            str: Details about the created presentation including ID and URL.
        """
        logger.info(f"[create_presentation] Invoked. Email: '{user_google_email}', Title: '{title}'")
    
        body = {
            'title': title
        }
    
        result = await asyncio.to_thread(
            service.presentations().create(body=body).execute
        )
    
        presentation_id = result.get('presentationId')
        presentation_url = f"https://docs.google.com/presentation/d/{presentation_id}/edit"
    
        confirmation_message = f"""Presentation Created Successfully for {user_google_email}:
    - Title: {title}
    - Presentation ID: {presentation_id}
    - URL: {presentation_url}
    - Slides: {len(result.get('slides', []))} slide(s) created"""
    
        logger.info(f"Presentation created successfully for {user_google_email}")
        return confirmation_message
  • The @server.tool() decorator registers the create_presentation function as an MCP tool.
    @server.tool()
  • The function signature defines the input schema: user_google_email (required str), title (optional str, default 'Untitled Presentation'), and returns str.
    async def create_presentation(
        service,
        user_google_email: str,
        title: str = "Untitled Presentation"
    ) -> str:
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It states this is a creation operation but doesn't mention permissions needed (beyond the email parameter), rate limits, whether this requires authentication, or what happens on failure. The return format is mentioned but lacks detail about error conditions or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence serves a purpose, though the 'Returns' section could be more specific about what 'Details' includes. The formatting helps readability but isn't perfectly front-loaded.

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 creation tool with no annotations, 2 parameters, and an output schema, the description is minimally adequate. It covers the basic purpose and parameters but lacks important context about authentication, error handling, and when to choose this over other creation tools. The presence of an output schema reduces the need to describe return values in detail.

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?

With 0% schema description coverage, the description compensates well by explaining both parameters: user_google_email is described as 'The user's Google email address. Required.' and title as 'The title for the new presentation. Defaults to "Untitled Presentation".' This adds meaningful context beyond the bare schema, though it doesn't explain format constraints or validation rules.

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 specific action ('Create a new Google Slides presentation') and resource ('presentation'), distinguishing it from sibling tools like create_doc or create_spreadsheet. It uses precise language that leaves no ambiguity about what the tool does.

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?

No guidance is provided on when to use this tool versus alternatives like create_doc or create_spreadsheet. The description doesn't mention prerequisites, use cases, or any context that would help an agent decide between this and other creation tools in the sibling list.

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/ZatesloFL/google_workspace_mcp'

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