Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post

Delete a published post

unpublish_post
Destructive

Remove a previously published post from Facebook, YouTube, X, LinkedIn, or Threads by providing the user profile, platform, and post ID.

Instructions

Delete a post already published to a platform. Instagram and TikTok are not supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesUpload-Post profile name.
postIdYesPlatform post ID to delete.
platformYesSocial platform. One of facebook, youtube, x, linkedin, threads. Instagram and TikTok are unsupported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo
Behavior3/5

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

Annotations already declare destructiveHint=true, so the 'Delete' action is expected. The description adds no further behavioral details (e.g., irreversibility, permissions, side effects). It does not contradict annotations, but adds minimal value beyond them.

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

Conciseness5/5

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

The description is a single sentence that immediately states the action and resource, then adds the key restriction on platforms. No filler, every word serves a purpose.

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?

Given the tool's simple destructive action, required parameters are fully documented in the schema, and annotations highlight its nature. The description adequately covers purpose and key exclusions. It could mention that deletion is irreversible or provide success/error behavior, but overall it's sufficient for a straightforward deletion tool.

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 coverage is 100% with detailed descriptions for all three parameters. The description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

The description uses the specific verb 'Delete' and identifies the resource as 'a post already published to a platform', clearly distinguishing its purpose from siblings like cancel_scheduled. It also explicitly states unsupported platforms (Instagram, TikTok) to narrow scope.

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

Usage Guidelines3/5

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

While the description names unsupported platforms, it does not provide explicit guidance on when to use this tool over alternatives (e.g., cancel_scheduled for scheduled posts). The context is clear but lacks direct comparison or usage conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Upload-Post/upload-post-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server