office_docs_mcp

Overview Schema Source Related Servers Discussions Admin

ppt_update_slide_text

Update the text of a specific shape on a PowerPoint slide by providing the file path, slide index, shape index, and new text content.

Instructions

Update the text of a specific shape on a slide in a PowerPoint presentation.

Args:
    file_path: Path to the PowerPoint file.
    slide_idx: 0-based slide index.
    shape_idx: 0-based shape index within the slide.
    text: New text content for the shape.
    backup: If True, create a backup of the original file before modifying.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes
`backup`	No
`file_path`	Yes
`shape_idx`	Yes
`slide_idx`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 27, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the backup parameter behavior but does not state side effects like overwriting existing text, whether the file is saved automatically, what happens if the shape or slide index is invalid, or any return value. For a mutating operation, this is insufficient disclosure.

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, front-loaded sentence stating the purpose, followed by a clean argument list. There is no fluff or redundant information. Every sentence earns its place.

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?

The description covers the core action and parameters but lacks contextual details such as how to obtain the correct indices (e.g., by first reading the slide), error scenarios, or any prerequisite steps. Given the presence of an output schema, return values are presumably covered, but the tool's usage context is not fully fleshed out.

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?

Schema description coverage is 0%, so the description must compensate. It explains every parameter, including that slide_idx and shape_idx are 0-based, and clarifies the backup behavior. This adds meaningful semantic information beyond the bare schema types and titles.

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 action (update text) and the specific resource (a shape on a slide in a PowerPoint file). It is distinct from sibling tools like ppt_read_slide (read-only) and ppt_update_notes (updates notes, not shape text), so an agent can easily tell this tool apart.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that to find the correct shape_idx one might need to call ppt_read_slide first, nor does it exclude cases like updating notes (ppt_update_notes) or other types of content. Usage context is left entirely to inference.

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