Build /internal toolsinternal tools/ for social media publishing and insights

Build a content calendar that schedules next week's posts across all our brand accounts, one publish job per post. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Check the remaining allowance with GET /limits first, create each post with POST /publishing/jobs (requestedPublishAt for the slot, a clientRequestId per post so retries never double-book), and render the booked week from GET /publishing/jobs with live statuses.

Build a tool that publishes one announcement to multiple social accounts. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Read connected accounts and remaining allowance, create one POST /publishing/jobs request with every approved account in targets, poll GET /publishing/jobs/{id} for per-account delivery status, and retry only failed deliveries with POST /publishing/jobs/{id}/retry. Return the accounts that were published, skipped, or need action without creating duplicate posts.

Build an X posts calendar that publishes our updates to X and cross-posts the same caption and images to Instagram in a single API call. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Validate per platform before sending (X captions fit 280 characters, at most 4 images), send one POST /publishing/jobs with both accounts in targets and a clientRequestId, and if one target fails retry only that delivery with POST /publishing/jobs/{id}/retry.

Build an Instagram publishing calendar that takes a CSV of image URLs plus captions and schedules each row, staggered every 4 hours starting tomorrow at 9am. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Multiple image URLs in one POST /publishing/jobs publish as a carousel; set requestedPublishAt per row and clientRequestId = csv hash + row index so a retried call never double-posts.

Build a failed social media post recovery flow that lists failed publish jobs, retries the retryable ones, and emails our team the rest. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Filter GET /publishing/jobs for failed statuses, read failureCategory and failureInstruction per job, retry the retryable ones with POST /publishing/jobs/{id}/retry (capped at 5, never a duplicate post), and send one digest with the rest.

Build a publishing-limits check that checks our social media publishing limits before each batch and defers posts when an account is close to its cap. Use the InvisibleAPI REST API with an organization API key (publishing:read and publishing:publish scopes). Read remainingAllowance per account from GET /limits, publish what fits with POST /publishing/jobs, schedule the rest past the reset date with requestedPublishAt, and alert us when an account crosses 90% usage.

Build an Instagram analytics dashboard that reads account insights for our connected accounts and charts them over time. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Read overview, trends, breakdowns, and audience demographics per Instagram professional account through the MCP insights tool, and store each snapshot with a timestamp since nothing is stored for you. Surface needs reconnect for any account missing the insights scopes.

Build a client reporting tool that reads each client's Instagram account insights and emails one summary per client on our reporting cycle. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Group the Instagram professional accounts by client, read each account's insights through the MCP insights tool, save each pull for month-over-month comparison, and list any account missing the insights scopes as needs reconnect instead of failing the digest.

Build an audience insights report that reads demographics for each of our Instagram accounts and compares them side by side. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Read audience demographics per Instagram professional account through the MCP insights tool, render one report per account plus a comparison, and store each snapshot with a timestamp so later runs show the change.

Build an insights exporter that pulls account insights for our Instagram accounts every Monday and appends them to a spreadsheet. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Read each account's overview, trends, and breakdowns through the MCP insights tool and append one row per account per run, stamped with the run date. The sheet becomes the history InvisibleAPI does not store for you.

Build a Claude agent that drafts next week's posts from our content brief and schedules them for my approval. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Draft one post per topic, show me the list, and wait for my approval. For each approved draft create a scheduled publish job with requestedPublishAt spread across the week and a clientRequestId per draft, then list the scheduled jobs back with their publish times. Never publish without my explicit approval.

Build an internal Instagram publishing tool and content planner based on interesting upcoming US cultural events and dates. Connect to the InvisibleAPI MCP server with an organization API key with MCP scopes, or OAuth. Read our connected Instagram professional and X accounts and the remaining allowance on each one first. Draft a caption per platform for every date, then ask me for a public media URL per post: InvisibleAPI does not upload media for you, so every image or video needs a publicly reachable sourceUrl. Organize the entire schedule into an interactive calendar view and show me the plan, with each post's target account, caption, media URL, and publishing time, before booking anything. After my explicit approval, create one scheduled publishing job per approved post with its target account, caption, public media URLs, requestedPublishAt, and a unique clientRequestId. Validate every row before booking it and never publish or schedule anything without my explicit approval.