Skip to main content
Glama
Sign In
threads-mcp-server

threads-mcp-server

by N-Graves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

threads_delete_post

Remove a post from your Threads account by its ID. This action permanently deletes the post and cannot be undone.

Instructions

Delete one of your own posts. Irreversible.

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": "threads_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full burden for behavioral disclosure. It explicitly warns 'Irreversible,' which is a critical behavioral trait for a delete operation, and it restricts the action to the user's own posts. However, it does not mention permissions, error cases, or side effects beyond deletion.

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?

The description is two short, direct sentences with no filler or redundant information. It front-loads the core operation and immediately adds the critical irreversibility warning.

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?

For a simple one-parameter tool with no output schema, the description is largely sufficient: it defines the scope, the target resource, and the irreversibility. It could go further by noting authentication requirements or response behavior, but these are not essential for basic correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description makes no direct mention of post_id. The parameter name is self-explanatory and the phrase 'one of your own posts' implies an identifier, but the description does not add explicit semantic guidance or clarify what post_id refers to.

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?

The description states a specific verb ('Delete') and a specific resource ('one of your own posts'), making the operation unambiguous. It clearly distinguishes this tool from the sibling get/create/profile/insights tools, even without an explicit comparison.

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?

The description does not provide any when-to-use or when-not-to-use guidance, nor does it mention an alternative tool. The only implicit signal is that this is the sole delete-related tool among the siblings, but no explicit usage context or exclusions are given.

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