Retrieve recent Substack blog posts with limit and offset pagination. Use it to browse new content or feed posts into search, filtering, and export workflows.
List the most recent blog posts
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of posts to return (default: 10) | |
| offset | No | Number of posts to skip (default: 0) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden. "List" implies a safe read, but nothing is said about ordering (is it newest-first?), whether results are paginated, or what the response contains.
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?
A single short sentence with zero waste and the resource front-loaded after the verb. It is arguably too terse to be maximally useful, but there is no filler.
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 simple two-parameter read tool with a fully documented schema, the description is minimally adequate. It still omits ordering behavior and any hint of default result size, which an agent calling a "recent posts" list would reasonably want.
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 coverage is 100% and both limit and offset are documented in the schema with defaults. The description adds no syntax, range, or default detail, so the baseline of 3 applies.
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?
States a specific verb ("List") and resource ("blog posts") with a scope qualifier ("most recent"), so the agent knows the operation. It does not, however, distinguish itself from siblings like get_posts_by_date_range or search_posts, which could plausibly cover overlapping territory.
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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The phrase "most recent" hints at a recency-based use case but leaves the agent to infer when this beats get_posts_by_date_range or search_posts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.