Skip to main content
Glama

create_draft

Create a new Substack draft post using markdown. The body is converted to Substack's format; the draft is saved without publishing.

Instructions

Create a new draft post. Accepts markdown body which is converted to Substack's format. Does NOT publish — creates a draft only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPost title
bodyNoPost body in markdown format
subtitleNoPost subtitle
audienceNoWho can see this posteveryone

Implementation Reference

  • MCP tool registration for 'create_draft' - the handler function that receives title, body, subtitle, audience; converts markdown body to ProseMirror format via markdownToProseMirror(); calls client.createDraft(); and returns the draft ID with success message.
    server.tool(
      "create_draft",
      "Create a new draft post. Accepts markdown body which is converted to Substack's format. Does NOT publish — creates a draft only.",
      {
        title: z.string().describe("Post title"),
        body: z.string().optional().describe("Post body in markdown format"),
        subtitle: z.string().optional().describe("Post subtitle"),
        audience: z
          .enum(["everyone", "only_paid", "founding", "only_free"])
          .optional()
          .default("everyone")
          .describe("Who can see this post"),
      },
      async ({ title, body, subtitle, audience }) => {
        const prosemirrorBody = body ? markdownToProseMirror(body) : undefined;
        const draft = await client.createDraft(
          title,
          prosemirrorBody,
          subtitle,
          audience,
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  id: draft.id,
                  title: draft.draft_title,
                  message: "Draft created successfully. Open Substack to review and publish.",
                },
                null,
                2,
              ),
            },
          ],
        };
      },
    );
  • SubstackClient.createDraft() - the actual API client method that constructs the DraftCreatePayload with title, optional body/subtitle, audience and type, then sends a POST request to the Substack API to create a draft.
    async createDraft(
      title: string,
      body?: string,
      subtitle?: string,
      audience: string = "everyone",
    ): Promise<SubstackDraft> {
      const payload: DraftCreatePayload = {
        draft_title: title,
        draft_bylines: [{ id: this.userId, is_guest: false }],
        audience: audience as DraftCreatePayload["audience"],
        type: "newsletter",
      };
    
      if (subtitle) payload.draft_subtitle = subtitle;
      if (body) payload.draft_body = body;
    
      return this.request<SubstackDraft>(
        `${this.publicationUrl}/api/v1/drafts`,
        {
          method: "POST",
          body: JSON.stringify(payload),
        },
      );
    }
  • DraftCreatePayload interface - defines the shape of the payload sent to the Substack API when creating a draft (draft_title, draft_subtitle, draft_body, draft_bylines, audience, type, section_id).
    export interface DraftCreatePayload {
      draft_title: string;
      draft_subtitle?: string;
      draft_body?: string;
      draft_bylines: Array<{ id: number; is_guest: boolean }>;
      audience?: "everyone" | "only_paid" | "founding" | "only_free";
      type?: "newsletter" | "podcast" | "thread";
      section_id?: number | null;
    }
  • src/server.ts:167-205 (registration)
    Tool registration via server.tool('create_draft', ...) - registers the tool with MCP server with Zod schema for input validation (title required, body/subtitle optional, audience with enum/default).
    server.tool(
      "create_draft",
      "Create a new draft post. Accepts markdown body which is converted to Substack's format. Does NOT publish — creates a draft only.",
      {
        title: z.string().describe("Post title"),
        body: z.string().optional().describe("Post body in markdown format"),
        subtitle: z.string().optional().describe("Post subtitle"),
        audience: z
          .enum(["everyone", "only_paid", "founding", "only_free"])
          .optional()
          .default("everyone")
          .describe("Who can see this post"),
      },
      async ({ title, body, subtitle, audience }) => {
        const prosemirrorBody = body ? markdownToProseMirror(body) : undefined;
        const draft = await client.createDraft(
          title,
          prosemirrorBody,
          subtitle,
          audience,
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  id: draft.id,
                  title: draft.draft_title,
                  message: "Draft created successfully. Open Substack to review and publish.",
                },
                null,
                2,
              ),
            },
          ],
        };
      },
    );
  • markdownToProseMirror() helper - converts markdown text to Substack's ProseMirror JSON format (handles headings, code blocks, horizontal rules, paragraphs with inline formatting).
    export function markdownToProseMirror(markdown: string): string {
Behavior4/5

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

With no annotations, the description fully covers key behaviors: markdown conversion, draft-only creation. It adds value beyond the schema by clarifying the tool's non-publishing nature, though it could mention return behavior.

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 sentences front-loaded with essential information. Every sentence is purposeful, no wasted words, and the negation 'does NOT publish' is placed effectively for clarity.

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?

Given 4 parameters, no output schema, and no annotations, the description provides adequate context for a creation tool. It explains conversion and draft state, though it omits mention of expected output (e.g., draft ID) or error scenarios.

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 baseline is 3. The description adds minimal extra meaning, mainly reinforcing that 'body' is markdown. It does not elaborate on the audience parameter or provide format details beyond the schema.

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 clearly states the tool creates a new draft post and explicitly notes it does not publish, using a specific verb and resource. It effectively distinguishes itself from sibling tools like update_draft and get_draft.

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 offers clear context by stating it accepts markdown and creates drafts only, implying when to use. However, it lacks explicit guidance on when not to use or direct references to alternatives among siblings.

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

Install Server

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/conorbronsdon/substack-mcp'

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