Skip to main content
Glama

Delete Post

delete_post
DestructiveIdempotent

Delete a post record from AdaptlyPost by id. Use it to cancel a DRAFT or SCHEDULED post before it goes out; a deleted scheduled post will not publish. Deleting never removes content already on a network: for a COMPLETED or PARTIAL_FAILURE post this only drops AdaptlyPost's record, and the live posts stay up until removed on each platform. Prefer update_post to change a post instead of deleting and recreating it. A post in PUBLISHING fails with 409; wait for list_post_results to settle. Deleting a post before scheduledAt also deletes a video it already uploaded to YouTube with scheduleOnYouTube; when YouTube refuses, the delete fails with 502 SCHEDULED_VIDEO_DELETE_FAILED and the post stays, so try again, after reconnecting the channel if it was disconnected. Only posts in the workspace (the current one unless workspaceId names another) can be deleted; others return "Post not found or access denied". Returns { deleted: true }. Irreversible.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID to delete, from list_posts or create_post
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with deleted: true once the post record is removed from AdaptlyPost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / result / properties / deleted / const
      Added value: +true
    • addedOutput schema / properties / result / properties / deleted / description
      Added value: +"Always true: the record is gone. A delete that fails returns an error instead"
    • changedOutput schema / properties / result / properties / deleted / type
      Previous value: -[
      -  "boolean",
      -  "null"
      -]New value: +"boolean"
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "deleted"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "deleted": {
      +    "type": [
      +      "boolean",
      +      "null"
      +    ]
      +  }
      +}
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  3. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another"New value: +"Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another"
  5. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Post ID to delete"New value: +"Post ID to delete, from list_posts or create_post"
    • changedOutput schema / properties / result / description
      Previous value: -"The deletion confirmation for the post as returned by the AdaptlyPost API."New value: +"An object with deleted: true once the post record is removed from AdaptlyPost."
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the destructive/idempotent annotations: it states that a deleted SCHEDULED post will not publish, that COMPLETED/PARTIAL_FAILURE deletions only drop AdaptlyPost's record while live posts stay up, and the exact error contracts (409 on PUBLISHING, 502 SCHEDULED_VIDEO_DELETE_FAILED with retry/reconnect guidance, access-denied message for out-of-workspace ids). It also flags irreversibility explicitly.

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?

The critical facts — what it deletes, the DRAFT/SCHEDULED use case, and the update_post alternative — are front-loaded, and the error/permission details follow in a logical order. It is dense and somewhat run-on in the middle, but no sentence is filler.

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, cross-system operation this covers success shape ({ deleted: true }), failure codes, workspace scoping, side effects on uploaded YouTube videos, and irreversibility. With an output schema also present, an agent has everything needed to call it correctly and recover from errors.

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 coverage is already 100%, so the baseline is 3, but the description adds real meaning for workspaceId by explaining that only posts in the acting workspace are deletable and that other workspaces yield "Post not found or access denied". The id parameter gains no new semantics beyond the schema's note about list_posts/create_post.

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?

Opens with a specific verb+resource+scope: "Delete a post record from AdaptlyPost by id." It immediately distinguishes itself from near-neighbours by naming update_post as the mutation alternative and by scoping the tool to post records rather than recurring posts or inbox items.

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?

Gives explicit when-to-use ("cancel a DRAFT or SCHEDULED post before it goes out"), when-not-to-use ("Prefer update_post to change a post instead of deleting and recreating it"), and a concrete blocking condition with the remedy (PUBLISHING → 409, wait for list_post_results to settle). Nothing about selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources