Skip to main content
Glama

tosea_edit_outline_page

Edit outline content in presentations by modifying or inserting text on specific pages using the MCP edit contract.

Instructions

Modify or insert outline content synchronously through the aggregated MCP edit contract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYes
page_numberYes
actionYes
instructionYes
model_nameNo
after_slideNo
idempotency_keyNo

Implementation Reference

  • The handler implementation for the tosea_edit_outline_page tool, which calls the client's editOutlinePage method.
    async ({
      presentation_id,
      page_number,
      action,
      instruction,
      model_name,
      after_slide,
      idempotency_key
    }) => {
      try {
        return asToolResult(
          await client.editOutlinePage({
            presentationId: presentation_id,
            pageNumber: page_number,
            action,
            instruction,
            modelName: model_name,
            afterSlide: after_slide,
            idempotencyKey: idempotency_key
          })
        );
      } catch (error) {
        throw wrapToolError(error);
      }
    }
  • src/tools.ts:179-215 (registration)
    Registration of the tosea_edit_outline_page tool with its schema definition and handler.
    server.tool(
      "tosea_edit_outline_page",
      "Modify or insert outline content synchronously through the aggregated MCP edit contract.",
      {
        presentation_id: z.string().uuid(),
        page_number: z.number().int().min(1),
        action: z.enum(["modify", "insert"]),
        instruction: z.string().min(1),
        model_name: z.string().optional(),
        after_slide: z.number().int().min(1).optional(),
        idempotency_key: z.string().min(8).optional()
      },
      async ({
        presentation_id,
        page_number,
        action,
        instruction,
        model_name,
        after_slide,
        idempotency_key
      }) => {
        try {
          return asToolResult(
            await client.editOutlinePage({
              presentationId: presentation_id,
              pageNumber: page_number,
              action,
              instruction,
              modelName: model_name,
              afterSlide: after_slide,
              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 'synchronously' which indicates immediate execution, but doesn't cover important aspects like required permissions, whether this is a destructive operation, rate limits, error handling, or what happens when modifying versus inserting. The phrase 'aggregated MCP edit contract' is opaque rather than transparent.

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 a single sentence that's reasonably concise. However, it's not optimally structured - it leads with technical implementation details ('through the aggregated MCP edit contract') rather than user-facing functionality. While brief, it could be more effectively organized to prioritize clarity over technical terminology.

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 tool with 7 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what the tool returns, what 'outline' means in this context, how modifications affect the presentation, or provide any context about the editing operations. The description leaves too many unanswered questions for effective tool use.

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

Parameters2/5

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

With 0% schema description coverage for 7 parameters, the description provides no information about any parameters. It doesn't explain what 'presentation_id', 'page_number', 'action', 'instruction', 'model_name', 'after_slide', or 'idempotency_key' mean or how they should be used. The description fails to 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'modify or insert outline content' which gives a basic purpose, but it's vague about what 'outline content' refers to (presentation outline? document outline?) and doesn't distinguish it from sibling tools like 'tosea_edit_slide_page' or 'tosea_generate_outline'. The phrase 'through the aggregated MCP edit contract' adds technical jargon but doesn't clarify the actual function.

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 guidance is provided about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'tosea_edit_slide_page' (for slide editing) or 'tosea_generate_outline' (for creating outlines), nor does it specify prerequisites or appropriate contexts for using this synchronous editing tool.

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