get_best_time_to_post
Answer "when should I post?", "what's my best time to post?", "when does my audience engage?" for a platform. Returns the day-of-week and hour slots (in the user's timezone) where posts have historically performed best, ranked by their posts' median engagement, each with how many posts it is based on (limit, default 3, max 10). With too few posts it says there isn't enough data yet. This is past results, not the posting schedule: to change when queued posts go out, use list_queue_schedule and add_queue_times.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"platform": "<platform>"
},
"name": "get_best_time_to_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many time slots to return (default 3, max 10). | |
| period | No | Rolling window ending today. Default 30d. For any other window, pass start_date/end_date instead. | |
| end_date | No | Optional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date. | |
| platform | Yes | Required. The network to analyze. | |
| workspace | No | Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that. | |
| start_date | No | Optional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days. |