Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Remake Padlet

remake_padlet

Remake (clone) a padlet to create a copy with configurable options.

  • Purpose: Create a copy of an existing padlet with optional content copying.

  • What this tool returns: On success, returns { success: true, wall_url: "...", workspace } with the URL of the newly created padlet. workspace is { name, library_url } for a library or { personal: true }; tell the user where the copy went. On failure, returns { success: false, message: "..." }.

Guidance for use:

  • Use this tool when the user wants to create a copy, clone, duplicate, or remake of their padlet.

  • The user must have permission to remake the padlet (they must be able to view it and the padlet must allow remaking).

  • By default, posts/objects and wallpaper are copied. Comments and reactions are not copied by default.

  • IMPORTANT: Only call this tool ONCE per user request. Even if the user asks to remake multiple times, only remake once. Inform them that you can only remake one padlet at a time.

  • The remake is performed synchronously. It may take a moment for large padlets.

  • Communication: The user cannot see tool call results directly. After calling this function, you MUST include the wall_url in your response using markdown link format: Click here to view your remade padlet.

Admin-only options:

  • with_original_authors and with_same_privacy are admin-only options that require the user to be an admin of the padlet.

  • If a non-admin user tries to use these options, the tool will return an error.

Where the copy goes:

  • Ask the user which workspace to use unless they already named one. Pass the library's library_url, or personal: true for their personal space, never both. list_libraries, when you have it as a tool or through run_padlet_read_action, gives each library's link.

  • With neither, the tool creates only when exactly one workspace can take the new padlet, and the result says which. Otherwise nothing is created, and available_workspaces lists the choices to ask about.

  • If the workspace cannot take a padlet, nothing is created and the result gives reason, message and available_workspaces. Tell the user why, ask which workspace to use, and call again with one entry's library_url or personal. Never pick one for the user.

Input Schema

NameRequiredDescriptionDefault
titleNoTitle for the new padlet. Defaults to 'Remake of {original_title}' if not provided.
personalNoOptional. true when the user chose their personal space. Never pass it with library_url.
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.
folder_idNoOptional bookmark folder id to add the remade padlet to. The folder must be owned by the user. If not provided, the remade padlet is not added to any folder.
with_postsNoWhether to copy posts/objects to the new padlet. Defaults to true.
library_urlNoOptional. The padlet.com link of the library the user chose, as list_libraries or an earlier refusal gives it.
with_commentsNoWhether to copy comments on posts. Defaults to false.
copy_wallpaperNoWhether to copy the wallpaper. If false, a random wallpaper is assigned. Defaults to true.
with_reactionsNoWhether to copy reactions (likes, votes, etc.) on posts. Defaults to false.
with_same_privacyNoAdmin only. Whether to copy privacy settings and collaborators. Defaults to false.
with_original_authorsNoAdmin only. Whether to retain original post/comment authors. Defaults to false.
translate_wall_content_toNoISO 639-1 language code to translate the remade wall content to.
with_posts_only_made_by_adminsNoOnly copy posts made by admins. Defaults to false.
with_objects_only_made_by_adminsNoOnly copy whiteboard objects made by admins. Defaults to false.

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 / library_id
      Removed value: -{
-  "description": "Target library ID for the remake. If not provided, remakes to the user's personal library.",
-  "type": "integer"
-}
    • addedInput schema / properties / library_url
      Added value: +{
+  "description": "Optional. The padlet.com link of the library the user chose, as list_libraries or an earlier refusal gives it.",
+  "type": "string"
+}
    • addedInput schema / properties / personal
      Added value: +{
+  "description": "Optional. true when the user chose their personal space. Never pass it with library_url.",
+  "type": "boolean"
+}
  3. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the wall to remake",
-  "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"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations (which only say it is a non-read-only, non-destructive, non-idempotent write), disclosing default copy semantics (posts/wallpaper yes, comments/reactions no), synchronous execution, admin-only error paths, and the full success/failure return shapes including available_workspaces on refusal.

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 shape, then cleanly sectioned bullets for guidance, admin options, and destination resolution. It is long, and a few lines (e.g. the admin-only bullet restating the schema descriptions) are mildly redundant, but for a 14-parameter tool the length is largely earned.

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?

There is no output schema, so the description carries the return contract itself — success with wall_url and workspace, failure with message and available_workspaces — and it also instructs the agent to surface the link to the user in markdown, which is the one thing an agent would otherwise omit.

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 still adds real value by clarifying the mutual exclusion of library_url and personal ('never both'), the admin-only status of with_original_authors and with_same_privacy, and how library links are obtained via list_libraries or run_padlet_read_action.

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 and resource — 'Remake (clone) a padlet to create a copy with configurable options' — and the guidance section enumerates the user intents it serves (copy, clone, duplicate, remake), which separates it from create_padlet or export_padlet without opening either 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?

Explicit about when to use, the prerequisite (user must be able to view it and the padlet must allow remaking), the admin gating for two options, and the 'only call once per user request' constraint. The workspace-resolution rules spell out when nothing is created and what to ask the user instead of guessing.

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