Clypmint

Change ideas in a content calendar

edit_content_plan

DestructiveIdempotent

Change ideas by number (n) before they are made or posted: title, hook, script, caption, hashtags, posting time, platforms, or removed: true to drop one (false puts it back). Words cannot change once an idea is being made; a scheduled post changes with update_post. Free. Cost: Free: no credits.

Input Schema

Name	Required	Description	Default
`items`	Yes
`plan_id`	Yes

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`items`	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 13, 2026

changedInput schema / $schema

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

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Clypmint edit_content_plan 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"
+      ]
+    },
+    "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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, and the description usefully adds that removal is reversible and that text is locked once an idea enters production. However, the trailing 'Free. Cost: Free: no credits' is repetitive boilerplate, and it never clarifies what exactly gets replaced on a partial update.

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 critical constraint (editable before production) is front-loaded and the field list is compact. The final 'Free. Cost: Free: no credits' clause is redundant filler that weakens an otherwise dense sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the annotations cover the safety profile, so the description need not explain returns. But for a destructive mutation it never says whether omitted fields are preserved or cleared, which 'words' are locked once production starts, or what plan_id must reference — gaps an agent needs resolved before calling.

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?

With only 0% schema description coverage, the description carries the burden well: it explains that 'n' is the idea number and maps the editable fields to title, hook, script, caption, hashtags, post_at and platforms, plus the true/false semantics of 'removed'. It adds nothing about plan_id, and the value constraints (max 31 items, 10 hashtags, 3 platforms) are left entirely 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?

A specific verb plus resource ('Change ideas by number') with an explicit list of the fields that can be edited. It also draws a boundary against the sibling update_post for already-scheduled posts, so an agent can identify the right tool 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 Guidelines5/5

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

States the precondition 'before they are made or posted' and names the alternative path explicitly ('a scheduled post changes with update_post'). It also gives the when-to-use rule for removal versus restoration ('true to drop one, false puts it back'), leaving nothing to inference.

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?