Skip to main content
Glama
Sign In
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a published post

unpublish_post
Destructive

Delete a published post from Facebook, YouTube, X, LinkedIn, Pinterest, Bluesky, or Google Business. Returns a preview first, then deletes only after user confirmation.

Instructions

Delete a post already published to a platform. Supported: facebook, youtube, x, linkedin, pinterest, bluesky, google_business. Instagram, TikTok, Threads and Reddit posts cannot be deleted through the API; they have to be removed in the platform's own app. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name.
postIdYesPlatform post ID to delete (Bluesky: the post AT-URI; Google Business: the full accounts/.../locations/.../localPosts/... name returned on upload).
platformYesSocial platform the post lives on.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.17.2
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Set to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.",
+  "type": "boolean"
+}
    • changedInput schema / properties / platform / description
      Previous value: -"Social platform. One of facebook, youtube, x, linkedin, threads. Instagram and TikTok are unsupported."New value: +"Social platform the post lives on."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "facebook",
-  "youtube",
-  "x",
-  "linkedin",
-  "threads"
-]New value: +[
+  "facebook",
+  "youtube",
+  "x",
+  "linkedin",
+  "pinterest",
+  "bluesky",
+  "google_business"
+]
    • changedInput schema / properties / postId / description
      Previous value: -"Platform post ID to delete."New value: +"Platform post ID to delete (Bluesky: the post AT-URI; Google Business: the full accounts/.../locations/.../localPosts/... name returned on upload)."
  2. Changed2 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Addedv0.7.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuinely new behavioral context: a two-phase preview call that sends nothing, the requirement for explicit user approval, and API-level deletion limits per platform. That is well beyond what the annotations convey and does not contradict them.

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?

Front-loaded purpose sentence, then platform support, then limitations, then the approval protocol — every sentence carries operational weight. The approval flow is restated somewhat redundantly with the `confirmed` schema description, keeping it just below top marks.

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

Completeness5/5

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

For a destructive, open-world mutation with an output schema present, the description supplies the safety protocol, the platform scope, and the exclusion set. Nothing an agent needs in order to call it correctly — including the sequencing of the two calls — is missing.

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% and the enum plus postId format notes (AT-URI, Google Business resource name) are all in the schema, so baseline 3 applies. The description reinforces the `confirmed` gate but adds no new syntax or meaning beyond what the schema already documents.

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?

Specific verb (delete) plus resource (an already-published post) and an explicit supported-platform list, which lets an agent distinguish it from upload_* and comment/management siblings without opening the schema.

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

Usage Guidelines5/5

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

States exactly when it can be used (seven named platforms) and when it cannot (Instagram, TikTok, Threads, Reddit must be removed in the platform's own app), plus the mandatory preview-then-confirm sequence. No alternatives are left to inference.

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

Deploy Server

Other Tools