> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt Agent tools · configured contract # Tool overview 17 configured tools carry an agent from workspace status and destination setup through guidance, bounded planning, execution evidence, and measurement. Exact tool names ## Configured tools The connected surface exposes exactly 17 tools. It includes setup status, account discovery, a human authorization handoff, and direct media upload; human approvals and credential management are not agent-callable. [01 `get_workspace_status` Start here to read setup progress, connection availability, accounts, policy, brief, and activity counts.](https://postdom.com/docs/tools/get-workspace-status) [02 `list_accounts` List destination account IDs and connection state, synchronizing provider state into Postdom for this workspace.](https://postdom.com/docs/tools/list-accounts) [03 `connect_account` Create a platform authorization URL for a human to complete when the workspace connection gate is unlocked.](https://postdom.com/docs/tools/connect-account) [04 `get_brief` Read the current workspace-owned brand guidance before planning or writing content.](https://postdom.com/docs/tools/get-brief) [05 `get_digest` Read the latest completed workspace week as descriptive evidence.](https://postdom.com/docs/tools/get-digest) [06 `get_learning` Read shared account learning: source-linked observations and exploratory advice for one learning scope.](https://postdom.com/docs/tools/get-learning) [07 `upload_media` Create a short-lived direct-upload contract for finished video or image bytes.](https://postdom.com/docs/tools/upload-media) [08 `get_media` Verify one uploaded media handle before publishing it.](https://postdom.com/docs/tools/get-media) [09 `submit_plan` Propose a time-bounded publication plan for one human approval.](https://postdom.com/docs/tools/submit-plan) [10 `get_plan` Read the current plan state and structured feedback from the human reviewer.](https://postdom.com/docs/tools/get-plan) [11 `publish_video` Submit finished media for immediate or UTC-scheduled execution using the current-source publish_video contract.](https://postdom.com/docs/tools/publish-video) [12 `get_publish` Read one post state, every destination outcome, and structured approval feedback.](https://postdom.com/docs/tools/get-publish) [13 `list_posts` List this workspace's posts to answer what is scheduled without already holding a post ID.](https://postdom.com/docs/tools/list-posts) [14 `get_performance` Read normalized measurements for one post or one connected account.](https://postdom.com/docs/tools/get-performance) [15 `get_best_posts` Rank one account's posts by one evidence-backed metric over a requested window.](https://postdom.com/docs/tools/get-best-posts) [16 `create_slideshow` Render carousel slides on the workspace brand kit from words and images, and store each slide as image media.](https://postdom.com/docs/tools/create-slideshow) [17 `account_music` Read or set who adds the music on each connected account, and read where each handed-off video stands.](https://postdom.com/docs/tools/account-music) Recommended sequence ## Canonical loop 1. START get_workspace_status Read setup progress and the exact connection gate before acting. 2. DISCOVER list_accounts Read connected destination IDs without guessing. 3. HANDOFF connect_account Create an authorization URL for the human when the workspace gate is unlocked. 4. READ get_brief Read workspace-owned brand guidance before planning or writing. 5. LEARN get_digest Read the latest completed week with its populations, cadence endings, and coverage gaps. 6. UPLOAD upload_media Create a short-lived contract and PUT finished bytes directly to Postdom-owned storage. 7. VERIFY get_media Continue only after the media handle reaches stored. 8. IF NEEDED submit_plan Propose bounded authority when account policy requires plan-level review. 9. IF USED get_plan Wait for exact state and structured feedback. 10. EXECUTE publish_video Submit finished media inside configured authority. 11. OBSERVE get_publish Separate post state from destination outcomes. 12. MEASURE get_performance Return normalized values with availability evidence. 13. COMPARE get_best_posts Rank only evidence-backed values and preserve exclusion reasons. Postdom Chat only ## Chat rules tools 3 more tools exist for Postdom Chat and not for a connected agent. They change the workspace's rules and the brief's Voice and Never do sections through the same versioned writes the Rules page uses, with the signed-in owner's or admin's authority, and answer every change as a before → after card. They are not on the MCP menu: the routes they write through refuse every agent credential, so an agent that needs a rule changed asks the human. [18 `set_approval_rule` Change when Postdom asks the person before posting, or pause posting, for the whole workspace or for one connected account.](https://postdom.com/docs/tools/set-approval-rule) [19 `set_posting_limits` Set how many posts a day Postdom may make and the quiet hours in which nothing goes out, for the whole workspace or for one connected account.](https://postdom.com/docs/tools/set-posting-limits) [20 `set_brand_notes` Rewrite the Voice section and/or the Never do section of the workspace brief in the person's words, leaving every other section as it is.](https://postdom.com/docs/tools/set-brand-notes) Current availability ## Access boundary ### Workspace key required A human creates the workspace and one-time agent key in Accounts, then pastes the generated MCP configuration. Agents can then upload finished video directly to workspace-scoped storage. Inspect the connected schemas before every call. Stop when a required account ID, stored media handle or accepted URL, credential, or human decision is missing. VERIFIED · 26 AUGUST 2026 **Configured MCP registration · Public truth ledger** The reference includes the 17 registered agent tools and the 3 chat rules tools, and nothing else.