PerfectPost

Update a draft

update_draft

Destructive

Updates the content or metadata of an existing unpublished draft. Only the provided fields are updated. Pass organization to move the draft to a company page, or clearOrganization to move it back to the personal profile. Works on the personal profile by default; pass organization to target a company page (see list_organizations).

Input Schema

TableJSON Schema

Name	Required	Description
`poll`	No	Poll to attach to the draft (replaces any existing media)
`title`	No	New title
`content`	No	New content in HTML
`draftId`	Yes	The identifier of the draft to update
`objective`	No	Marketing objective: tofu (awareness), mofu (consideration), bofu (conversion)
`categories`	No	New categories/tags
`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.
`clearOrganization`	No	Set to true to move a company-page draft back to the personal profile.
`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.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds genuinely useful behavioral context beyond that: patch semantics ('Only the provided fields are updated') and the relocation behavior of organization/clearOrganization. It does not mention permission needs or that attaching a poll replaces existing media, so it is not complete.

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?

Purpose is front-loaded in the first sentence and the sentences are short. The organization/default-target sentence is partly redundant with the preceding `organization`/`clearOrganization` sentence, which slightly dilutes it.

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 a 10-parameter mutation tool with nested poll/scheduledComments/scheduledReshares objects and no output schema, the description covers the primary call shape and targeting rules. The complex nested scheduling parameters are left entirely to the schema, which is acceptable given full schema coverage but leaves the description a bit thin.

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

Parameters4/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 goes beyond the schema by explaining the default targeting rule and the interactive behavior of organization vs clearOrganization, which the schema documents only separately.

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 ('Updates the content or metadata of an existing unpublished draft'). The qualifier 'unpublished draft' cleanly separates it from the sibling update_post, so an agent can route without opening either 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?

Gives the operating context: works on the personal profile by default, and pass `organization` to act on a company page, pointing to list_organizations for ids. It does not name explicit exclusions or contrast against update_post/schedule_draft, but the when-to-use context is clear.

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?