Skip to main content
Glama
Sign In
Substack MCP Server

Substack MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Remove comment

remove_comment
Destructive

Hide a comment on your publication post as moderator, removing its text while keeping replies visible; use delete_comment for your own comments.

Instructions

Remove someone's comment from your post as the publication's moderator.

Hides a comment on a post of your publication, as Remove in the comment menu does: readers see that a moderator removed it, the text is gone, replies under it stay. Use delete_comment for your own comments. A comment on someone else's post returns an error.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "remove_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesComment ID from list_comments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent, so the description is free to add what they cannot: readers see a moderator-removal notice, the comment text is gone, but replies underneath persist. It also discloses the moderator-role requirement and the error path for out-of-scope comments.

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 core action and sized to its content. The first sentence and the opening of the second partially restate each other ('Remove someone's comment from your post' / 'Hides a comment on a post of your publication'), which is mild redundancy.

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?

One required parameter, no output schema, and the description covers effect, audience visibility, role requirement, error condition, and the sibling alternative. The only omission is whether the removal can be reversed, which matters for a destructive operation.

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 coverage is 100% and comment_id's provenance ('from list_comments') is already documented in the schema. The description adds only indirect scoping context (your publication's post) and no format or lookup detail beyond the schema.

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?

Specific verb (remove/hide) plus resource (comment) and the exact permission scope ('as the publication's moderator'). The second paragraph defines the operation concretely as the UI's 'Remove' action, which distinguishes it unambiguously from the nearby delete_comment sibling.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use delete_comment for your own comments.' It also states a hard exclusion — a comment on someone else's post returns an error — so the agent knows both the alternative tool and the precondition for success.

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