Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a Note

delete_note
Destructive

Permanently remove a published Substack Note by ID; requires confirm: true because deletion cannot be undone.

Instructions

Delete one of your published Notes. Permanent, with no undo, so it refuses to run without confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric Note id.
confirmNoSet true only when the user asked for exactly this action.
publicationNoWhich connected publication to act on, matched loosely against its hostname (for example 'example.substack.com' or just 'example'). Defaults to the first connected publication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.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. This action 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 observedv2.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavioral facts: the operation is permanent with no undo and it self-gates on the confirm flag. It does not cover authorization requirements or what happens to a scheduled note, so it stops 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and then the irreversible consequence and its guard. Every clause carries information; nothing 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 3-parameter destructive tool with full schema coverage, annotations, and no output schema, the description supplies the safety context an agent needs (permanence, confirm gate). Minor gaps remain around permissions and failure behavior, but nothing essential for correct invocation is missing.

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 100%, so baseline is 3, and the description earns an increment by explaining the semantics of 'confirm' — that its absence causes refusal — rather than just restating the field. The 'id' and 'publication' parameters are left to the already-complete schema.

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 ... Notes') with a scope qualifier ('one of your published Notes'), which cleanly separates it from sibling deleters like delete_draft, delete_comment, and delete_template. An agent can identify the correct tool 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 Guidelines4/5

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

It gives a clear activation prerequisite — the tool 'refuses to run without confirm: true' — which tells the agent exactly what condition must hold before invoking. It does not, however, contrast this tool against the other delete_* siblings or state when deletion is preferable to unpublishing.

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