Call the getScheduledPosts MCP tool

Read back the publishing calendar: every scheduled (and mid-publish) post in a date window, optionally for one account, ordered by publish time, with the account name, the linked document, and collision flags: two posts from the same account under 4h apart, two posts delivering the same document on one day, a post stuck in publishing, a scheduled post with no publish time, a lead-magnet hook with no campaign, or whose campaign is not active. Undated scheduled/publishing rows are ALWAYS included (they are invisible to every other read). Call this before bulk-scheduling a week and again after, to verify what you set. Defaults: from = now, to = 30 days later. Pass include_approved:true to also see approved posts that still carry a date.

Called through the Actions bridge: the response is that tool's own result, wrapped as { data: <tool result> } under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE data, never remapped to an HTTP status (see the templated /api/v1/actions/{toolName} operation above for the full protocol, and x-mcp-actions for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.