Skip to main content
Glama
office-powerpoint-mcp-server

office-powerpoint-mcp-server

Add Bullet Slide

add_bullet_slide

Insert a styled bullet slide with title, optional subtitle, and hierarchical bullet points into a PowerPoint presentation, with theme selection and slide positioning options.

Instructions

Quickly add an institutional structured bullet slide with header and divider.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "bullet_points": "<bullet_points>"
    },
    "name": "add_bullet_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoColor scheme to use for typography and accentsinstitutional_navy
titleYesSlide headline title
subtitleNoOptional contextual subtitle under the header
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
slide_indexNoPosition index to insert slide at (appends to end if None)
bullet_pointsYesList of strings or structured BulletItem with levels and formatting
presentation_idNoIn-memory presentation ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a small amount of structural context (a fixed header and divider layout are generated), but it says nothing about the file_path versus presentation_id target modes, auto-save side effects, or insertion-position behavior.

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?

A single front-loaded sentence with no filler. It is efficient, though the adjective 'institutional' is doing double duty and slightly blurs the meaning of the sentence.

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?

An output schema and full annotation/schema documentation carry most of the weight, so the description need not explain return values. However, for an eight-parameter mutation tool, it omits the meaningful choice between writing to file_path and an in-memory presentation_id, which is exactly the kind of context a description should surface.

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 all eight parameters including theme, slide_index, auto_save, and the nested bullet formatting are fully documented in the schema. The description adds essentially no parameter meaning beyond that, so baseline 3 applies; 'institutional' faintly echoes the default institutional_navy theme.

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?

States a specific verb and resource ('add an ... bullet slide with header and divider'), which is more precise than the bare tool name and implies a pre-formatted layout rather than a generic template slide. It does not explicitly contrast itself with the sibling add_slide_from_template, so an agent must infer the distinction.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as add_slide_from_template or manage_slides. The word 'Quickly' hints at a convenience path but never states a condition that selects this tool over its siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.