Skip to main content
Glama

get_subscriber_count

Retrieve the current subscriber count for a Substack publication to monitor audience growth and engagement metrics.

Instructions

Get the current subscriber count for your Substack publication

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getSubscriberCount() method in SubstackClient fetches subscriber count from Substack's publication_launch_checklist API endpoint. It handles multiple possible response formats (subscriber_count, subscriberCount, subscribers array) and returns both the count and a note indicating the data quality/source.
    async getSubscriberCount(): Promise<{ count: number; note: string }> {
      // Try multiple endpoints — Substack's API is inconsistent
      try {
        const data = await this.request<Record<string, unknown>>(
          `${this.publicationUrl}/api/v1/publication_launch_checklist`,
        );
        if (typeof data.subscriber_count === "number") {
          return { count: data.subscriber_count, note: "exact" };
        }
        if (typeof data.subscriberCount === "number") {
          return { count: data.subscriberCount, note: "exact" };
        }
        // The subscribers field is a paginated sample, not the full list
        if (Array.isArray(data.subscribers)) {
          return {
            count: data.subscribers.length,
            note: "sample only — this is a paginated subset, not the total. Check your Substack dashboard for the exact count.",
          };
        }
      } catch {
        // Fall through
      }
      return { count: -1, note: "Could not retrieve subscriber count. Check your Substack dashboard." };
    }
  • src/server.ts:14-26 (registration)
    Registration of the get_subscriber_count tool with the MCP server. The tool has an empty schema (no parameters), a description, and an async handler that calls client.getSubscriberCount() and returns the result as formatted JSON.
    server.tool(
      "get_subscriber_count",
      "Get the current subscriber count for your Substack publication",
      {},
      async () => {
        const result = await client.getSubscriberCount();
        return {
          content: [
            { type: "text", text: JSON.stringify(result, null, 2) },
          ],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without disclosing behavioral traits. It doesn't mention if this is a read-only operation, requires authentication, has rate limits, or what the return format looks like, leaving significant gaps in understanding how the tool behaves.

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 a single, well-structured sentence that directly communicates the tool's purpose with zero wasted words. It's front-loaded with the essential information and appropriately sized for a simple tool.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the return value looks like (e.g., numeric count, structured data), error conditions, or authentication requirements, leaving the agent with incomplete operational context.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose, which aligns with the baseline expectation for parameterless tools.

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 specific action ('Get') and resource ('current subscriber count for your Substack publication'), making the purpose immediately understandable. It distinguishes this tool from siblings like get_draft or get_post by focusing on subscriber metrics rather than content.

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 description implies usage context (monitoring publication metrics) but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided on prerequisites, timing, or comparisons with other tools, leaving usage decisions to inference.

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