VoiceMoat

Schedule a post

schedule_post

Destructive

Add a post to the user's scheduled queue, to publish unattended at a time they choose. Call it once WITHOUT confirmation_token to get a preview and a token, then again with the token only if the user agrees. The time must be UTC ISO-8601 and at least ten minutes in the future.

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": {
      "content": "<content>",
      "platform": "<platform>",
      "scheduled_for": "<scheduled_for>"
    },
    "name": "schedule_post"
  }
}

Input Schema

Name	Required	Description
`format`	No	Twitter only. long_post is one post up to 25,000 characters and needs X Premium. Default post.
`content`	Yes	The exact post text.
`platform`	Yes	Which platform.
`signature`	No	Optional. "none" posts without the profile's signature. Leave it out otherwise.
`tone_used`	No	Optional tone label.
`account_id`	No	The connected account to post to, from list_profiles. Only needed when more than one account is connected on that platform.
`content_type`	No	Twitter only. Ignored on LinkedIn, which has no threads.
`made_with_ai`	No	Twitter only. Adds Twitter's Made with AI label to the post. Only when the user asks for it.
`scheduled_for`	Yes	UTC ISO-8601 timestamp, at least ten minutes from now.
`reply_settings`	No	Twitter only. Who can reply. Default everyone. On a thread it applies to the first post.
`confirmation_token`	No	Leave this out on the first call. The tool then returns a preview and a token without posting anything. Pass the token back, with identical arguments, only after the user has confirmed.

Output Schema

Name	Required	Description
`url`	No	The live post, once published.
`kind`	Yes	post_preview: nothing has been posted yet. post_result: the post went out or was queued.
`parts`	No	The post exactly as it will go out. More than one part is a Twitter thread.
`action`	Yes	The tool this card belongs to.
`length`	No
`status`	Yes
`platform`	Yes
`expires_at`	No	When this preview stops being confirmable, UTC ISO-8601.
`see_more_at`	No	LinkedIn only: the character in the post where "see more" falls on a computer.
`account_name`	Yes	The connected profile's handle or name, as the user sees it.
`calendar_url`	No	VoiceMoat's calendar, once scheduled.
`scheduled_for`	No	UTC ISO-8601. schedule_post only.
`duplicate_minutes_ago`	No	Set when this exact text went out to this account that many minutes ago.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 6, 2026

addedInput schema / properties / format

Added value: +{
+  "description": "Twitter only. long_post is one post up to 25,000 characters and needs X Premium. Default post.",
+  "enum": [
+    "post",
+    "long_post"
+  ],
+  "type": "string"
+}

addedInput schema / properties / made_with_ai

Added value: +{
+  "description": "Twitter only. Adds Twitter's Made with AI label to the post. Only when the user asks for it.",
+  "type": "boolean"
+}

addedInput schema / properties / reply_settings

Added value: +{
+  "description": "Twitter only. Who can reply. Default everyone. On a thread it applies to the first post.",
+  "enum": [
+    "everyone",
+    "following",
+    "mentionedUsers",
+    "subscribers",
+    "verified"
+  ],
+  "type": "string"
+}

addedInput schema / properties / signature

Added value: +{
+  "description": "Optional. \"none\" posts without the profile's signature. Leave it out otherwise.",
+  "enum": [
+    "none"
+  ],
+  "type": "string"
+}

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "account_name": {
+      "description": "The connected profile's handle or name, as the user sees it.",
+      "type": "string"
+    },
+    "action": {
+      "description": "The tool this card belongs to.",
+      "enum": [
+        "publish_post",
+        "schedule_post"
+      ],
+      "type": "string"
+    },
+    "calendar_url": {
+      "description": "VoiceMoat's calendar, once scheduled.",
+      "type": "string"
+    },
+    "duplicate_minutes_ago": {
+      "description": "Set when this exact text went out to this account that many minutes ago.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "expires_at": {
+      "description": "When this preview stops being confirmable, UTC ISO-8601.",
+      "type": "string"
+    },
+    "kind": {
+      "description": "post_preview: nothing has been posted yet. post_result: the post went out or was queued.",
+      "enum": [
+        "post_preview",
+        "post_result"
+      ],
+      "type": "string"
+    },
+    "length": {
+      "additionalProperties": false,
+      "properties": {
+        "limit": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "longest_part": {
+          "description": "True for a thread: used is its longest part.",
+          "type": "boolean"
+        },
+        "used": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "used",
+        "limit",
+        "longest_part"
+      ],
+      "type": "object"
+    },
+    "parts": {
+      "description": "The post exactly as it will go out. More than one part is a Twitter thread.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "platform": {
+      "enum": [
+        "linkedin",
+        "twitter"
+      ],
+      "type": "string"
+    },
+    "scheduled_for": {
+      "description": "UTC ISO-8601. schedule_post only.",
+      "type": "string"
+    },
+    "see_more_at": {
+      "description": "LinkedIn only: the character in the post where \"see more\" falls on a computer.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "status": {
+      "enum": [
+        "confirm_required",
+        "published",
+        "scheduled"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "description": "The live post, once published.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "action",
+    "status",
+    "platform",
+    "account_name"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Adds real value beyond the annotations by disclosing that the first call is side-effect free and returns a preview plus token, which clarifies the destructiveHint=true risk. It does not mention what gets posted where on success, rate limits, or whether scheduling can be canceled, so the safety story is only partially filled in.

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?

Three sentences, each earning its place: what the tool does, the confirmation protocol, and the hard timing constraint. Front-loaded and free of filler.

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?

For an 11-parameter mutation tool with an output schema and fully described parameters, the description covers the intent, the risky two-step flow, and the timing precondition. Nothing essential for a correct call 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 every parameter is already documented, including confirmation_token's two-phase semantics and the UTC constraint. The description restates those facts rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb and resource ("Add a post to the user's scheduled queue") plus the outcome ("publish unattended at a time they choose"). That implies the distinction from publish_post (immediate publishing), but it never names that sibling, so an agent must infer the boundary.

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

Usage Guidelines4/5

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

Gives explicit invocation guidance for the two-call confirmation flow: first call without confirmation_token for a preview, second call with the token only after user agreement. It lacks guidance on when to prefer this over publish_post or list_profiles for account selection.

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

All VoiceMoat 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?