Skip to main content
Glama

Edit carousel slides' words

flypost_edit_slides
Destructive

Change the words on one or more carousel slides in place (the editor's slide fields): title, body, subtitle, example, points (recap), emphasis_words, actions/handle (CTA). Only the fields you pass change; pass null to clear one. Slide ids come from flypost_view_visuals. Use this for any edit short of rewriting the whole deck (flypost_save_concept with content_bank_item_id does that). Slide images stay where they are.

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": {
      "content_bank_item_id": "<content_bank_item_id>",
      "edits": "<edits>"
    },
    "name": "flypost_edit_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYes
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context: the edit is in place, only passed fields mutate, null explicitly clears a field, and slide images are untouched. It stops short of stating irreversibility, validation/atomicity (whether a partial failure rolls back), or the 30-slide batch ceiling.

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?

Four tight sentences, each doing distinct work: scope, mutation semantics, id provenance, and sibling routing. The mutation contract is front-loaded and nothing is padded or repeated from the schema.

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 nested-batch mutation tool with no output schema and no annotation-level detail on failure modes, the description covers what changes, what stays, and where inputs come from. Remaining gaps are the unexplained content_bank_item_id scope, batch size limits, and whether an edit can be reverted.

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 description coverage is 0%, so the description must carry the nested field meaning, and it largely does: it maps the editable fields to their editor concepts and explains the null-clears / omitted-preserves contract plus the provenance of slide_id. The required content_bank_item_id is never explained, and the minItems=1/maxItems=30 bounds on the edits array are left to the schema.

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?

"Change the words on one or more carousel slides in place" names a specific verb and resource, then enumerates exactly which fields are editable (title, body, subtitle, example, points, emphasis_words, actions/handle). An agent can distinguish this from the deck-level rewrite and from the read-only visual viewer without opening any schema.

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?

Explicit routing is provided in both directions: use this for "any edit short of rewriting the whole deck," while full rewrites go to flypost_save_concept with content_bank_item_id, and slide ids come from flypost_view_visuals. The alternative is named together with the condition that selects it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.