Skip to main content
Glama

Schedule post

schedule_content_post
Destructive

Schedule a post to be published at a time, or cancel its schedule. Obriym itself publishes it to every ready channel of the post within about 15 minutes after that time — the AI client does not need to be running then. This is how regular publishing is set up: create several drafts, then schedule each. Needs the owner's "AI may publish to social channels" switch to schedule (see publishingEnabled in list_content_channels); cancelling (scheduledAt: null) does not. A post that is published or being published cannot be scheduled. Returns a warning when no channel of the post is ready yet. Echoes the workspace.

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": {
      "id": "<id>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "schedule_content_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe publication id returned by create_content_post or list_content_posts.
scheduledAtYesWhen to publish, as an ISO 8601 date-time WITH its time-zone offset, e.g. "2026-10-12T10:00:00+03:00". At least one minute and at most one year ahead; list_content_channels returns the workspace time zone. Obriym publishes it itself at that time — no AI client needs to be running. null cancels the schedule and returns the post to a draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only mark it non-read-only, non-idempotent, destructive, open-world): it discloses that Obriym itself publishes ~15 minutes after the target time with no AI client running, that the owner's publishing switch gates scheduling but not cancellation, that published posts cannot be rescheduled, and that a warning is returned when no channel is ready.

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?

Front-loads the action, then prerequisites, then limits, which is the right order. It is dense but each sentence carries a constraint; the only mild waste is restating the publish-timing behavior that the scheduledAt schema description already covers.

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?

With no output schema, the description compensates by stating what comes back (a warning when no channel is ready) and that the workspace is echoed, and it covers prerequisites, failure modes and reversibility. Nothing material for correct invocation 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% and the schema already documents the ISO 8601-with-offset format, the one-minute/one-year window, the workspace time-zone pointer and the null-cancels semantics. The description largely restates these, adding only that null returns the post to a draft, so the baseline 3 applies.

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 precise verb+resource ('Schedule a post to be published at a time') plus the inverse operation ('cancel its schedule'), which immediately separates it from publish_content_post (publish now) and create_content_post (draft). An agent can place it in the content lifecycle 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?

Gives explicit when-to-use workflow ('create several drafts, then schedule each'), an explicit prerequisite (owner's 'AI may publish to social channels' switch, with a pointer to publishingEnabled in list_content_channels), an explicit carve-out for cancelling, and an explicit cannot-use condition ('A post that is published or being published cannot be scheduled').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources