Clypmint

Write a month of video ideas

plan_content

Idempotent

Start a content calendar for a topic: count faceless videos (1-31) over days (7-31), each with a title, hook, the exact script, caption, hashtags and a posting time. Best: write the ideas yourself in the conversation and send them as items (taken as written, at once); otherwise Clypmint writes them (this call keeps going until they are written, or tells you to call again with the same operation_id). Makes nothing and spends nothing; answers plan_id, the ideas and the quote (credits a video, room left this month). Show the user the ideas, change them with edit_content_plan, and approve_plan only after their yes. Use for "start a faceless account" or "a month of posts about X". Cost: Free to write; making each video costs about 4 credits (30 s).

Input Schema

Name	Required	Description
`days`	Yes	Over how many days (7-31).
`count`	No	How many videos (1-31); leave out when sending items.
`items`	No	Ideas you wrote yourself (title, hook, script, caption, hashtags): taken as written, at once. Without them Clypmint writes the ideas.
`topic`	Yes	What the account posts about.
`voice`	No	The narrator for a video made from words: matilda, sarah, jessica, alice, liam, chris, brian, george, roger, laura, charlie, river, will, eric, bella, daniel, lily, bill, adam, callum, harry (sarah: calm, reassuring, health and money; alice: a clear British educator; brian: deep documentary; liam: energetic ads). Leave out to let Clypmint pick one that fits the words. "Voice: <name>" in instructions does the same.
`seconds`	No
`audience`	No
`start_at`	No	The first day; tomorrow when left out.
`style_id`	No
`timezone`	No
`platforms`	No	Where each post goes; Instagram when left out.
`instructions`	No
`operation_id`	No	A stable ID for this request. Preserve it on retries. Use a new ID only for a deliberate new request.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`items`	No
`quote`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 22, 2026
- addedInput schema / properties / items / items / properties / hashtags / items / description
```
Added value: +"One word, letters, digits or _, with or without #."
```
- addedInput schema / properties / items / items / properties / hashtags / items / maxLength
```
Added value: +61
```
- addedInput schema / properties / items / items / properties / hashtags / items / minLength
```
Added value: +1
```
- removedInput schema / properties / items / items / properties / hashtags / items / pattern
```
Removed value: -"^#?[\\p{L}\\p{N}_]{1,60}$"
```

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / voice / description

Previous value: -"The narrator for a video made from words: matilda, sarah, jessica, alice, liam, chris, brian, george, roger, laura, charlie, river, will, eric, bella, daniel, lily, bill, adam, callum, harry. Leave out to let Clypmint pick one that fits."New value: +"The narrator for a video made from words: matilda, sarah, jessica, alice, liam, chris, brian, george, roger, laura, charlie, river, will, eric, bella, daniel, lily, bill, adam, callum, harry (sarah: calm, reassuring, health and money; alice: a clear British educator; brian: deep documentary; liam: energetic ads). Leave out to let Clypmint pick one that fits the words. \"Voice: <name>\" in instructions does the same."

Changed1 schema field changedOct 13, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / voice / description

Previous value: -"The narrator for a video made from words: matilda, sarah, jessica, alice, liam, chris, brian, george. Leave out to let Clypmint pick one that fits."New value: +"The narrator for a video made from words: matilda, sarah, jessica, alice, liam, chris, brian, george, roger, laura, charlie, river, will, eric, bella, daniel, lily, bill, adam, callum, harry. Leave out to let Clypmint pick one that fits."

changedInput schema / properties / voice / enum

Previous value: -[
-  "matilda",
-  "sarah",
-  "jessica",
-  "alice",
-  "liam",
-  "chris",
-  "brian",
-  "george"
-]New value: +[
+  "matilda",
+  "sarah",
+  "jessica",
+  "alice",
+  "liam",
+  "chris",
+  "brian",
+  "george",
+  "roger",
+  "laura",
+  "charlie",
+  "river",
+  "will",
+  "eric",
+  "bella",
+  "daniel",
+  "lily",
+  "bill",
+  "adam",
+  "callum",
+  "harry"
+]

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Clypmint plan_content result. Error results carry error; successful requests expose the identifiers and state available for the next step. Signed media stays in private metadata.",
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "code": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "dry_run": {
+      "type": "boolean"
+    },
+    "error": {
+      "type": "string"
+    },
+    "import_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "output_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "quote": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "studio_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "style_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "video_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Discloses important behavior beyond the annotations: the call may be long-running, may tell the agent to retry with the same operation_id, makes no videos and spends no credits, and returns plan_id, ideas, and a quote. It also states the cost model for later video creation, which an agent needs before recommending approval.

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 dense but front-loaded with the main purpose and key constraints. Every sentence adds useful procedural or cost context, though the long parenthetical-heavy prose could be more scannable for a tool with this many parameters.

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 complex 13-parameter planning tool, the description covers the critical call behavior, output values, cost, and approval workflow, and an output schema exists for return details. The remaining gap is that several optional parameters are not explained in the description and are only partially covered by the schema.

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

Parameters3/5

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

The description explains the core parameters (topic, days, count, items) and the item shape, and clarifies that supplied items are taken as written at once. However, with 13 parameters and only 62% schema description coverage, it leaves several optional parameters such as seconds, audience, style_id, timezone, and instructions unexplained in the description. The schema carries part of the burden, so a baseline 3 is appropriate.

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 ('Start a content calendar for a topic') plus the exact output shape: video ideas with title, hook, script, caption, hashtags, and posting time. It names the relevant downstream siblings edit_content_plan and approve_plan, so the agent can distinguish this from editing or approving a plan.

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?

Gives explicit trigger phrases ('start a faceless account', 'a month of posts about X') and explains the two modes: send self-written items versus let Clypmint write them. It also prescribes the post-call workflow: show the ideas to the user, use edit_content_plan for changes, and call approve_plan only after the user agrees.

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

All Clypmint tools Inspect

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

Need Help?