Configured tool · write

`submit_plan`

Propose a time-bounded publication plan for one human approval.

writenon-destructiveclosed-world

Human and agent roles

Configured boundary

Configured workspace

The agent proposes accounts, timing, purpose, and capacity. Only a human supervisor can authorize the plan.

This reference describes a connection made with @postdom/mcp@0.3.0 and a workspace-scoped agent key created in Accounts.

Callable schema

Input fields

Field names match the configured tool schema. Runtime-only constraints are labeled separately from schema validation.

FieldTypeContract

account_idsRequired

string[]

At least one value · Runtime: unique account/platform targets

Connected destination account identifiers inside the proposed boundary.

titleRequired

string

1–120 characters

A short human-readable name for the plan.

objectiveRequired

string

1–1,000 characters

The outcome the bounded schedule should support.

starts_atRequired

datetime

RFC 3339 UTC ending in Z

The opening instant of the proposed plan window.

ends_atRequired

datetime

Schema: UTC ending in Z · Runtime: after start, ≤14 days

The closing instant of the proposed plan window.

max_postsRequired

integer

1–20

The maximum posts the plan can authorize.

brief_versionOptional

integer

Positive · must exist in this workspace

The Workspace Brief version used to plan or write the proposed work.

intentRequired

string

1–500 characters

The calling agent's reason for proposing this plan.

agent_identityOptional

string

1–120 characters

Caller identity when the configured client does not supply one.

idempotency_keyOptional

string

Non-empty

Caller-supplied replay key. The adapter generates a UUID when omitted.

Synthetic values

Example call

Identifiers and values are examples. They do not represent a connected workspace or accepted media source.

EXAMPLE CALL · CONFIGURED TOOL SCHEMA

submit_plan({
  account_ids: ["acct_example_ig", "acct_example_yt"],
  title: "Launch week",
  objective: "Coordinate the approved launch schedule",
  starts_at: "2026-09-01T00:00:00Z",
  ends_at: "2026-09-07T23:59:59Z",
  max_posts: 12,
  intent: "Schedule approved short-form video"
})

Observed API record

Return shape

Returns the plan record directly, including its exact state and any structured human feedback.

id · version · request_hashidentity: Stable plan identity and immutable review reference.
title · objectivestring: The submitted human-readable plan purpose.
starts_at · ends_atdatetime: The bounded plan window.
max_posts · posts_authorizedinteger: Approved capacity and posts already authorized.
source · agent · created_atmetadata: Submission source, caller context, and creation time.
brief_versioninteger | null: The retained Workspace Brief version, when supplied.
destinationsarray: Authorized account, platform, and nullable handle records.
statusplan state: One of the six exact plan states.
approval_feedbackobject | null: Decision, category, and text when a reviewer returns feedback.
outcomeobject | null: Null until the plan closes, then evidence-backed counts, top post, and available metric aggregates.

Stop conditions

Agent handoff

requires_approval

Wait for review

Stop plan-backed scheduling until a human changes the state.

changes_requested

Revise the plan

Use the returned category and text, then submit a deliberate revision.

rejected · expired · cancelled

Return control

Stop plan-backed work and return the exact state to a human.

approved

Use the boundary

Stay inside its accounts, UTC window, and remaining post capacity.