Skip to main content
Glama

pptx_read_slide

Extract slide title, layout, and shape details from a PowerPoint file by specifying the file path and slide index.

Instructions

Return the slide's title, layout, and shape list.

Args: path: Path to an existing .pptx. index: 0-based slide index. folder: Optional base folder for relative paths.

Returns: {"index": <int>, "layout": <str>, "title": <str>, "shapes": [<shape_dict>, ...]}.

Each ``shape_dict`` has ``type`` (shape class name),
``shape_type`` (the numeric ``MSO_SHAPE_TYPE`` or ``None``),
``name`` (auto-generated name), and ``text`` (text-frame
text, or ``""`` for shape types without text).

Raises: OfficeMCPError: ERR_INVALID_PARAMS for a non-int or out-of-range index, ERR_FILE_NOT_FOUND if the file is missing, ERR_UNSUPPORTED_FMT for non-.pptx extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
indexYes
folderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It explains the return format and error conditions (ERR_INVALID_PARAMS, ERR_FILE_NOT_FOUND, ERR_UNSUPPORTED_FMT) but does not disclose whether the tool is read-only or any potential side effects. The safety profile is not explicitly mentioned, which is a gap.

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 well-structured with a one-line summary followed by Args, Returns, and Raises sections. It is front-loaded with the main purpose and provides essential details without unnecessary verbosity. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, output schema present, no nested objects), the description is complete. It thoroughly covers parameter semantics, return value structure (including shape_dict details), and error cases. No additional information is needed for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully with an 'Args' section that explains each parameter: 'path' as path to existing pptx, 'index' as 0-based slide index, and 'folder' as optional base folder for relative paths. This adds significant meaning beyond the schema's type and title.

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 ('Return the slide's title, layout, and shape list') and the resource (a slide within a pptx file). It is specific and distinguishes this read operation from sibling pptx tools that modify or create slides.

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 description implies usage for reading slide details but does not explicitly state when to use this tool versus alternatives like pptx_list_slides or pptx_get_info. No exclusions or guidance on when not to use it are provided.

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/gawirable/office-mcp'

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