Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a post template

delete_template
Destructive

Permanently delete a saved Substack template after setting confirm: true. Posts already created from it remain unchanged.

Instructions

Delete a saved template. Permanent, so it refuses to run without confirm: true. Posts already created from it are unaffected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTemplate id, from list_templates.
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 non-obvious behavior: the call is hard-gated on confirm:true, and posts previously generated from the template survive the deletion. That scope-of-impact disclosure is genuine value beyond the structured fields.

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?

Three short sentences, front-loaded with the action, then the safety gate, then the side-effect scope. No filler and nothing that repeats the title.

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, non-idempotent tool with no output schema, the description covers the critical unknowns: confirmation requirement, irreversibility, and blast radius. Publication targeting and id format are handled by the schema, so nothing essential 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 the baseline is 3, but the description adds the consequence of the confirm flag ('refuses to run') and the permanence rationale, giving the flag meaning beyond the schema's terse 'Set true only when...'.

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 saved template') that cleanly separates it from the delete_note, delete_draft, and delete_comment siblings. An agent can identify the target object 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?

Explicitly states the gating condition ('refuses to run without confirm: true'), which tells the agent when the call will actually execute. It doesn't name an alternative tool for the case where the user wants to remove a draft rather than a template, but the context is otherwise clear.

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