substack-mcp

get_post_by_title

Retrieve a Substack post by exact or partial title match. Use the exact flag to require a precise title match when searching for a specific article.

Instructions

Get a specific post by exact or partial title match

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "get_post_by_title"
  }
}

Input Schema

Name	Required	Description	Default
`exact`	No	Require exact match (default: false)
`title`	Yes	Post title or partial title to search for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about case sensitivity, partial-match behavior, ambiguity handling when multiple posts match, or whether an exact-match result returns a single post versus a list. For a lookup tool with zero annotation coverage, these gaps matter.

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?

A single efficient sentence that front-loads the verb and resource. No filler, though it is arguably under-specified rather than minimalist.

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

Completeness2/5

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

For a two-parameter lookup with no annotations and no output schema, the description omits key behavioral details: ambiguity handling, match semantics, and return type. It is not complete enough for an agent to call it reliably without inferring behavior.

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 both parameters are documented in the schema (including the 'exact' boolean default). The description adds only a marginal restatement of 'exact or partial title match' and does not add syntax or format meaning beyond the schema baseline.

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 explicitly states a verb ('Get') and resource ('post by exact or partial title'), and clarifies the matching scope. It adequately distinguishes itself from get_post_by_url, but does not mention the pattern-matching versus list/search siblings like search_posts.

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?

No guidance on when to prefer this over search_posts, list_recent_posts, or get_post_by_url. An agent cannot tell whether this performs a lookup or a fuzzy search from the description alone.

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

Deploy Server