`validate_schedule`

Validate a schedule document against provider rules, media limits, account state, and publish times WITHOUT creating any posts. Always run this before apply_schedule.

Calling it

Invoke this tool with a JSON-RPC 2.0 tools/call request against the hosted MCP endpoint at POST https://getsocialclaw.com/mcp. Send your workspace API key as Authorization: Bearer sc_live_your_key. In an MCP client (Claude, Cursor, Claude Code) the client makes this call for you — just ask it to use validate_schedule.

Arguments

Parameter	Type		Description
`schedule`	`object`	required	SocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }. Per-post provider settings go in settings, e.g. TikTok inbox mode: settings: { tiktokPostMode: "draft" } sends the media to TikTok's inbox notification flow instead of publishing, and the creator finishes the post inside the TikTok app.

Example request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "validate_schedule",
    "arguments": {
      "schedule": {
        "timezone": "UTC",
        "posts": [
          {
            "account": "linkedin:person:123",
            "name": "Launch update",
            "description": "We just shipped the new SocialClaw workflow.",
            "publish_at": "2026-08-01T15:00:00Z"
          }
        ]
      }
    }
  }
}

Response

The server replies with a JSON-RPC result whose content array carries the tool output as a JSON-encoded text block. isError is true when the call failed.

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{ /* JSON-encoded tool result */ }"
      }
    ],
    "isError": false
  }
}