Skip to main content
Glama
thenavidm

substack-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List your Notes

list_notes
Read-onlyIdempotent

Retrieve published Notes from a connected Substack publication in reverse chronological order, with limit and offset pagination and optional hostname selection.

Instructions

List Notes you have published, newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many to return. 1 to 50, default 20.
offsetNo
publicationNoWhich connected publication to act on, matched loosely against its hostname (for example 'example.substack.com' or just 'example'). Defaults to the first connected publication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive behavior. The description adds genuine context beyond them: the 'newest first' ordering and the 'published' scope, both useful for interpreting results. It stops short of describing pagination behavior or filtering, so a 3 is fair.

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, front-loaded sentence with zero waste. Every element (verb, scope, ordering) earns its place.

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

Completeness3/5

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

For a read-only list tool whose annotations carry the safety profile and with no output schema to explain, the definition is adequate but thin. It omits pagination behavior, the meaning of offset, and how 'published' interacts with drafts or scheduled notes.

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

Parameters2/5

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

Schema coverage is 67%, below the 80% baseline, so the description should compensate, but it says nothing about limit, offset, or publication. 'offset' has no schema description at all, leaving pagination semantics undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a clear verb ('List'), resource ('Notes'), scope ('you have published'), and ordering ('newest first'). It distinguishes a listing operation from the many note-mutation siblings like publish_note and delete_note, though it doesn't differentiate from list_scheduled_notes or research_creator_notes.

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?

There is no explicit when-to-use guidance or mention of alternatives. 'Published' implies it excludes drafts and scheduled notes, but the agent must infer this rather than being routed to list_scheduled_notes or list_drafts.

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