MCP tool

get_posting_rules

Posting rules per account

Reads only · changes nothing, and needs no approval.

What it does

The full rulebook for the accounts you are about to post to, as data — call it BEFORE building platform_configurations instead of guessing keys from prose. Per account: the same limits/can brief as list_accounts, plus options — every platform_configurations key THIS account accepts, each with kind (text | textarea | list | toggle | select), accepted values, default, max_length/max_items, placement gates (only_placement/except_placement) and a note where the key alone would mislead. A key that is ABSENT is absent because this account's connection cannot publish it — sending it anyway is refused at create time or loses the delivery, so never copy an option from one account to another. Pinterest accounts also answer boards: the live boards board_ids accepts, each { name, eligible, reason? } (null means the lookup is unavailable right now — boards can be omitted and the pin lands on Quick Saves). Pin only to boards marked eligible. An ineligible board is LISTED rather than hidden, because it is a real board someone can see on pinterest.com — but it cannot take a pin (a board made on Pinterest's sandbox refuses every real one), and sending it loses that delivery. Its reason is the sentence to repeat if you have to explain the choice.

Arguments

Calling it

Any MCP client calls this by name once the connector is added. The address is the same for every tool:

https://xpost.to/api/mcp

A client that has signed in sends the tool name and its arguments:

{
  "name": "get_posting_rules",
  "arguments": {
    "social_account_ids": []
  }
}

The other tools

Back to the MCP connector · What the MCP server is · Connect your assistant