Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

substack_post

Retrieve a public Substack post's extended metadata by publication and slug, including word count, bylines, and podcast audio details; bodies are not returned.

Instructions

Get one public Substack post. Returns one public post with the extended metadata the archive listing omits, including word count, every credited byline, and podcast audio details where the post has them. Post bodies are not returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPost slug, the trailing path segment of the post URL
publicationYesPublication subdomain or custom domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does a reasonable job by stating the tool returns public posts, lists the extended metadata fields (word count, bylines, podcast details), and clearly declares that bodies are excluded. It does not, however, discuss failure behavior, pagination, or any access constraints.

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?

Three compact sentences with no filler. The key capability is front-loaded, the value-add metadata is summarized succinctly, and the critical limitation is stated plainly.

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

Completeness4/5

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

For a simple two-parameter retrieval tool, the description covers the action, the response contents, and the notable absence (post bodies). Without an output schema or annotations, a bit more detail about error cases or response shape would help, but the core usage is adequately specified.

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 parameter meanings are already fully documented. The description adds no additional parameter-level detail beyond reinforcing that the post is public.

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 opens with a specific verb and resource: 'Get one public Substack post.' It further differentiates itself from the archive listing by noting it returns extended metadata, and explicitly states that post bodies are not returned.

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

Usage Guidelines4/5

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

The description implies the main use case: retrieve a single post when the archive listing does not include the desired extended metadata. It also states a clear exclusion ('Post bodies are not returned'), helping an agent avoid using this tool for body content, though it does not name an alternative tool explicitly.

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