Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Restack a Note

restack_note
Destructive

Republish a Note to your followers under your name. Public and immediate, so it requires confirm: true.

Instructions

Restack a Note, which republishes it to your own followers under your name. Public and immediate, so it refuses to run without confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoFeed tab id, when the API asks for one.
confirmNoSet true only when the user asked for exactly this action.
comment_idYesNumeric Note id to restack.
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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true. The description adds genuinely new behavioral context beyond that: the action is public and immediate, and the tool hard-fails unless confirm is true. It does not clarify irreversibility or error behavior, but the confirm gate is a meaningful disclosure.

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?

A single tight sentence with an em-dash clause; the effect is front-loaded and the confirm constraint follows immediately. No filler or restated boilerplate.

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 mutation tool whose safety profile is already carried by annotations and whose parameters are fully documented, the description covers the two things an agent most needs: the public/immediate nature and the confirm gate. Missing only secondary details like undo semantics or rate limits.

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 coverage is 100%, so all four parameters are already documented, including the 'Set true only when the user asked for exactly this action' guidance on confirm. The description's restatement of the confirm requirement adds emphasis but no new format or syntax detail, so the baseline 3 applies.

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 and resource and explains the effect precisely: 'republishes it to your own followers under your name.' That is far more informative than the bare title. It does not, however, contrast itself with closely-related siblings such as publish_note or publish_note_with_link, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives one concrete precondition - 'refuses to run without confirm: true' - and characterizes the action as 'public and immediate.' But it never says when to choose this over publish_note, schedule_note, or publish_note_with_link, so alternative selection is left implicit.

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