Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Delete Comment

delete_comment
Destructive

Delete a comment from a post given the comment id.

  • Purpose: Delete a comment from a post given the comment id.

  • What this tool returns: { success: true } on successful comment deletion; otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.

Guidance for use:

  • comment_id should be a string that represents an integer ID, i.e. only contain digits. If you don't know the integer ID, try getting the padlet's content first.

  • This action is irreversible. Always inform the user that deletion is permanent and confirm before proceeding.

Input Schema

NameRequiredDescriptionDefault
wall_urlYesThe 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.
comment_idYesThe id of the comment to delete. Must be a string that represents an integer ID, i.e. only contain digits. If you don't know the integer ID, try getting the padlet's content first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wall_url / description
      Previous value: -"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."New value: +"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."
  2. Changed2 schema fields changed
    • addedInput schema / properties / wall_url
      Added value: +{
+  "description": "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.",
+  "maxLength": 2048,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "comment_id"
-]New value: +[
+  "wall_url",
+  "comment_id"
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the human-facing obligation (confirm with the user, deletion is permanent) and the return contract ({ success: true } or { success: false, message }). It does not cover permission/auth requirements or partial-failure modes, but it meaningfully extends the annotation-only view.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, but there is waste: the opening sentence is immediately repeated verbatim under 'Purpose:', and the comment_id guidance duplicates the schema description word for word. The return-value and confirmation guidance do earn their place; the duplication does not.

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?

With no output schema, the description correctly supplies the return shape, and it covers the destructive-action safeguard and the id-resolution fallback. For a two-parameter mutation this is close to complete; only permissions/error-variant behavior is unstated.

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 the description's comment_id guidance ('string of digits only, fetch content if unknown') is largely a verbatim restatement of the schema field. It neither adds format or edge-case detail beyond the schema nor explains how wall_url relates to comment_id scope.

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 and resource: delete a comment from a post, identified by comment id. It is unambiguous but does no sibling differentiation — it never contrasts itself with add_comment_to_post or update_posts, leaving the agent to infer that this is the only comment-removal path.

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 real operational context: confirm with the user before deleting, warn that it is permanent, and if the integer id is unknown, fetch the padlet content first (pointing at a sibling capability). It lacks an explicit 'when not to use this' or an alternative for editing rather than removing a comment.

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

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