Skip to main content
Glama

Update a draft

update_draft
Idempotent

Modify any part of an existing Substack draft—title, body, audience, or more—without resending unchanged fields. Works on unpublished drafts.

Instructions

Change any part of an existing draft. Only the fields you pass are touched, so you can update just the title without resending the body. Works on unpublished drafts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDraft id, from create_draft or list_drafts.
bodyNoPost body. Markdown by default. Supported: headings, bold, italic, inline code, strikethrough, links, images, nested lists (any depth, ordered and unordered mixed), fenced code blocks with a language, blockquotes and horizontal rules. Two things worth knowing: - A line containing only a YouTube, X, Spotify or Vimeo URL becomes a real embedded player, not a link. Put the URL inside a sentence if you want a plain link. - Write <paywall> on its own line to mark where the paywall starts. Everything after it is for paying subscribers only. One per post. Markdown tables have no equivalent in Substack's editor, so they are preserved verbatim in a code block rather than being mangled.
typeNoPost type. 'newsletter' is the normal long-form post.
titleNo
audienceNoWho can read it. 'everyone' is public, 'only_free' is any subscriber, 'only_paid' and 'founding' are paying tiers.
subtitleNo
section_idNo
body_formatNoHow to read `body`. 'auto' detects it and is almost always right. Use 'prosemirror' to send a Substack document directly.
cover_imageNo
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.
social_titleNo
search_engine_titleNo
search_engine_descriptionNo
Install Server

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as non-read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond the annotations: partial updates are applied only to passed fields, and the tool is restricted to unpublished drafts. This is exactly the kind of extra context an agent needs.

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 sentences, each earning its place. The core purpose is front-loaded, the key partial-update behavior is stated second, and the scope constraint is stated last. There is no filler or repetition of the schema.

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

Completeness3/5

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

The description covers the essential behavioral contract, but with 13 parameters, no output schema, and many sibling draft-related tools, it leaves some gaps: no indication of what the tool returns, no mention of validation behavior or errors, and no explicit relation to set_draft_body for body-only updates. It is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 46%, and the description does not compensate for the undocumented parameters. It mentions title and body by example, but offers no guidance on unclear parameters like section_id, cover_image, social_title, search_engine_title, or search_engine_description. The description adds useful update semantics but little parameter-level meaning.

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?

The description opens with a specific verb and resource: 'Change any part of an existing draft.' This clearly distinguishes it from create_draft (which creates) and get_draft/list_drafts (which read). It also clarifies scope by stating it works on unpublished drafts.

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?

The description gives clear guidance on when to use the tool: on existing unpublished drafts, and it explains the partial-update model ('only the fields you pass are touched'). It does not explicitly name alternatives like set_draft_body or publish_draft, but the framing makes the appropriate use case clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/navidmoazzez/substack-mcp-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server