Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_post

Remove one of your own Reddit posts using its post ID. Requires user authentication to verify ownership before deletion.

Instructions

Delete your own post (requires user auth)

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": {
      "post_id": "<post_id>"
    },
    "name": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose two real traits: an auth requirement and an ownership restriction ('your own'). However, for a destructive operation it omits whether the deletion is permanent, what happens to attached comments, and the response shape.

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 compact sentence with the scope qualifier and the auth prerequisite front-loaded. Nothing is padded and there is no wasted clause.

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 one-parameter mutation with no annotations and no output schema, the description covers auth and ownership but leaves the destructive nature and downstream effects (comments, permanence) unaddressed, which is the main thing an agent needs to call it safely.

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 0%, so the schema documents nothing about post_id. The description implies the target is the caller's post, making post_id self-evident from its name, but it adds no format, ID source, or constraint detail beyond that inference.

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 (Delete) plus resource (post) and narrows scope with 'your own', which separates it from delete_comment and from edit_post in the sibling list. It is clear without naming an alternative explicitly, so it falls just short of the 5-tier benchmark.

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

Usage Guidelines3/5

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

The parenthetical '(requires user auth)' is the only routing condition, giving a bare prerequisite. There is no guidance on when to delete vs edit_post, or any caveat about irreversibly removing a post; usage is only implied.

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