PerfectPost

Create a LinkedIn draft

create_draft

Creates a new LinkedIn post draft for the personal profile or, with organization, for a company page. The content is HTML: use for paragraphs and for line breaks. Works on the personal profile by default; pass organization to target a company page (see list_organizations).

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Optional draft title
`content`	Yes	Draft content in HTML
`objective`	No	Marketing objective: tofu (awareness), mofu (consideration), bofu (conversion)
`categories`	No	Categories or tags associated with the draft
`organization`	No	LinkedIn company page to act on instead of the personal profile. Pass the page id or urn returned by list_organizations, or the exact page name. Omit to target the personal profile.
`programmingDate`	No	ISO 8601 scheduling date (requires the 'publish' scope; otherwise use schedule_draft with a publish token).
`scheduledComments`	No	Comments to post automatically under the publication, each with its own delay
`scheduledReshares`	No	Reshares of the post to schedule, each with its own delay

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / scheduledReshares / items / properties / organization

Added value: +{
+  "description": "Company page that reshares the post instead of the personal profile (page id, urn or exact name, see list_organizations). Requires Premium and post rights on the page.",
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the create-but-non-destructive profile is already known. The description adds real behavioral value by specifying that content must be HTML and which tags to use (<p>, <br>), which is a formatting requirement an agent would otherwise have to guess. It stops short of covering auth/scope needs or the publish flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, followed by format then targeting. Slight redundancy: the personal-profile default and `organization` routing is stated twice, once implicitly in sentence one and again in sentence three.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter creation tool with full schema coverage and no output schema, the description covers the core invocation story (what is created, where, content format) adequately. It does not mention what is returned (e.g., a draft id needed for set_draft_media_* or schedule_draft) or the publish-scope interaction with programmingDate, though the latter is covered in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description's `organization` explanation (default profile, company page target) largely restates what the schema already says for that property, and the HTML note overlaps the `content` property description, so added meaning beyond structured fields is modest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Creates a new LinkedIn post draft') and immediately scopes the two targets: personal profile vs. company page via `organization`. An agent can distinguish this from update_draft, schedule_draft, and list_drafts without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the default behavior (personal profile) and the condition that switches targets (pass `organization`) and points to list_organizations for valid values. It does not, however, say when to prefer this over update_draft for an existing draft or how it relates to schedule_draft.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PerfectPost tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?