Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Publish a draft

publish_draft
Destructive

Publish a Substack draft immediately; set send=false for web-only, or email all subscribers. Requires confirm=true, and sent emails cannot be unsent.

Instructions

Publish a draft immediately. With send: true this emails every subscriber you have, and an email cannot be unsent. The post also becomes publicly visible. Refuses to run without confirm: true. To put a post live without emailing anyone, pass send: false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDraft id to publish.
sendNoEmail the post to subscribers. true sends to your whole list and cannot be undone. false publishes to the web only.
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.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint, idempotentHint=false) by spelling out the irreversible consequence ('an email cannot be unsent'), the public-visibility side effect, and the hard gate ('Refuses to run without confirm: true'). This is exactly the behavioral context an agent needs for an irreversible action.

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 sentences, front-loaded with the action and its consequence, then the gate, then the escape hatch. Every sentence carries distinct, load-bearing information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an irreversible publish tool with no output schema, the description supplies the risk profile, the confirmation requirement, and the non-emailing alternative. Combined with the annotations, an agent has everything needed to call it safely.

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, and the schema already documents all four params. The description still adds framing value by tying send: true to an irreversible broadcast and clarifying that confirm: true is a deliberate user-intent gate, not a routine flag.

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 (publish) plus resource (draft) and its effect ('becomes publicly visible'). This cleanly separates it from siblings like schedule_draft (deferred) and publish_note (a different resource), so an agent can pick it 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?

Gives explicit routing: use send: true to email everyone, pass send: false to go live without email. It does not name the sibling alternative (e.g., schedule_draft) for deferring, so it stops just short of full when/when-not guidance, but the in-tool branching is 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