Crawlora MCP

substack_publication

Read-only

Get a Substack publication's public profile and complete subscription offering: every purchasable web plan with per-currency pricing, the separately priced App Store plans, per-tier benefit copy, and the toggles governing which tiers are sold. Identify it by name (subdomain such as semianalysis, or custom domain such as www.thefp.com) or by numeric publication_id -- exactly one. Prefer publication_id when you have it: it reads a compact document, while resolving by name parses the publication's full homepage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "substack_publication"
  }
}

Input Schema

Name	Required	Description	Default
`publication`	No	Publication subdomain (semianalysis) or custom domain (www.thefp.com). Provide this or publication_id.
`publication_id`	No	Numeric publication id. Cheaper and more robust than resolving by name. Provide this or publication.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: name resolution 'parses the publication's full homepage' while publication_id 'reads a compact document', telling the agent about a cost/robustness tradeoff. No return format or rate-limit details, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the payload contents, followed by identification and preference guidance in a logical order. Two sentences with little waste, though the first sentence's enumeration is dense enough to be slightly heavy.

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?

An output schema exists, so return values need no explanation; parameters and safety hints are fully covered. Nothing essential is missing, though the description repeats some schema-level detail rather than adding deeper 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?

Schema coverage is 100%, so the baseline is 3. The description adds two things the schema does not make as explicit: the mutual-exclusivity constraint ('exactly one') and the rationale for preferring publication_id over name resolution, which is meaningful selection guidance.

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?

States a specific verb and resource ('Get a Substack publication') and enumerates the exact payload (web plans with per-currency pricing, App Store plans, per-tier benefits, tier toggles). This clearly separates it from siblings like substack_publication_posts, substack_publication_contributors, and substack_publication_recommendations.

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?

Gives concrete operational guidance: identify by name or publication_id, 'exactly one', and prefer publication_id. It does not explicitly name sibling tools or state when this tool should be chosen over them, so it falls short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?