Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Delete Automations

delete_automations
Destructive

  • Purpose: Delete multiple automations on a padlet.

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

Guidance for use:

  • Do not inform the user about timezone handling. You must use a human-friendly format when displaying dates.

  • After calling this tool, you MUST include the automations widget in your response using this exact format:

  • Example response: "I've deleted the freeze automation scheduled for tomorrow at 9AM. "

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.
automation_idsYesThe ids of the automations to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the padlet where the automations are going to be deleted.",
-  "type": "integer"
-}
    • 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: -[
-  "wall_id",
-  "automation_ids"
-]New value: +[
+  "wall_url",
+  "automation_ids"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's added value is the return shape: { success: true } or { success: false, message: "..." }, which matters because there is no output schema. It also mandates a UI widget after the call, a genuinely non-obvious behavioral requirement. It does not spell out irreversibility or partial-failure semantics when only some ids are invalid.

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?

Bulleted and front-loaded with purpose and return value before the usage rules, which is the right order. The "do not inform the user about timezone handling" line is somewhat boilerplate for a delete operation, but it ties loosely to the date-bearing example response.

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 usefully covers return values, and the widget directive covers the caller's post-call obligation. The main gap is operational context for a destructive batch call: required permissions and behavior when some automation ids fail.

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% and wall_url's schema text is unusually thorough (explicitly excludes breakout/submission links and padlet ids). The description adds nothing parameter-specific beyond implying a padlet target, so the baseline 3 applies.

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 with scope: "Delete multiple automations on a padlet." The batch/plural framing separates it from create_automation and get_padlet_automations, though neither sibling is named explicitly.

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 "Guidance for use" section is entirely about response formatting (widget embedding, date display), not about when to choose this tool versus alternatives. There is no mention of needing automation ids from get_padlet_automations first, no permission prerequisites, and no when-not-to-use conditions for a destructive batch operation.

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