Skip to main content
Glama
adaptlypost

AdaptlyPost

Official
by adaptlypost
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete Post

delete_post
Destructive

Cancel a draft or scheduled post before it publishes, or remove its record from AdaptlyPost. Published content stays live on social networks; use this to prevent an upcoming post or clean up records.

Instructions

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. Only posts in the token's workspace can be deleted; others return "Post not found or access denied". Returns { deleted: true }. Irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPost ID to delete, from list_posts or create_post

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoAn object with deleted: true once the post record is removed from AdaptlyPost.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.1.1
    • 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."
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The description goes beyond the destructiveHint annotation by explaining the irreversible nature, side effects (does not remove content from networks for COMPLETED/PARTIAL_FAILURE), and error scenario for out-of-workspace posts.

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 concise yet comprehensive, front-loading the core action and organizing status-specific behavior and alternatives without redundancy.

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?

Given the single parameter and no nested objects, the description covers all relevant contexts: statuses, side effects, error handling, and alternative tools, making it sufficient for an agent to decide when to invoke.

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

Parameters5/5

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

The only parameter 'id' is fully described in the schema, and the description adds context that it comes from list_posts or create_post, aiding in proper usage.

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 clearly states the verb (delete), resource (post record), and scope (by id). It also distinguishes when to use it for DRAFT/SCHEDULED versus other statuses, and contrasts with update_post.

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?

Explicitly states when to use (cancel DRAFT/SCHEDULED) and when not (prefer update_post for changes). It also clarifies behavior for COMPLETED/PARTIAL_FAILURE and access restrictions.

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/adaptlypost/agent'

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