MCP: Planning
suggest_posting_times
Suggest when to post. The next times a platform's audience is usually most active, ready for publishAt. General guidance.
TL;DR
| Question | Answer |
|---|---|
| What does it do? | The next times a platform's audience is usually most active, ready for publishAt. General guidance. |
| Does it change anything? | Reads only. |
| Which endpoint does it call? | GET /v1/posting-times |
| Which server? | https://mcp.flung.dev/mcp-oauth (sign in) or https://mcp.flung.dev/mcp (API key). |
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
platform | "x" | "instagram" | "facebook" | "threads" | "linkedin" | "tiktok" | "youtube" | "pinterest" | "bluesky" | "mastodon" | "discord" | "farcaster" | yes | The social platform. |
timeZone | string | no | The audience's IANA time zone, such as Australia/Brisbane. Defaults to UTC. at most 64 characters. |
count | integer | no | minimum 1; maximum 6. |
Example call
json
{ "name": "suggest_posting_times", "arguments": { "platform": "linkedin", "timeZone": "Australia/Brisbane" }}Things a person might say
- "When should we post this on LinkedIn?"
Annotations
| Hint | Value |
|---|---|
readOnlyHint | true |
destructiveHint | false |
idempotentHint | true |
openWorldHint | false |
See also
| Doc | Why |
|---|---|
| MCP tools | Every tool |
| Connect an AI agent | Install the server in your client |
GET /v1/posting-times | The same operation over HTTP |