get_recent_postsFetch recent posts from a specified Substack publication using its name or URL. Supports limits and offset for paging through archives.
Recent posts from one publication.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | Skip this many posts, for paging back through the archive. | |
| publication | Yes | Publication name, subdomain, or URL (e.g. "Platformer", "platformer", "https://www.platformer.news"). |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no behavioral detail beyond the annotations, such as sorting order, pagination behavior, or whether only published posts are included. It does not contradict the annotations but also contributes no extra transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that is front-loaded and contains no fluff. It is appropriately concise for a simple read operation, though it could benefit from a few more words to add usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with only 3 parameters and no output schema, the description is mostly complete for a basic call, but it lacks guidance on how this tool differs from siblings like get_feed or search_posts. This omission makes it slightly incomplete for agent decision-making in a crowded toolset.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 67% (offset and publication have descriptions, limit does not). The description adds little beyond the schema—it repeats the 'one publication' idea but does not explain limit or offset semantics. With moderate coverage, a baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Recent posts from one publication' clearly indicates the tool returns a list of recent posts for a single publication. It is not a tautology and distinguishes from sibling tools like search_posts (which searches) and get_feed (potentially multiple publications), though it doesn't explicitly name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives such as get_feed or search_posts. The description only implies it is for a single publication, but it does not state conditions or exclusions, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.