Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a post

delete_post
Destructive

Delete a Bluesky post by at:// URI or bsky.app link; confirm: true is required, and the action cannot be undone.

Instructions

Delete one of your own posts. This cannot be undone, and it does not remove the post from feeds and caches that already have it. Needs confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesat:// URI or bsky.app link of the post to delete.
accountNoWhich connected account to act as, by handle (for example 'alice.bsky.social' or just 'alice'). Defaults to the first connected account. Call list_accounts to see them.
confirmNoSet true only when the user asked for exactly this action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for this to run. The result is public immediately or cannot be undone, so it is refused without an explicit confirmation."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv1.1.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=false, and the description adds genuinely new behavior: the action is irreversible and, notably, 'does not remove the post from feeds and caches that already have it'. That caching/eventual-consistency caveat is exactly the kind of nuance the agent needs and is not derivable from the annotations.

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?

Two tight sentences, front-loaded with the action and scope, then the irreversible/caching caveat, then the confirm requirement. Every clause carries information; no padding.

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 3-param mutation with full schema coverage and annotations that already flag destructiveness, the description supplies the missing pieces: irreversibility, the caching limitation, and the confirmation gate. Nothing an agent needs to invoke it safely is absent.

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%, so uri, account, and confirm are already documented, including the confirm semantics ('set true only when the user asked for exactly this action'). The description restates the confirm requirement but adds no new syntax or format detail, so the baseline 3 applies.

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 ('Delete ... post') and narrows scope with 'one of your own posts', which cleanly separates it from create_post, like_post, and the other post siblings. An agent can identify the operation and its target 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 Guidelines3/5

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

The description surfaces a real prerequisite ('Needs confirm: true') and scopes the action to the user's own posts, but gives no explicit when-to-use / when-not-to-use framing. With no sibling delete/undo tool, routing ambiguity is low, so this is adequate but not exemplary.

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