# Everything for today's plan

> Call this first when the user asks what to post or do today, for today's plan or strategy, or what to focus on. One call returns the data a plan needs: what happened since the last check, recent posts against the account's normal, what's working and what isn't, growth this week, what X doesn't show (reach from replies, the follow funnel's weakest step, posts taking off right now), proven posts in the niche, who to reply to now, the queue and open slots, the best times today, Worker drafts and notes due, and account problems. It's data, not a plan: you decide what matters and build the plan. As the account's growth mentor: start with whatChanged, follow up on lastCheckIn (what was advised and how the account did since), check the raw data before advising, end with three to five follow-up questions the user can ask next, and save your diagnosis and advice with log_check_in. Each section names the tools to dig deeper with.

`today.plan` · read

- **MCP tool:** `plan_my_day`. Loaded by default in MCP clients.
- **REST:** `GET /v1/today/plan`
- **CLI:** `xholic today plan`
- **Scope:** `read`
- **Plan:** Every plan, including the trial
- **Cost:** Free.
- **Rate limit bucket:** `read`

## Input

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `timezone` | string ≤ 80 chars | No | IANA timezone for 'today'. Leave it out to use the account's scheduler timezone. |
| `account` | string ≤ 64 chars | No | X account to act on, as @handle. Leave it out to use the connection's default account. |
| `note` | string ≤ 20000 chars | No | Optional, on any tool: one or two sentences for Xholic's shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. "Dropping threads for now; focusing on replies to founders"). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people's posts. Leave it out when nothing new was said. |
