Outline a carousel, callable

Turns a topic into a slide-by-slide carousel outline: a hook, one idea per middle slide, a specific ask, and review notes saying what is still weak.

It returns STRUCTURE rather than rendered images. Every tool in this category sells the render, and a render is the part an agent can already do; deciding what goes on each slide, and in what order, is the part that decides whether the carousel works.

There is a page for people too: the carousel outline tool runs the same engine in a browser, free and without an account.

Inputs and bounds

What comes back

• slides - each with its number, its kind (hook, point or ask) and its body
• slideCount - derived from how much the brief carries, never padded to a round number
• notes - checks computed against this outline, so a note only appears when it is true

Where the data goes

What it will not do

Not a slide renderer and not a design tool. It will not produce artwork, and it deliberately does not try, because a generic render published under someone's name costs them more than it saves.

Calling it

The server speaks MCP over JSON-RPC 2.0 at https://repic.site/api/free-tools/mcp. There is no key and no account. Calls share one per-IP daily budget with the free web tools, so an agent gets the same allowance a person does.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "outline_linkedin_carousel",
    "arguments": {
      "topic": "Why most engineering managers inherit a team rather than build one",
      "audience": "New engineering managers",
      "tone": "Plain and direct",
      "takeaway": "Write down the one process you will change first"
    }
  }
}

Call tools/list first for every capability and its schema. The result carries both a readable content block and a lossless structuredContent object, so nothing has to be parsed out of prose.

The other skills