Schedule social media posts from ChatGPT

Read connected account IDs, workspace timezone, publishing opt-in, and content pillars. Never exposes provider credentials.

Read caption, media and account requirements before drafting or scheduling. Supply an account ID for live account-specific limits.

Create a draft by default. Setting scheduled_at can create a public publishing commitment, and publish_now can publish externally; use either only after explicit user approval. Timestamps require an ISO-8601 offset. Retries may create another post because this tool is not idempotent.

Update an existing unpublished post. Omitted fields are preserved. A scheduled_at changes its public publishing commitment; publish_now publishes externally. Use either only after explicit approval. Retries can repeat a publish request, so check the post before retrying.

Tailor captions per selected platform or account. Keys are platform names or platform:account_id. Other post fields are preserved.

Read-only dry-run of publish-time validation. Leaves nothing behind: no saved post, reserved quota, upload, schedule, or publication. It uses the real validation path inside a rolled-back transaction and returns structured platform, field, code, message, and blocking issues. Use existing media IDs.

Schedule a post only after explicit user approval. This creates a future public publishing commitment. The timestamp must contain Z or an explicit timezone offset. Validates content, media and quota before scheduling; retries are safe for the same post and timestamp.

Immediately publish an existing post. Call only after the user explicitly approves immediate publication. Requires workspace agent publishing opt-in; API keys also need publish:now.

List posts in the authorized workspace with bounded pagination. Returns UTC timestamps and workspace timezone.

Read one post and its account-specific captions, publication state and validation warnings.

Permanently delete a draft or scheduled post after user approval. Refuses published posts, partially published posts and posts currently publishing.

Upload a public HTTPS URL, or raw base64 (maximum 3 MiB decoded) only for small files you already hold as bytes. Never re-encode a conversation image as base64: in ChatGPT use upload_media_file. Saved in the media library until deleted; counts toward storage quota. Use the returned media ID in posts. No redirects or private-network URLs.

ChatGPT only: import an image or video from this conversation, such as one ChatGPT generated or the user attached, into the media library. Pass the file itself; never convert it to base64. Use the returned media ID in posts. Other clients should use upload_media with a public HTTPS URL.

Show an upload widget where the user picks images or videos from their device into the media library. Use this in Claude and other clients when the user wants to attach a file that has no public URL, including a file already attached to this chat: files in your sandbox cannot be passed, so ask the user to choose the file in the widget. The widget reports the new media IDs in the conversation; list_media also shows them. In clients that cannot display widgets, such as terminals, give the user the returned upload_url to open in their browser instead. Never base64-encode the file instead.

List workspace media IDs and temporary signed preview URLs. URLs expire after five minutes; call again to refresh.

Summarize post performance for a date range: totals compared with the previous period, daily changes, results by content format and the top posts. Numbers appear about 24 hours after a post goes live and refresh daily. Some platforms report only some metrics, so a zero can mean not reported.

List lifetime metrics per published post on connected accounts, including posts made outside PostQuest. Limited to the plan history. Use sort to find the best performers.

Read one post's lifetime metrics and its day-by-day history: the cumulative totals on each day and how much each grew since the day before.

Queue a refresh of post metrics from the connected platforms. Analytics already sync every 24 hours, so call this only when the user asks for fresh numbers. Allowed once every 15 minutes per workspace; results arrive within a few minutes.