ChatPPT

by ParkerDiamond

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

element_delete

Destructive

Permanently delete multiple elements from a specific slide in one batch by supplying deck, slide, and element IDs.

Instructions

Permanently delete one or more elements from a slide in batch.

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>",
      "slideId": "<slideId>",
      "elementIds": "<elementIds>"
    },
    "name": "element_delete"
  }
}

Input Schema

Name	Required	Description
`deckId`	Yes	Stable ID of the presentation deck
`slideId`	Yes	Stable ID of the slide
`elementIds`	Yes	Array of element IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare destructiveHint=true, so the description is not the only source of the danger signal. It does add real value by stating "Permanently" (irreversibility, no undo) and by disclosing that deletion is batched, but it omits partial-failure behavior, whether deletion cascades to child elements, and permission requirements.

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?

A single twelve-word sentence with zero filler, and the critical word "Permanently" plus the resource appear immediately. Nothing could be removed without losing information.

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 simple three-required-parameter mutation with full schema coverage, no output schema, and a destructiveHint annotation, the description covers the essentials but leaves open what is returned, whether a partial batch succeeds, and whether deleted IDs remain referenceable. Those matter for a batch destructive 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 all three parameters are documented in the schema itself and the baseline is 3. The phrase "one or more elements" loosely mirrors the minItems=1/maxItems=100 bounds but adds no format, ordering, or ID-provenance detail 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+resource ("delete ... elements"), the container ("from a slide"), and the batch scope, which distinguishes it from slide_delete and deck_delete siblings by naming the element grain. It does not explicitly name the sibling alternatives, so it stops short of a 5.

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 or when-not-to-use guidance and never points to element_update or element_reorder as the non-destructive alternatives. An agent must infer from the verb alone that this is the removal path rather than a move or update.

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