Skip to main content
Glama
dkships

substack-publisher-mcp

by dkships
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Post

get_post
Read-onlyIdempotent

Retrieve a Substack post's full content and metadata using its URL slug. Returns title, subtitle, audience, post date, cover image, authors, and body in Markdown or other formats.

Instructions

Get a post by its URL slug, including its full body. Returns post_id, title, subtitle, audience, postDate, urlSlug, coverImage, authors, and body (Markdown by default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlSlugYesThe URL slug of the post (from list_posts results or the post URL).
bodyFormatNoHow to return the body: 'markdown' (default), 'prosemirror' (the raw JSON string from the API), or 'none' to omit it and return metadata only.
publicationNoPublication name (e.g., 'ny', 'la'). Required if multiple publications are configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / bodyFormat
      Added value: +{
+  "description": "How to return the body: 'markdown' (default), 'prosemirror' (the raw JSON string from the API), or 'none' to omit it and return metadata only.",
+  "enum": [
+    "markdown",
+    "prosemirror",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / urlSlug / minLength
      Added value: +1
  2. Changed1 schema field changedv1.1.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior. The description adds value beyond those by specifying the exact return fields and the default body format (Markdown), which is useful given there is no output schema.

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 sentence that front-loads the action and then provides a compact, useful list of returned fields. No filler or redundant explanation.

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 there is no output schema, spelling out the returned fields is valuable and mostly sufficient. The minor gap is the absence of any mention of the publication disambiguation scenario, though the schema does cover it.

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?

Input schema description coverage is 100%, so the schema already documents urlSlug, bodyFormat, and publication. The description only echoes the URL-slug mechanism and Markdown default, adding no new parameter meaning 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?

States a specific verb and resource ('Get a post by its URL slug') and clarifies it returns the full body. The enumerated return fields make it easy to distinguish from sibling tools like list_posts, search_posts, and get_post_stats.

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?

The intended use case is implied by the URL-slug parameter and the nature of the tool, but there is no explicit guidance on when to use it versus alternatives like search_posts or list_posts. No exclusions or alternative routing are mentioned.

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