Skip to main content
Glama

Switch a carousel's template

flypost_switch_carousel_template

Change a carousel's template as the editor's template picker does, without rendering. Templates come in copy styles: standard/editorial-light/portrait-photo take ~22-30 words a slide; minimal-* take one short statement (~10-12 words) plus an optional supporting line; photo-* and wide-* take a ~10-word caption over a slide image. Within one style the switch is instant. Across styles, fit 'keep' keeps the words exactly (they render smaller; tips are not shown in statement styles), and fit 'fit' has the app re-fit every slide for the new style (or restores the version already written for it); the previous version is kept, so switching back is free. Photo and wide templates need an image on every hook and body slide (flypost_generate_slide_image).

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>",
      "template_family": "<template_family>"
    },
    "name": "flypost_switch_carousel_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoAcross copy styles: 'keep' (default) or 'fit'.
template_familyYes
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With only sparse annotations supplied, the description carries the behavioral burden well: it explains instant same-style switching, cross-style 'keep' versus 'fit' behavior, word-count implications, hidden tips in statement styles, and that the previous version is retained so switching back is free. It also discloses the image prerequisite for photo and wide templates. There is no contradiction with the readOnlyHint=false, destructiveHint=false annotations.

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 information-dense but front-loaded with the core action, then proceeds through template families, fit behavior, and prerequisites. Every sentence contributes operational detail needed to choose parameters or understand side effects.

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 mutation tool with no output schema and minimal annotations, the description covers the essential behavioral details: style families, fit semantics, retained previous version, and image requirements. It could more fully explain the content_bank_item_id parameter or what the tool returns, but the critical calling information is present.

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 only 33%, with only 'fit' documented in the schema, so the description usefully adds meaning for the complex parameters. It groups the template_family enum values into copy styles and explains their word-count and image requirements, and it clarifies the behavioral difference between fit='keep' and fit='fit'. The required content_bank_item_id remains unexplained, which keeps this below a 5.

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 states a specific verb and resource: 'Change a carousel's template as the editor's template picker does, without rendering.' The 'without rendering' clause distinguishes it from visual-generation siblings, so an agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

It clearly frames the tool as the editor-style template switcher and explains the key fit decision across copy styles. It also notes that photo and wide templates require images generated via flypost_generate_slide_image. It does not explicitly compare against sibling operations such as build_carousel or edit_slides, so it stops short of full when/when-not guidance.

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.