Skip to main content
Glama
Sign In

Simplo

by ai.getsimplo
OverviewDiscussionsAdmin

Create carousel

create_carousel

Writes and draws an Instagram carousel about a topic, then saves it as a draft post. COSTS CREDITS: the slide copy, plus each picture when pictures are on (the boldPhoto style always has pictures). Slide text is set in real type from the brand's fonts, so it is spelled exactly as written. The draft is never published or scheduled here: schedule it with schedule_post, or publish it with publish_post, after the user approves. Pass a time (localTime with timeZone, or scheduledAt) to place the draft on its day in the plan (draft_scheduled); it still never sends by itself. A small preview of every slide comes back with the result, so you can check each one. A slide listed in overflowSlides has more text than fits, so its copy runs off the slide — tell the user. To redo a carousel, pass the old draft as replacesPostId: the new one takes its day in the plan and the old draft is deleted, so the plan never holds both. possibleDuplicateOf names another planned post within 14 days that opens the same way: ask the user whether both should stay.

Input Schema

NameRequiredDescriptionDefault
goalNoStyled decks only. "tips" teaches and closes on a save; "promo" sells and closes on the brand's offer (its offer line, or the link in bio). Omitted: read from the topic
styleNoA carousel style. Omitted: the style of the brand's latest styled carousel, else clean. "plain" draws the older layouts with no style
topicYesWhat the carousel is about
captionNoThe post caption; omit to use the one written with the slides
picturesNoPut pictures on some slides (product photos where they fit, generated otherwise); costs more
timeZoneNoThe user's IANA time zone, e.g. America/Edmonton. Needed with localTime; with scheduledAt it only sets the zone scheduledLocal is shown in. The answer's scheduledLocal says how the saved time reads there: check it against what the user asked for
localTimeNoThe time as the user's clock shows it, YYYY-MM-DDTHH:MM with no offset (e.g. 2026-11-09T12:00), with timeZone. Preferred over scheduledAt: Simplo works out the UTC offset in force on that date. Not together with scheduledAt
projectIdYesSimplo project id (from list_projects)
slideCountNo
scheduledAtNoISO 8601 time with offset: puts the draft on that day in the plan, without scheduling it. localTime with timeZone is safer
replacesPostIdNoA draft this carousel replaces: it takes that draft's day (unless a time is passed) and the old draft is deleted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / goal
      Added value: +{
+  "description": "Styled decks only. \"tips\" teaches and closes on a save; \"promo\" sells and closes on the brand's offer (its offer line, or the link in bio). Omitted: read from the topic",
+  "enum": [
+    "tips",
+    "promo"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / localTime
      Added value: +{
+  "description": "The time as the user's clock shows it, YYYY-MM-DDTHH:MM with no offset (e.g. 2026-11-09T12:00), with timeZone. Preferred over scheduledAt: Simplo works out the UTC offset in force on that date. Not together with scheduledAt",
+  "type": "string"
+}
    • changedInput schema / properties / replacesPostId / description
      Previous value: -"A draft this carousel replaces: it takes that draft's day (unless scheduledAt is passed) and the old draft is deleted"New value: +"A draft this carousel replaces: it takes that draft's day (unless a time is passed) and the old draft is deleted"
    • changedInput schema / properties / scheduledAt / description
      Previous value: -"ISO 8601 time with offset: puts the draft on that day in the plan, without scheduling it"New value: +"ISO 8601 time with offset: puts the draft on that day in the plan, without scheduling it. localTime with timeZone is safer"
    • addedInput schema / properties / timeZone
      Added value: +{
+  "description": "The user's IANA time zone, e.g. America/Edmonton. Needed with localTime; with scheduledAt it only sets the zone scheduledLocal is shown in. The answer's scheduledLocal says how the saved time reads there: check it against what the user asked for",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing credit costs, that boldPhoto always generates pictures, that slide text is rendered in real brand fonts, that a passed time never auto-sends, and that replacesPostId deletes the old draft so the plan never holds both. The only gap is the mention of possibleDuplicateOf, which does not appear in the input schema, leaving its origin ambiguous.

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?

Front-loaded with purpose and then cost, then behavior, then the follow-up routing — a good ordering. It is one dense block and the final sentence about possibleDuplicateOf arrives without context since that field is not in the schema, which slightly blunts the structure.

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?

With 11 parameters and no output schema, the description carries the burden well: it explains what comes back (a preview of every slide), what overflowSlides means and what to do about it, and how scheduledLocal should be checked. Combined with the schema, an agent has what it needs to call this correctly.

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 coverage is already 91%, so the baseline is 3, but the description adds real meaning: the picture cost implication, the boldPhoto style forcing pictures, the preference of localTime over scheduledAt, and the deletion/day-inheritance semantics of replacesPostId. It does not repeat the schema's enum explanations, which is the right call.

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?

States a specific verb and resource — 'Writes and draws an Instagram carousel about a topic, then saves it as a draft post' — which cleanly separates it from create_post and create_reel among the siblings. The end state (a draft, not a published post) is stated in the same breath.

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 this tool never publishes or schedules, and names the follow-up tools: 'schedule it with schedule_post, or publish it with publish_post, after the user approves.' It also gives conditional usage for the time parameters (place the draft on its day) and for replacesPostId (redo a carousel) and possibleDuplicateOf (ask the user).

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

All Simplo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources