Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Auto-Remake Settings

update_auto_remake_settings

  • Purpose: Enable, disable, or configure the autoremake link on a padlet. Autoremake links allow others to create their own copy of the padlet via a special link.

  • What this tool returns: On enable/update success, { success: true, remake_link_url: "" }. On disable success, { success: true }. Otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.

Guidance for use:

  • Use this tool when the user wants to let others remake (copy) their padlet.

  • Only set the parameters you want to change. Omit parameters to keep their current values.

  • For board padlets: use copy_posts and use_original_posts_authorship to control what gets copied.

  • For whiteboard padlets: use copy_objects instead (copy_posts and use_original_posts_authorship are ignored).

  • After calling this tool with enable: true, you MUST include the autoremake link widget in your response using this exact format, replacing REMAKE_LINK_URL with the remake_link_url from the tool result:

  • Example response: "I've enabled the autoremake link for your padlet. "

  • Keep your message concise (1-2 sentences) and always include the widget.

Input Schema

NameRequiredDescriptionDefault
enableYesWhether to enable or disable the autoremake link
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.
copy_postsNoBoard padlets only. What posts to include when remaking: all, none, or admin_only.
copy_objectsNoWhiteboard padlets only. What objects to include when remaking: all, none, admin_only, or frozen_only.
use_original_wallpaperNoWhether to copy the wallpaper design when remaking.
add_admins_as_collaboratorNoWhether to add the original padlet's admins as collaborators on remakes.
limit_to_one_remake_per_userNoWhether to limit each user to creating only one remake.
use_original_posts_authorshipNoBoard padlets only. Whether to preserve original post authorship when remaking.

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",
-  "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",
-  "enable"
-]New value: +[
+  "wall_url",
+  "enable"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing exact return shapes for enable, disable, and failure cases, plus the critical post-call obligation to render a specific widget. It also warns that certain parameters are silently ignored on whiteboard padlets, which is behavioral detail no annotation conveys.

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 purpose and return contract, then bulleted guidance and the mandatory widget format. Length is justified by the widget requirement, though the worked example response is arguably redundant with the template line above it.

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, yet the description supplies the full return contract including failure shape, and covers the non-obvious post-invocation requirement. For an 8-parameter mutation tool this leaves nothing an agent must guess.

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 already 100%, so the baseline is 3; the description earns above that by explaining partial-update semantics, the board-vs-whiteboard applicability of copy_posts / copy_objects / use_original_posts_authorship, and by surfacing remake_link_url as a return value.

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 set and resource — enable, disable, or configure the autoremake link on a padlet — and immediately defines what an autoremake link is. This separates it cleanly from sibling tools like remake_padlet (which performs a remake) and update_padlet_access_settings.

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 an explicit trigger ('when the user wants to let others remake their padlet') and important partial-update semantics ('Only set the parameters you want to change'). It also branches guidance by padlet type (board: copy_posts/use_original_posts_authorship; whiteboard: copy_objects). It stops short of naming when-not to use it or pointing to remake_padlet as the execution counterpart.

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