suggest_times
Free times to post, with the reason for each.
- Returns
- Times with a plain reason (your numbers, or your sector's).
- Does
- Reads · scope
read - Who
- Free on every account
- Limits
- 2,000 planner calls a day per account, 200 of them writes.
- REST
GET /api/v1/times/suggest
Try it on your account
Give it to your agent
Prompt for
No key in it: your agent reads it from SOCIALSCOUT_KEY or asks you.
Read the prompt
Set up SocialScout for me and use it: Belgian social-media data (viral brand videos, Flemish creators, Meta ads and what they say, the Belgian marketing calendar, my own numbers and my content calendar), as an MCP server.
## 1. Connect
You are Claude Code. Add SocialScout as an MCP server for my user (not in this project's .mcp.json, so the key never lands in git):
claude mcp add --transport http --scope user socialscout https://socialscout.be/api/mcp --header "Authorization: Bearer $SOCIALSCOUT_KEY"
First check that SOCIALSCOUT_KEY is set (echo ${SOCIALSCOUT_KEY:+set}); the shell fills it in when the command runs.
Then tell me to run /mcp (or restart Claude Code) so the socialscout tools load.
My key: use the environment variable SOCIALSCOUT_KEY. If it is not set, ask me for my key (I find it at https://socialscout.be/me/crew, under "SocialScout inside your AI": the part after ?key=). Treat it as a password: never print it back, never put it in a file that goes into git.
What the key may do: it reads everything my plan includes and may make drafts in my calendar (scopes read + drafts). It cannot schedule, publish or touch ads: schedule_post, reschedule_post, unschedule_post and delete_post answer "needs_confirmation" with a review_url. Give me that link; nothing happens until I confirm there.
Check the connection: call corpus_stats (works without a key), then list_accounts (needs the key), and tell me in one line what you see.
## The tool: suggest_times
Free times to post, with the reason for each.
Returns: Times with a plain reason (your numbers, or your sector's).
Does: Reads · Free on every account
Limits: 2,000 planner calls a day per account, 200 of them writes.
Parameters:
- account_ids? (integer[])
- from? (string): YYYY-MM-DD (Belgian day)
- to? (string): YYYY-MM-DD (Belgian day)
- count? (integer)
## Worked example
"When should my next LinkedIn post go out?"
Call suggest_times and answer from what it returns, with the links.
## Rules
- Every claim about a video, creator, brand or ad comes from a tool result. Say so when a tool returned nothing.
- Every result carries a link to its page on socialscout.be: put it next to each name.
- "5x" or "viral" means five times the account's own normal views, not a fixed number.
- Times without an offset are Belgian time (Europe/Brussels).
- A tool that answers with a sentence instead of data is telling you what it needs (a plan, a key): pass that on, do not guess.What your agent reads
Free with any SocialScout account. Good times to post between two days, best first, each with its basis (the account's own numbers, its sector, or a common default) and the reason in words. Read-only.
| Parameter | Type | About |
|---|---|---|
account_ids | integer[] | |
from | string | YYYY-MM-DD (Belgian day) |
to | string | YYYY-MM-DD (Belgian day) |
count | integer |
More in planner
list_momentsThe Belgian marketing calendar: holidays, school breaks, sales, local events, with the day to start planning.list_accountsThe social accounts you connected, with what each can post.get_platform_rulesText and media limits per platform, as scheduling checks them.get_momentOne calendar moment in full: its dates, why it matters and how brands used it.list_calendarYour calendar between two days: drafts, scheduled and published posts.get_postOne post on your calendar, with what would stop it from going out.list_posting_timesThe posting times set for one connected account.my_overviewYour own numbers in short: reach, views, engagement and followers, free on every account.