ChatPPT

Overview Schema Source Related Servers Discussions Admin

slide_create

Create one or multiple slides in a presentation deck by passing an array of slide definitions, enabling batch slide creation with titles and optional speaker notes.

Instructions

Create one or multiple new slides in a presentation deck. Pass an array of slide definitions for vectorized batch creation.

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": {
      "deckId": "<deckId>",
      "slides": "<slides>"
    },
    "name": "slide_create"
  }
}

Input Schema

Name	Required	Description	Default
`deckId`	Yes	Stable ID of the presentation deck
`slides`	Yes	Array of slide definitions to create in batch

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden and falls short. It discloses batch/vectorized creation, which is a meaningful trait, but says nothing about where new slides are placed in the deck, what permissions are required, whether the operation is atomic on partial failure, or what the response contains.

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 tight sentences with the core action front-loaded and the batch pattern second. Nothing is redundant or padded, and the reader reaches the essential behavior immediately.

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?

For a two-parameter mutation tool with no output schema and no annotations, the description is minimally adequate. It never states what happens on success (returned IDs, order of created slides) or failure behavior for a batch, which an agent needs in order to chain a follow-up call.

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 deckId and slides (including nested notes and title) are already documented in the schema; the 3 baseline applies. The description reinforces that slides is an array for batch creation but adds no constraints, ordering semantics, or per-item meaning beyond the schema.

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: 'Create one or multiple new slides in a presentation deck.' This clearly distinguishes creation from siblings like slide_update or slide_duplicate, though it never names an alternative. The batch capability is stated up front, so an agent knows it is a writer, not a reader.

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 gives no when-to-use conditions, no prerequisites (e.g. that deckId must reference an existing deck), and no guidance on choosing between this and slide_duplicate or element_create. 'Pass an array' describes the mechanics of calling, not the circumstances that select this tool.

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