Skip to main content
Glama
marcomoauro

Substack MCP Server

by marcomoauro

get_analytics

Fetch Substack analytics: 16 reports on retention, unsubscribes, growth sources, referrals, audience overlap, subscriber notes, paid growth, subscriber/follower/ARR timeseries. Optional date window.

Instructions

Read one publication-level analytics report, covering the dashboard's Stats tabs: cohort retention, unsubscribes and their reasons, growth sources, referrals, audience overlap with other Substacks, subscriber Notes, paid growth, and timeseries for subscribers, followers and ARR. For per-post numbers use get_post_stats instead. Pick a report with report; the ones covering a period accept from_date and to_date and otherwise default to the last 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many rows to return. Only used by audience_overlap and subscriber_notes, which default to 6 and 8.
reportYesWhich report to read. unsubscribes — Unsubscribes in a window, broken down by the reason given. unsubscribes_timeseries — Unsubscribes over time. retention — Cohort retention: how much of each signup cohort is still subscribed months later. retention_summary — Headline retention rates at 1, 6 and 12 months. referrals_leaderboard — Which subscribers have referred the most readers. referrals_summary — Gifts sent, accepted and converted. audience_overlap — Other Substacks whose audience overlaps yours, with the overlap percentage — the publications worth collaborating with. audience_locations — How many distinct countries and US states your subscribers span. subscriber_notes — Recent Notes written by your subscribers. paid_subscriber_growth — Paid growth rate for the period, with new subscriptions and expirations. arr_timeseries — Annual recurring revenue over time. followers_timeseries — Follower count over time. subscribers_timeseries — Subscriber count over time. growth_sources — Where new subscribers came from in a window, ranked by how many each source brought. growth_events — The individual growth events in a window. network_attribution — What share of your subscribers arrived through the Substack network rather than your own channels.
to_dateNoEnd of the window, as YYYY-MM-DD. Defaults to today.
from_dateNoStart of the window, as YYYY-MM-DD. Only used by the reports that cover a period; defaults to 30 days ago, or a year ago for retention.
Behavior4/5

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

With no annotations, the description carries the disclosure burden. It states the tool is read-only ('Read'), explains report selection, and explicitly mentions date defaults (e.g., 'default to the last 30 days'). However, it does not detail edge cases like rate limits or result format, which is acceptable given the simple read nature.

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?

The description is two sentences, front-loaded with the core purpose, and includes only essential usage instructions and an alternative reference. Every clause earns its place without redundancy.

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

Completeness5/5

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

Given the tool's moderate complexity (4 params, 1 enum, no output schema), the description covers purpose, usage, report selection, date defaults, and an alternative path. It is sufficiently complete for an agent to invoke the tool correctly without additional context.

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 the baseline is 3. The description provides a high-level summary of parameter behavior ('the ones covering a period accept from_date and to_date') but does not add per-parameter meaning beyond what the schema already specifies, such as the enum values or the limit usage details.

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's function: 'Read one publication-level analytics report,' with an explicit scope covering the dashboard's Stats tabs and a list of report types. It also distinguishes itself from a sibling by directing per-post queries to get_post_stats, ensuring no ambiguity.

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

Usage Guidelines5/5

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

The description tells the agent when to use this tool versus an alternative: 'For per-post numbers use get_post_stats instead.' It also explains how to select a report and the default date behavior, providing clear context for usage.

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

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