> ## Documentation Index > Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt > Use this file to discover all available pages before exploring further. # Content > LinkedIn posts: drafting, scheduling and the recurring publishing calendar. Requires the **Publish** permission. Tools in this group are hidden from `tools/list` and refused on call when your plan does not grant it. | Tool | Kind | | - | - | | [`post_generate`](#post_generate) | Read-only | | [`post_list`](#post_list) | Read-only | | [`post_schedule_get`](#post_schedule_get) | Read-only | | [`post_schedule_set`](#post_schedule_set) | Write, Destructive | | [`post_schedule_settings`](#post_schedule_settings) | Write | | [`post_upsert`](#post_upsert) | Write, Destructive | ## post\_generate Read-only Generate LinkedIn post copy from a prompt using a connected AI provider. Returns text only and stores nothing — save it with `post_upsert`, or the copy is lost when the conversation moves on. Requires an AI provider connected in the web app under Settings - Integrations. Requires the "Publish" permission on the plan. ### Parameters Which connected AI provider to use. Providers are connected in the web app. What the post should be about, and in what voice. ## post\_list Read-only Posts drafted, scheduled or published from a LinkedIn account, with their engagement numbers. Includes per-status counts. Posts published to the account's own feed — unrelated to campaign outreach, which is `campaign_list` and `analytics_campaign`. Read this before `post_upsert` to avoid creating a near-duplicate of something already queued. Requires the "Publish" permission on the plan. ### Parameters LinkedIn account id, from `linkedin_account_list`. Filter by status. ## post\_schedule\_get Read-only The recurring weekly slots at which queued posts are published for an account. The repeating timetable, not the queue: for the posts themselves use `post_list`. Change the slots with `post_schedule_set` and the timezone or approval rules with `post_schedule_settings`. Requires the "Publish" permission on the plan. ### Parameters LinkedIn account id, from `linkedin_account_list`. ## post\_schedule\_set Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Define the publishing times for one weekday. Queued posts are released into these slots. One weekday per call, and it replaces that day's times rather than adding to them — read `post_schedule_get` first. It does not schedule any particular post; that is `post_upsert` with `scheduledAt`. Requires the "Publish" permission on the plan. ### Parameters Omit to create a new slot. LinkedIn account id, from `linkedin_account_list`. Weekday, e.g. "monday". Publish times as 24-hour "HH:MM", e.g. \["09:00","17:30"]. IANA timezone for these times. CONTENT agent that fills empty slots automatically. Require human approval before an auto-generated post publishes. Whether this is live. Keep false while drafting. ## post\_schedule\_settings Write Set the timezone, the auto-drafting CONTENT agent, and whether posts need approval before publishing. Account-wide publishing policy, not times — the times are `post_schedule_set`. Attaching a CONTENT agent here lets it draft posts on its own, so confirm with the user first; the agent is configured in `agent_upsert`. Requires the "Publish" permission on the plan. ### Parameters LinkedIn account id, from `linkedin_account_list`. AI agent id, from `agent_list`. IANA timezone, e.g. "America/New\_York". Require human approval before anything auto-generated goes out. ## post\_upsert Write Destructive Marked destructive in the protocol — your MCP client asks for confirmation before running it. Draft or schedule a LinkedIn post. `status: "DRAFTED"` keeps it private; `"PENDING"` with a `scheduledAt` queues it for publishing; `"REQUIRE_APPROVAL"` routes it to a reviewer. A PENDING post with a past or imminent `scheduledAt` will go live publicly — confirm the copy with the user first. This is the only tool that saves a post. `post_generate` writes copy but stores nothing, and `post_schedule_set` defines the weekly slots a PENDING post is released into, not this post's own time. Requires the "Publish" permission on the plan. ### Parameters Omit to create a new post. Account that will publish it. Post body. Comment auto-posted underneath, e.g. a link. Image, video or document to attach. Publicly reachable URL of the image, video or document. File name, e.g. "launch-deck.pdf". Shown as the title of a document post. MIME type, e.g. "image/png", "video/mp4", "application/pdf". When to publish, as epoch milliseconds or ISO 8601. DRAFTED keeps it private; PENDING queues it for publishing. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.