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

office-powerpoint-mcp-server

Update Table Cells

update_table_cells

Modify specific cells in an existing PowerPoint table by setting text, font size, bold/italic, text color, background shading, and alignment.

Instructions

Update specific cells in an existing PowerPoint table.

Allows modifying cell text, font size, bold/italic, text color, background shading, and text alignment.

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>",
      "shape_index": "<shape_index>",
      "updates": "<updates>"
    },
    "name": "update_table_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesList of cell update specifications (row, col, text, colors, font)
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
shape_indexYes0-based shape index of the table
slide_indexYes0-based index of slide containing the table
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
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds only a list of editable fields that the schema already documents; it never explains partial-update semantics (null fields presumably leave styling untouched), that existing cell text is overwritten, or how auto_save interacts with file_path.

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?

Two short sentences with the operation stated first, no filler and no repetition of boilerplate. The second sentence largely mirrors the schema's field list, so it is not entirely load-bearing, but the definition is well within an appropriate size.

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 exists, so return values need not be explained, and annotations cover the mutation profile. However, for a 6-parameter batch-mutation tool the description omits the non-obvious invocation concerns: whether unspecified style fields are preserved, what happens when file_path and presentation_id are both omitted, and what auto_save writes to disk.

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 including the nested update fields is already documented in the schema; the baseline of 3 applies. The description's field list adds no syntax, ordering, or defaulting information beyond it, and does not clarify the file_path vs presentation_id targeting choice.

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+resource: 'Update specific cells in an existing PowerPoint table', and enumerates the mutable attributes (text, font size, bold/italic, colors, alignment). It is clearly a mutation of an existing table rather than a creation tool like add_data_table, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'existing' implies the table must already be present, which is useful implied guidance, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives. Nothing tells the agent when to prefer this over manage_shapes or add_data_table.

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