Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a comment

delete_comment
Destructive

Permanently remove a Substack comment by its numeric ID. Requires confirm: true because the action cannot be undone.

Instructions

Delete a comment by id. Permanent, with no undo, so it refuses to run without confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true only when the user asked for exactly this action.
comment_idYesNumeric comment id.
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.2/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 they do not convey irreversibility; the description adds "Permanent, with no undo" plus the fact that the tool self-guards on confirm, which is behavior an agent cannot infer from the structured fields. It stops short of describing auth requirements or rate limits.

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, zero padding, and the destructive nature plus the confirm requirement are front-loaded before any schema reading is needed.

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 three-parameter destructive tool with full schema coverage, strong annotations, and no output schema, the description supplies the one thing structured data lacks: irreversibility and the refusal-without-confirm behavior. Nothing critical for correct invocation is 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 comment_id, confirm, and publication are already fully documented in the schema, including the publication hostname matching and default. The description reinforces the confirm contract but adds no parameter detail beyond it; 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 a comment by id") and immediately adds the two facts that matter for a destructive op: permanence and the confirm gate. The agent can distinguish it from delete_note, delete_draft, and delete_template purely from the resource noun.

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?

Gives a clear precondition for invocation (must pass confirm: true or it refuses to run), which is the key gating rule for this tool. It does not name alternatives or explicitly say when to prefer this over, say, get_comment_thread, but for a deletion endpoint the confirm rule is the operative guidance.

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