Skip to main content
Glama

reorder_slides

Move one or more slides to a specified position in a Google Slides deck. Provide slide object IDs and insertion index to reorder them consecutively.

Instructions

Move one or more slides to a new position in the deck.

Reorders slides by inserting them at insertion_index in the slide list. When multiple slide IDs are passed, they are placed consecutively at the target position, preserving the order given in slide_object_ids. This tool only reorders slides — it does not reorder page elements inside a slide. For that, use batch_update_presentation with updatePageElementZOrder.

Requires OAuth scope: https://www.googleapis.com/auth/presentations (write). Google Slides API enforces that all listed IDs must currently belong to the presentation; mixing element IDs with slide IDs is an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
slide_object_idsYesList of slide object IDs to move, in the order you want them to appear after the move. Each must be a slide page ID (from `get_presentation.slides[].objectId`), not a page element. Example: `["slide_3", "slide_1"]` will place slide_3 first, then slide_1 at `insertion_index`.
insertion_indexYes0-based position in the re-ordered deck where the moved slides start. `0` = move to the front. Index is computed AFTER removing the slides being moved — pass the final desired position, not adjusted math. To move slides to the end, use the current slide count (e.g., if the deck has 10 slides, `10` puts them last; the API clamps out-of-range values to end-of-deck).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description carries full burden. It details the insertion behavior (preserving order, index computation after removal, clamping out-of-range values) and side effects (requires write scope, mixing IDs is an error). This fully discloses the tool's behavioral traits.

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 concise with a clear lead sentence, followed by organized paragraphs. Each sentence adds value (e.g., index calculation, alternatives, errors). No wasted words.

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 (reordering with multiple slide IDs, index logic) and the presence of an output schema (indicated by context), the description is complete. It covers the core behavior, index details, error conditions, and permissions. The output schema (not shown) likely explains return values, so no further description needed.

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

Parameters4/5

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

Schema coverage is 75% (3 of 4 parameters have descriptions). The description adds significant meaning beyond the schema: explains slide_object_ids order preservation with example, and insertion_index computation after removal with clamping behavior. The user_google_email parameter lacks description but is self-explanatory.

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 ('Move one or more slides to a new position') and the resource ('the deck'). It distinguishes itself from sibling tools like duplicate_slide and format_slides_* by explicitly stating what it does and does not do (e.g., not reordering page elements).

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance ('Reorders slides...') and when-not-to-use ('does not reorder page elements...'). It directly points to an alternative tool (batch_update_presentation with updatePageElementZOrder) for different needs. Also includes required OAuth scope and error conditions.

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/HuntsDesk/ve-gws'

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