AdaptlyPost

Delete Comment

delete_inbox_comment

DestructiveIdempotent

Delete a comment on the platform and from the inbox, where capabilities.canDelete is true. Facebook and LinkedIn allow any comment on the Page's or organization's posts, Instagram any comment on the account's media, and YouTube, Threads, Bluesky and Mastodon only the account's own comments and replies. Anything else answers 400 inbox_action_unsupported; stop there. Returns { deleted: true }. It cannot be undone, so confirm with the user first, quoting the comment. A 403 with code inbox_reconnect_required means the account lacks the platform permission for this channel or action (some channels still wait on platform review) or its token expired: tell the user to reconnect the account in AdaptlyPost and do not retry. 404 inbox_item_not_found means the id is unknown in this workspace. 429 inbox_rate_limited means the platform rate limited the call: wait a while before trying again. 503 inbox_platform_error means the platform failed: try again later. Needs the inbox.reply permission, which Admin and Editor hold (403 permission_denied otherwise), and an active plan.

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": {
      "id": "<id>"
    },
    "name": "delete_inbox_comment"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The comment id, from list_inbox_comments
`workspaceId`	No	Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

Name	Required	Description	Default
`result`	Yes	An object with deleted: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026
- addedOutput schema / properties / result / properties / deleted / const
```
Added value: +true
```
- addedOutput schema / properties / result / properties / deleted / description
```
Added value: +"Always true: the record is gone. A delete that fails returns an error instead"
```
- changedOutput schema / properties / result / properties / deleted / type
```
Previous value: -[
-  "boolean",
-  "null"
-]New value: +"boolean"
```
- addedOutput schema / properties / result / required
```
Added value: +[
+  "deleted"
+]
```
Changed4 schema fields changedNov 9, 2026
- addedOutput schema / properties / result / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / result / properties
```
Added value: +{
+  "deleted": {
+    "type": [
+      "boolean",
+      "null"
+    ]
+  }
+}
```
- addedOutput schema / properties / result / type
```
Added value: +"object"
```
- addedOutput schema / required
```
Added value: +[
+  "result"
+]
```
AddedNov 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare destructive and non-readOnly, and the description adds substantial context on top: irreversibility with an instruction to confirm quoting the comment, the required inbox.reply permission and which roles hold it, the active-plan prerequisite, and a full error taxonomy (403 reconnect vs permission_denied, 404, 429, 503) with retry guidance. Nothing beyond the return payload is undisclosed.

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?

Purpose and irreversibility warning are front-loaded, and the error codes are grouped logically with actionable responses. It is a long single paragraph, and the trailing permission/plan sentence would read better hoisted next to the capability gate, but no sentence is filler.

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

Completeness5/5

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

For a destructive, cross-platform delete with an output schema present, the definition covers authorization, role requirements, plan state, per-platform eligibility, irreversibility, and every error branch with instructions. An agent has everything needed to decide whether to call it and how to recover if it fails.

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 the comment id (sourced from list_inbox_comments) and the workspaceId scoping rule are already fully documented in the schema. The description adds no additional parameter meaning, which matches the baseline for fully-covered schemas.

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?

States a specific verb and resource ('Delete a comment') plus the dual scope ('on the platform and from the inbox') and the capability gate ('where capabilities.canDelete is true'). That dual scope is what separates it from siblings like hide_inbox_comment, which only affects the inbox surface.

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

Usage Guidelines4/5

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

Gives per-platform applicability rules (Facebook/LinkedIn any comment on Page posts, Instagram on account media, YouTube/Threads/Bluesky/Mastodon own comments only) and an explicit stop condition when the platform rejects the target (400 inbox_action_unsupported). It never names a sibling alternative such as hide_inbox_comment, so the 'when not to delete but to hide instead' routing is left to inference.

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

All AdaptlyPost tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?