Skip to main content
Glama
haandol
by haandol

prepare_slide_edit

Prepares to add or update a slide by updating the outline and returning a generation task with prompts and schema.

Instructions

Prepares to add or update ONE slide — updates the outline, returns a generation task.

No LLM call. For add: shifts files and inserts the new outline. For update: updates the outline (if title/content_summary given). Returns the slide generation prompt + response_schema. Generate the slide spec JSON, then call ingest_slide_edit with the SAME action and slide_index.

For narrow single-element tweaks, use prepare_modify_component instead.

Args: project_id: Target project ID (required). action: "add" | "update". slide_index: 1-based position. add: insertion point (-1 = end). update: target. title: Slide title (required for add; required for update on imported projects). content_summary: Content description (required for add; required for update on imported). component_hint: Layout hint (default: "bullets"). slide_type: "title" | "content" | "closing" | "agenda" (default: "content"). speaker_notes: Optional speaker notes. color_theme: Color theme ("dark" or "light").

Returns: JSON with system_prompt, user_prompt, response_schema, action, project_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
actionYes
project_idYes
slide_typeNocontent
color_themeNodark
slide_indexNo
speaker_notesNo
component_hintNobullets
content_summaryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses key behaviors: no LLM call, shifts files for add, updates outline, returns prompt and response_schema. Lacks explicit mention of side effects or permissions, but overall good transparency.

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?

Well-structured: summary, usage guidance, parameter list, return value. Front-loaded purpose, every sentence adds value. No fluff.

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?

Complete coverage: explains what tool does, how to use, parameter details, return value, and next step (ingest_slide_edit). Output schema exists but description still covers return JSON.

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?

All 9 parameters are described with defaults, allowed values, and conditional requirements. The schema has 0% description coverage, so the description fully compensates and adds significant meaning.

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?

Clearly states the tool prepares to add or update one slide, updating outline and returning a generation task. Distinguishes from sibling by naming prepare_modify_component for narrow tweaks.

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?

Explicitly says when to use (add/update slide) and when not (use prepare_modify_component for single-element tweaks). Also provides conditional requirements for title and content_summary.

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/haandol/ppt-generator'

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