Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Section

update_section
Destructive

Manage sections on a padlet: create, update, delete, or reorder sections.

  • Purpose: Create new sections, update existing section titles, delete sections, or reorder sections.

  • What this tool returns: { success: true } on successful update. When new sections are created, also returns { created_section_ids: { "new_1": "123", "new_2": "456" } } mapping each temporary "new_" id to the real section id. When sections are deleted, also returns { deleted_section_ids: [...], deleted_post_ids: [...] } with the ids of the deleted sections and their posts. Otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.

  • IMPORTANT: When creating sections and then creating posts, use the real section ids from created_section_ids (not the "new_" prefixed ids) as the section_id in the create_posts tool.

  • IMPORTANT: Save these deleted_section_ids and deleted_post_ids so you can pass them to the restore_posts_and_sections tool if the user asks to undo the deletion.

Guidance for use:

  • Requires admin permission on the padlet.

  • CREATING new sections: Use a string id with "new_" prefix (e.g. "new_1", "new_abc").

  • UPDATING existing sections: Use the existing section id exactly as provided in the padlet data.

  • DELETING sections: Set should_delete to true. All posts in the section will be soft-deleted.

  • IMPORTANT: The last section on a padlet cannot be deleted. A padlet must always have at least one section.

  • REORDERING sections: Provide section_order with all section ids in the desired order.

Input Schema

NameRequiredDescriptionDefault
sectionsNoCreate, update, or delete sections. Each section has an id and title.
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_orderNoSet the order of sections. Include all section ids in the desired order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / sections / items / properties / section_title / description
      Previous value: -"Title of the section."New value: +"Title of the section. Required to create or rename a section, not to delete one."
    • changedInput schema / properties / sections / items / required
      Previous value: -[
-  "section_id",
-  "section_title"
-]New value: +[
+  "section_id"
+]
    • 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 wall to update",
-  "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 declare destructiveHint=true and non-idempotent, and the description goes well beyond them by disclosing that deletions are soft, cascade to all posts in the section, and produce recoverable ids. It also documents the exact return shapes for create/delete success and failure, including the 'new_' id mapping that materially changes how the agent must behave.

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?

The one-line summary is front-loaded and the bulleted structure is scannable. There is some redundancy — the 'Purpose' bullet largely restates the opening sentence — and the return-value paragraph is dense, though it substitutes for the missing output schema so it earns its place.

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?

No output schema exists, and the description fully specifies return payloads, the id-mapping contract, and failure shape. Combined with the permission requirement and deletion constraint, an agent has everything needed to invoke this destructive multi-operation tool safely.

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 adds real meaning on top — why temporary 'new_' ids exist, why they must not be reused as real section ids later, and that section_order must list every id. Some of this duplicates the schema field descriptions, keeping it just short of 5.

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?

Opens with a specific verb set and resource: 'create, update, delete, or reorder sections' on a padlet. The four operations are enumerated in a follow-up bullet, making it trivially distinguishable from content-level siblings like create_posts, update_posts, and update_padlet_layout.

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 per-operation instructions: 'new_' prefix ids to create, existing ids to update, should_delete=true to delete, section_order containing all ids to reorder. It also states the prerequisite ('requires admin permission'), a hard constraint ('the last section cannot be deleted'), and routes the agent to two named alternatives: create_posts for subsequent posts and restore_posts_and_sections for undo.

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