Padlet

Delete Padlet Items

delete_padlet_items

Destructive

Deletes posts, sections, comments and custom fields from a padlet, any mix of them in one call. It is the only tool that deletes them.

Returns { success: true } and the ids it deleted: deleted_post_ids, deleted_section_ids, deleted_comment_ids and deleted_custom_field_ids. undo says which of them can be restored.
Deleted posts and sections can be restored for 24 hours with restore_posts_and_sections, passing deleted_post_ids as its post_ids and deleted_section_ids as its section_ids. Where it is an action, run it with run_padlet_write_action. Deleted comments and custom fields cannot be restored, so tell the user before deleting them.
A deleted section takes its posts with it, and they are in deleted_post_ids. Its scheduled posts go back to drafts. The last section on a padlet cannot be deleted.
Take the ids from get_padlet: post_id and section_id from the posts, comment_id from the comments, and field_id from padlet_settings.custom_fields.
You can delete only posts and comments you wrote, unless you are a moderator or admin of the padlet. Deleting a section or a custom field needs admin permission. Nothing can be deleted while the padlet is frozen.
When some items could not be deleted, the result also has not_applied, a list of { post_id, section_id, comment_id or custom_field_id, reason }. If one post is missing or you cannot delete it, no post in the call is deleted, and likewise for sections. Tell the user which items were not deleted and why, and never say a listed item was deleted.

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": {
      "wall_url": "<wall_url>"
    },
    "name": "delete_padlet_items"
  }
}

Input Schema

Name	Required	Description
`post_ids`	No	Posts to delete.
`wall_url`	Yes	The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link, and not a padlet id: no tool takes a wall_id.
`telemetry`	No	Optional. Padlet records this to improve its tools; it does not change what the tool does.
`comment_ids`	No	Comments to delete. They cannot be restored.
`section_ids`	No	Sections to delete, with their posts.
`custom_field_ids`	No	Custom fields to delete, by field_id. They cannot be restored, and every post loses its value for them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / telemetry

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional. Padlet records this to improve its tools; it does not change what the tool does.",
+  "properties": {
+    "intent": {
+      "description": "Explain the task and why you are calling this tool. Omit full queries, large inputs, personal information, and secrets.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description still adds substantial non-redundant behavior: the 24-hour restore window, that a section delete cascades to its posts and pushes scheduled posts to drafts, that the last section cannot be deleted, and all-or-nothing semantics per item type via not_applied. Strong disclosure, though not quite exhaustive about partial failure across item types.

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 verb and scope, then organized into bullets covering returns, restore, cascade, id sources, permissions and partial failure. Dense but each bullet carries operational information; a little length comes from restating the restore path in both prose and tool names.

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?

A destructive 6-parameter tool with no output schema, yet the description documents the return shape ({ success: true } plus per-type deleted id lists), the undo flag, and the not_applied error list with its fields. An agent has everything needed to call it and to report results accurately.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by telling the agent exactly where each id comes from (post_id/section_id from posts, comment_id from comments, field_id from padlet_settings.custom_fields in get_padlet) and by explaining section_ids cascade and custom_field_ids wiping per-post values.

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 (deletes) and the exact resource set (posts, sections, comments, custom fields), including that any mix can go in one call. The claim 'It is the only tool that deletes them' lets an agent distinguish it from siblings like update_padlet_post_fields or run_padlet_destructive_action without opening another schema.

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?

Gives explicit when/when-not guidance: use restore_posts_and_sections within 24 hours for posts/sections, comments and custom fields are unrecoverable so warn the user first, and run the restore through run_padlet_write_action. It also gates usage on permissions (author for posts/comments, admin for sections/fields) and on the padlet being unfrozen.

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

All Padlet 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.