Browse docs

Configured tool · read-only

get_workspace_status

Start here to read setup progress, connection availability, accounts, policy, brief, and activity counts.

read-onlynon-destructiveclosed-world

Human and agent roles

Configured boundary

Configured workspace

This tool observes only the workspace identified by the configured agent key. It cannot unlock connections, change policy, or create credentials.

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

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
get_workspace_status({})

Observed API record

Return shape

Returns an org-scoped setup snapshot and the exact connection gate the agent must respect.

accounts[]account status[]
Connected destination IDs, platform, health, pause state, trust level, and bounded policy.
brief.versioninteger | null
Current Workspace Brief version, or null when unavailable.
counts.plansinteger
Plans stored in this workspace.
counts.postsinteger
Posts stored in this workspace.
connect_gate.stateunlocked | locked | globally_paused
The exact connection-availability state.
connect_gate.enabledboolean
Whether connect_account may be attempted now.
connect_gate.detailstring
Human-readable handoff detail preserved from the API.

Stop conditions

Agent handoff

unlocked

Inspect accounts

Call list_accounts. Use connect_account only when the requested destination is missing.

locked

Ask the human

Return connect_gate.detail exactly. The agent cannot unlock its own workspace.

globally_paused

Stop setup

Connection creation is globally paused. Do not retry around the gate.

VERIFIED · 26 AUGUST 2026GET /v1/workspace/status · get_workspace_status MCP registration

Examples are synthetic. Human workspace-key creation and revocation remain in the authenticated Accounts screen.