Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Restore Posts and Sections

restore_posts_and_sections

Restore soft-deleted posts and/or sections on a padlet.

  • Purpose: Restore posts or sections that were previously deleted (e.g. by the user or by a prior tool call). Deletions are soft-deleted, so they can be restored.

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

Guidance for use:

  • Restoring sections requires admin permission on the padlet. Restoring posts requires edit permission on each post.

  • Provide post_ids to restore specific posts, section_ids to restore specific sections, or both. At least one non-empty list is required.

  • When restoring a section AND its posts, provide BOTH the section_ids AND the post_ids. Posts are NOT automatically restored when a section is restored. Use the deleted_post_ids returned by the update_section or update_posts tool to know which post_ids to include.

  • When restoring only posts (not a section), provide post_ids.

  • Only soft-deleted items can be restored. If an id is not found or was not soft-deleted, it is skipped; others are still restored.

  • Deleted posts and sections are permanently removed after 24 hours; restore must be requested within that window.

  • Always use the exact deleted_post_ids and deleted_section_ids returned by update_section or update_posts tool call. Never guess or fabricate IDs.

  • Use get_padlet_content to see current state; soft-deleted items are not returned there. The user may ask to "undo" a deletion or "restore" something they or the assistant just deleted.

Input Schema

NameRequiredDescriptionDefault
post_idsNoIds of soft-deleted posts to restore. Omit or leave empty to restore no posts.
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.
section_idsNoIds of soft-deleted sections to restore. Omit or leave empty to restore no sections. Posts in those sections are NOT restored automatically; you must also pass their post_ids.

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. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the padlet containing the posts/sections to restore",
-  "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"
-]New value: +[
+  "wall_url"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply a generic non-read-only, non-destructive, non-idempotent profile; the description adds genuinely behavioral facts: 24-hour permanent-deletion window, skip-on-missing/not-soft-deleted semantics with partial success, permission requirements per resource, and the exact return shape including the failure hash with optional message.

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 purpose and return contract, then clearly bulletted guidance, so it scans well despite its length. It is mildly repetitive: the 'posts are NOT automatically restored with a section' rule appears twice, and the standalone 'when restoring only posts, provide post_ids' bullet restates the schema's own default.

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 mutation tool with no output schema and no rich annotations, the description covers permissions, id sourcing, partial-failure behavior, time-to-live, return shape, and verification via get_padlet_content. An agent has everything needed to call it correctly and interpret the result.

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 goes further by stating the interaction rule between post_ids and section_ids (posts are not implicitly restored with a section) and by warning never to fabricate ids but to reuse deleted_post_ids/deleted_section_ids. It adds little about wall_url formatting, which the schema already covers in detail.

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 (restore) and resource (soft-deleted posts and/or sections) scoped to a padlet, and explicitly frames the operation as the inverse of deletion. That is enough for an agent to distinguish it from update_posts, update_section, and delete-oriented siblings without opening the 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-to-use triggers (user asks to 'undo' or 'restore' something just deleted), required permissions per item type, the at-least-one-list rule, and the crucial sequencing rule that a section restore does not restore its posts so both id lists must be supplied. It also routes the agent to update_section/update_posts for the source of the ids and to get_padlet_content for current state.

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