Skip to main content
Glama

tosea_edit_slide_page

Edit or add slides in presentations using text instructions and optional visual references to modify content or layout.

Instructions

Modify or insert a slide. Supports optional screenshot grounding for multimodal edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYes
page_numberYes
actionYes
instructionYes
edit_modeNooutline_layout
model_nameNo
image_modelNo
after_slideNo
screenshot_pathNo
idempotency_keyNo

Implementation Reference

  • src/tools.ts:243-290 (registration)
    Registration and handler implementation for "tosea_edit_slide_page" tool. The handler calls `client.editSlidePage` after preparing arguments and reading the screenshot if provided.
    server.tool(
      "tosea_edit_slide_page",
      "Modify or insert a slide. Supports optional screenshot grounding for multimodal edits.",
      {
        presentation_id: z.string().uuid(),
        page_number: z.number().int().min(1),
        action: z.enum(["modify", "insert"]),
        instruction: z.string().min(1),
        edit_mode: z.enum(["outline_layout", "layout_only"]).default("outline_layout"),
        model_name: z.string().optional(),
        image_model: z.string().optional(),
        after_slide: z.number().int().min(1).optional(),
        screenshot_path: z.string().optional(),
        idempotency_key: z.string().min(8).optional()
      },
      async ({
        presentation_id,
        page_number,
        action,
        instruction,
        edit_mode,
        model_name,
        image_model,
        after_slide,
        screenshot_path,
        idempotency_key
      }) => {
        try {
          const screenshotBase64 = await maybeReadBase64File(screenshot_path);
          return asToolResult(
            await client.editSlidePage({
              presentationId: presentation_id,
              pageNumber: page_number,
              action,
              instruction,
              editMode: edit_mode,
              modelName: model_name,
              imageModel: image_model,
              afterSlide: after_slide,
              screenshotBase64,
              idempotencyKey: idempotency_key
            })
          );
        } catch (error) {
          throw wrapToolError(error);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'optional screenshot grounding for multimodal edits' which hints at visual editing capabilities, but fails to describe critical behaviors: whether this is a destructive mutation, what permissions are required, how long operations take, error conditions, or what happens when inserting vs modifying. For a 10-parameter mutation tool, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with two clear sentences. The first sentence states the core functionality, and the second adds important capability context about multimodal editing. No wasted words, though it could be more front-loaded with critical behavioral information given the tool's complexity.

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

Completeness2/5

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

For a complex mutation tool with 10 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, side effects, or parameter interactions. The mention of 'multimodal edits' is helpful but doesn't compensate for the missing foundational information needed to use this tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, meaning no parameters have descriptions in the schema. The tool description provides no information about any of the 10 parameters—not explaining what 'presentation_id', 'page_number', 'action', 'instruction', or the 6 optional parameters mean or how they interact. The description doesn't compensate for the complete lack of schema documentation.

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 clearly states the tool's purpose: 'Modify or insert a slide' specifies the verb and resource. It distinguishes from siblings like 'tosea_edit_outline_page' by focusing on slides rather than outlines, but doesn't explicitly contrast with other slide-related tools (none listed). The mention of 'optional screenshot grounding for multimodal edits' adds useful context about capabilities.

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?

No explicit guidance on when to use this tool versus alternatives. While the description mentions 'modify or insert a slide,' it doesn't specify when to choose 'modify' vs 'insert' actions, or when to use this versus sibling tools like 'tosea_edit_outline_page' for outline modifications. The agent must infer usage from parameter names and enums alone.

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/ToseaAI/mcp-ToseaAI'

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