Skip to main content
Glama
dkships

substack-publisher-mcp

by dkships
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Post Stats

get_post_stats
Read-onlyIdempotent

Get engagement analytics for a Substack post using its URL slug, showing opens, clicks, views, new subscriptions, revenue, and media metrics.

Instructions

Get engagement statistics for a post by its URL slug: recipients, opens, clicks, views, new free and paid subscriptions, and estimated revenue increase, plus podcast and video metrics when applicable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlSlugYesThe URL slug of the post (from list_posts results or the post URL).
publicationNoPublication name (e.g., 'ny', 'la'). Required if multiple publications are configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • 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

A3.6/5.0
Behavior3/5

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

Annotations already convey read-only, idempotent, and open-world behavior, so the description does not need to restate those. It adds modest context by noting metrics are conditional ('when applicable') and revenue is 'estimated,' but it does not describe response shape or edge cases.

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 front-loads the action and resource, then compactly lists the included metrics with no filler. Every clause adds useful information.

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 simple read-only stats tool with no output schema, the description adequately enumerates the return categories and conditional metrics. The main gaps are usage alternatives and output formatting, which are already addressed in other dimensions.

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?

The input schema already documents both parameters at 100% coverage, including the urlSlug source and publication requirement. The description adds no new parameter-level meaning beyond referring to the slug, so the baseline of 3 applies.

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 states a specific verb and resource: 'Get engagement statistics for a post by its URL slug,' and enumerates the exact metrics returned. This clearly separates it from content-focused sibling get_post and from subscriber-count tools.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided. It does not explain when to prefer this over get_post or get_subscriber_counts, nor does it mention that list_posts can supply the needed slug. Usage context is only implicit in the resource type.

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