shapeless

Dismiss posts

posts_dismiss

Destructive

Cancel proposed, scheduled, failed, or handed-off posts without affecting published or in-progress ones. Include the user's reason to teach the agent their preferences.

Instructions

Cancel posts: proposed, scheduled, failed or handed-off. Nothing already publishing or published is touched. Pass the user's reason when they gave one; it teaches the agent their taste. Needs the write scope.

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": {
      "ids": "<ids>"
    },
    "name": "posts_dismiss"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Post ids to dismiss.
`reason`	No	Why the user skipped them, if they said.

Output Schema

Name	Required	Description	Default
`resolved`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.4Oct 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds real value beyond them: exactly which states are affected vs. spared, and that write scope is required. It doesn't cover reversibility or rate/confirmation behavior, but with annotations carrying the destructive profile this is solid extra context.

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?

Four short, front-loaded sentences. The eligible-state scope comes first, followed by the exclusion, the reason guidance, and the auth requirement. No sentence is padding.

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 destructive mutation with an output schema, the description covers scope, exclusion, auth, and optional-parameter intent, so an agent can call it correctly. Return values are handled by the output schema, leaving little 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 description coverage is 100%, so both parameters are already documented. The note 'Pass the user's reason when they gave one' reinforces the optionality of reason but adds little syntax or meaning beyond the schema's own 'if they said' description. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (cancel/dismiss) and resource (posts) and enumerates the eligible states (proposed, scheduled, failed, handed-off). It implicitly differentiates from posts_publish by stating 'Nothing already publishing or published is touched,' but never names a sibling tool to route the agent between them.

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?

Provides clear context for when the tool applies (cancel posts in the four pre-publish states) and an exclusion ('nothing already publishing or published'). It stops short of naming alternatives like posts_publish or posts_approve or stating any explicit when-not-to-use beyond the state filter.

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

Deploy Server