Skip to main content
Glama
Sign In
substack-mcp

substack-mcp

by andersschaffner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_citation

Generate formatted citations for Substack blog posts in APA, MLA, Chicago, or markdown from a single URL.

Instructions

Generate a formatted citation for a blog post

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": {
      "url": "<url>"
    },
    "name": "generate_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the blog post to cite
styleNoCitation style: APA, MLA, Chicago, or markdown (default: markdown)markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing beyond the action. It does not say whether the URL is fetched live, whether any network/auth is required, whether anything is persisted, or what the output looks like, which matters for a tool with no output schema.

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?

A single economical sentence with the core action and object front-loaded. Nothing extraneous; every word earns its place.

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

Completeness3/5

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

For a simple two-parameter generation tool this is minimally adequate, but with no output schema and no annotations it should clarify what 'formatted citation' returns (e.g. a string of citation text) and whether the URL is fetched. Those gaps leave the tool usable but under-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%, with the enum of styles and default already fully documented in the schema. The description adds no syntax, format, or behavior details beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb ('Generate') and resource ('formatted citation for a blog post'), which is clearly distinct from the retrieval-focused siblings (search_posts, get_post_by_url, etc.). However, it does not explicitly name or contrast with any sibling to reinforce the distinction.

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 use this versus alternatives, no prerequisites, and no exclusions. The description only restates the action, leaving the agent to infer context from the name and siblings.

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