ChatPPT

Overview Schema Source Related Servers Discussions Admin

element_list

Read-only

Lists every visual element on a slide in z-index order, so you can inspect layering and identify objects to edit or troubleshoot.

Instructions

List all visual elements on a slide in z-index order.

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>"
    },
    "name": "element_list"
  }
}

Input Schema

Name	Required	Description	Default
`deckId`	Yes	Stable ID of the presentation deck
`slideId`	Yes	Stable ID of the slide

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results come back in z-index (layering) order — but says nothing about pagination, whether hidden/zero-opacity elements are included, or result volume limits.

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 sentence with the resource and the ordering guarantee front-loaded and no filler. Every clause carries information.

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

Completeness4/5

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

For a simple two-parameter read operation with annotation coverage and no output schema, this is nearly sufficient. The one remaining gap is what an 'element' record contains or whether the list is complete versus truncated.

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% and both required parameters (deckId, slideId) are documented in the schema, so the description is not obligated to restate them. It adds no constraint such as whether slideId must belong to deckId, leaving it at baseline.

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?

The description gives a specific verb and resource ('List all visual elements on a slide') plus a meaningful scope qualifier ('in z-index order'). It clearly separates itself from element_read by implying a collection over a whole slide, though it never names that 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?

Usage is only implied: an agent can infer this is the call for enumerating a slide's contents, but there is no statement of when to prefer it over element_read or slide_read, and no preconditions (e.g., slide must exist, visibility of hidden elements).

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