Clypmint

Change a scheduled post

update_post

DestructiveIdempotent

Change the caption or publication time of an existing scheduled post identified by post_id. Returns the updated publishing receipt.

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": {
      "post_id": "<post_id>"
    },
    "name": "update_post"
  }
}

Input Schema

Name	Required	Description
`postAt`	No	The new time: an ISO time with offset.
`caption`	No	The new caption.
`post_id`	Yes	The post to change, from list_posts.
`timezone`	No	The IANA time zone the user means.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	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.

AddedNov 8, 2026
RemovedOct 21, 2026

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 update_post 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"
+      ]
+    },
+    "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 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description is consistent with the annotations (readOnlyHint=false, destructiveHint=true) by framing this as a mutation, and it adds that the change is restricted to caption or publication time and that an updated publishing receipt is returned. It does not disclose that overwriting a caption destroys the previous value, nor any permission or rate constraints — meaningful gaps given destructiveHint=true.

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?

Two sentences, no filler, with the scope constraint ('existing scheduled post') front-loaded before the return-value note. Every clause carries information.

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?

With a full output schema and fully documented parameters, the description only needs to convey the mutation scope and return, which it does. It could say slightly more about the destructive replacement of an existing caption, but nothing essential to invoking the tool is missing.

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?

Schema description coverage is 100%, so all four parameters are already documented in the schema, including post_id's provenance ('from list_posts') and timezone's role. The description adds little beyond identifying which fields are mutable; the timezone parameter is not addressed in prose, but the schema carries it adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Change') plus the limited field set (caption or publication time) and the resource ('an existing scheduled post identified by post_id'). This cleanly separates it from schedule_post and cancel_post, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'existing scheduled post', which tells the agent this is for already-scheduled content rather than new scheduling. It gives no explicit when-not guidance and does not route the agent to cancel_post or schedule_post for adjacent operations.

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?