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

office-powerpoint-mcp-server

Add Image

add_image

Inserts an image into a PowerPoint slide from a local file path or base64 string while preserving aspect ratio within a defined bounding box.

Instructions

Insert an image into a slide from a local file path or base64 string.

Automatically preserves aspect ratio within the specified bounding box (left, top, max_width, max_height).

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": {
      "slide_index": "<slide_index>"
    },
    "name": "add_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoTop coordinate of bounding box in inches
leftNoLeft coordinate of bounding box in inches
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
max_widthNoMaximum allowable width in inches
image_pathNoPath to image file within allowed directory sandbox
max_heightNoMaximum allowable height in inches
slide_indexYes0-based index of slide to place image on
image_base64NoBase64 encoded image string (e.g. from matplotlib or camera)
presentation_idNoIn-memory presentation ID
preserve_aspect_ratioNoWhether to lock aspect ratio and fit cleanly in bounding box

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is already covered. The description adds real behavioral context — aspect ratio is automatically preserved and the image is fitted inside a bounding box — but it does not mention that auto_save writes the presentation to disk by default or what happens if neither image source is provided.

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?

Two short sentences with the core action front-loaded and the fitting behavior as a follow-up. Nothing is redundant or padded.

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 set reduce the burden, but with 11 parameters the description leaves the most consequential rule unstated: one of image_path or image_base64 must be provided. Sandbox restrictions on image paths are also only visible in the schema, so the definition is workable but not complete.

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 every parameter is already documented, which sets the baseline at 3. The description restates the bounding-box semantics (left, top, max_width, max_height) and aspect-ratio fitting but adds no new detail such as coordinate origin or units beyond what the schema already says.

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?

States a specific verb and resource ('Insert an image into a slide') plus the two supported input modes (local file path or base64 string). No sibling tool handles images, so no differentiation is needed, and an agent can tell immediately what this 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?

There is no guidance on when to choose this over alternatives, nor on when to use image_path versus image_base64. The description also omits the practical prerequisite that at least one of those two source parameters must be supplied, which is the main usage decision for this tool.

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