Skip to main content
Glama

add-slide-title-only

Add a title slide to a PowerPoint presentation by specifying the presentation name and slide title.

Instructions

This tool adds a new title slide to the presentation you are working on. The tool doesn't return anything. It requires the presentation_name to work on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_nameYesName of the presentation to add the slide to
titleYesTitle of the slide

Implementation Reference

  • Core handler function that adds a title-only slide to the specified presentation using slide layout 0.
    def add_title_slide(self, presentation_name: str, title: str) -> Slide:
        try:
            prs = self.presentations[presentation_name]
        except KeyError as e:
            raise ValueError(f"Presentation '{presentation_name}' not found")
    
        # Add a slide with title and content
        slide_layout = prs.slide_layouts[self.SLIDE_LAYOUT_TITLE]
        slide = prs.slides.add_slide(slide_layout)
    
        # Set the title
        title_shape = slide.shapes.title
        title_shape.text = title
        return slide
  • Server tool call handler for 'add-slide-title-only' that validates input, delegates to PresentationManager.add_title_slide, and returns confirmation.
    elif name == "add-slide-title-only":
        presentation_name = arguments.get("presentation_name")
        title = arguments.get("title")
    
        if not all([presentation_name, title]):
            raise ValueError("Missing required arguments")
    
        if presentation_name not in presentation_manager.presentations:
            raise ValueError(f"Presentation not found: {presentation_name}")
    
        try:
            slide = presentation_manager.add_title_slide(presentation_name, title)
        except Exception as e:
             raise ValueError(f"Unable to add '{title} to presentation: {presentation_name}. Error: {e}")
    
        return [
            types.TextContent(
                type="text",
                text=f"Added slide '{title}' to presentation: {presentation_name}"
            )
        ]
  • Tool registration in list_tools() including name, description, and input schema definition.
    types.Tool(
        name="add-slide-title-only",
        description="This tool adds a new title slide to the presentation you are working on. The tool doesn't "
                    "return anything. It requires the presentation_name to work on.",
        inputSchema={
            "type": "object",
            "properties": {
                "presentation_name": {
                    "type": "string",
                    "description": "Name of the presentation to add the slide to",
                },
                "title": {
                    "type": "string",
                    "description": "Title of the slide",
                }
            },
            "required": ["presentation_name", "title"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden. It states 'The tool doesn't return anything,' which is useful behavioral info, but lacks details on permissions, side effects (e.g., if it modifies existing slides), or error handling. For a mutation tool with zero annotation coverage, this is inadequate.

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 appropriately sized with two sentences, front-loading the core purpose. However, the second sentence could be more integrated or omitted since schema covers requirements, slightly reducing efficiency.

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 no annotations, no output schema, and a mutation tool, the description is incomplete. It lacks crucial context like what happens on success/failure, how the slide is positioned, or dependencies (e.g., requires an open presentation). More detail is needed for safe agent use.

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 both parameters (presentation_name and title). The description adds minimal value by mentioning presentation_name is required, but doesn't provide additional context like format examples or constraints beyond the schema.

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 ('adds a new title slide') and resource ('to the presentation you are working on'), distinguishing it from siblings like add-slide-comparison or add-slide-title-content by specifying it's title-only. It's not a tautology of the tool name, which lacks context.

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 like add-slide-title-content or add-slide-title-with-chart. It mentions the presentation_name requirement but doesn't help differentiate among similar slide-adding 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/supercurses/powerpoint'

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