Skip to main content
Glama

Social0

delete_draft

DestructiveIdempotent

Delete an unpublished Social0 draft or scheduled post from Social0. Published/live social posts cannot be deleted with this tool — only drafts and not-yet-published schedules. Example: 'Delete yesterday's draft.'

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": {
      "post_id": "<post_id>"
    },
    "name": "delete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesDraft or scheduled post ID to delete (not a published post)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=true, idempotentHint=true, readOnlyHint=false), so the description's added value is the resource-scope rule: only unpublished drafts/scheduled posts can be removed. It does not state whether deletion is reversible or what permissions are required, which keeps it short of a 5.

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 exclusion is front-loaded in the second sentence where it matters most, and the text is short. It is slightly redundant by restating the unpublished-only rule twice, and the quoted example adds little beyond the schema, but there is no real clutter.

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?

For a one-parameter destructive tool with no output schema, the definition covers purpose, scope limits, and the destructive nature via annotations. The main omission is any statement about irreversibility or confirmation requirements, which would matter for an agent about to perform a delete.

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?

There is a single parameter with 100% schema description coverage, and the schema already says "Draft or scheduled post ID to delete (not a published post)." The description's mention of draft/scheduled posts restates that constraint rather than adding format or lookup guidance, so the baseline of 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?

The description gives a specific verb+resource ("Delete an unpublished Social0 draft or scheduled post") and immediately constrains scope by excluding published/live posts. This lets an agent distinguish it from create_draft and update_draft without inspecting either schema.

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

Usage Guidelines4/5

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

It states explicitly when the tool applies (drafts and not-yet-published schedules) and when it does not (published/live posts). The only gap is that no alternative path is named for published posts, but the exclusion itself is unambiguous.

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.