> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt

Configured tool · write

# `account_music`

Read or set who adds the music on each connected account, and read where each handed-off video stands.

write · non-destructive · closed-world

Human and agent roles

## Configured boundary

### Configured workspace

One account changes per call, and only to postdom or (TikTok only) trending. With trending, the video goes silent to the creator's TikTok inbox at post time and the person adds a sound and posts it in TikTok. Nothing is published or deleted here.

This reference describes the hosted server at https://api.postdom.com/mcp, which runs current source, with a workspace-scoped key created under Connected apps → For developers. The published `@postdom/mcp@0.4.0` package has 14 of these tools: it lacks list_posts, create_slideshow, account_music and the media array.

Callable schema

## Input fields

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

| Field | Type | Contract |
| --- | --- | --- |
| account_id Optional | string | With music, changes that account The connected account to change. Omit it to read every account. |
| music Optional | postdom \| trending | trending is TikTok only postdom: Postdom adds the music and posts on schedule. trending: the video goes to the TikTok inbox for a trending sound. |
| post_ids Optional | string[] | Up to 100 post ids · reads only Also return each post's TikTok inbox or Instagram 'Post it myself' state. |

**For AI agents:** Send only fields exposed by the current tool schema.

**Known failure:** Do not invent platform settings, account IDs, media fields, or setup steps.

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_

```
account_music({
  account_id: "acct_example_tt",
  music: "trending"
})
```

Observed API record

## Return shape

A read returns every account's choice and the inbox holds; a change returns the changed account.

**`accounts[].account_id · platform · music · chosen` (array)** — Each account's setting, and whether a person chose it (false: the default).

**`holds[].account_id · waiting · held` (array)** — Videos waiting unposted in a TikTok inbox, and whether new TikTok videos are held back (3 waiting).

**`handoffs[]` (array)** — With post_ids: each post's handoff kind, state (requested, in_inbox, waiting, posted, marked_posted, not_posted, self_posting) and times.

**`changed` (object)** — After a change: the account's new setting, with its upcoming and in_inbox counts.

Stop conditions

## Agent handoff

`read`

### Report the settings

Say which accounts use trending and how many videos wait in each inbox.

`changed`

### Confirm the change

Report the new setting and how many upcoming posts it affects.

`held`

### Ask the person

Videos are waiting in the TikTok inbox; the person posts them in TikTok before more are sent.

 VERIFIED · 26 AUGUST 2026  **Configured MCP schema · GET /v1/music · PUT /v1/music/accounts/:id · GET /v1/music/handoffs**

Examples are synthetic. Human workspace-key creation and revocation remain in Postdom under Connected apps → For developers.