Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Transfer Padlet

transfer_padlet
Destructive

  • Purpose: Transfer a padlet to another of the user's workspaces, like "Transfer board" on the padlet page. The owner stays the same.

  • What this tool returns: { success: true, wall_url, workspace } on success. workspace is { name, library_url } for a library or { personal: true }. Otherwise { success: false, message }, usually with a reason. A refusal over the workspace usually also gives available_workspaces, the workspaces that can take the padlet.

  • A transfer keeps named collaborators, removes group collaborators, and applies the new workspace's privacy rules.

Guidance for use:

  • Only the padlet's owner can transfer it. To copy a padlet instead, use remake_padlet.

  • Ask the user which workspace to transfer to 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.

  • Never pick a workspace for the user. With neither argument, nothing is transferred.

  • If the transfer is refused, tell the user why and offer the entries of available_workspaces when present.

  • Only call this tool ONCE per user request.

  • Communication: A transfer usually changes the padlet's link. You MUST give the user the returned wall_url as a markdown link: Open your padlet.

Input Schema

NameRequiredDescriptionDefault
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.
library_urlNoOptional. The padlet.com link of the library the user chose, as list_libraries or an earlier refusal gives it.

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare that this is a destructive, non-idempotent mutation. The description goes well beyond that: it discloses that existing named collaborators are kept, group collaborators are removed, new workspace privacy rules apply, and the padlet link usually changes, plus it defines both success and refusal return shapes.

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 value, then guidance bullets, with no filler sentences. It runs long, but nearly every line carries decision-relevant information; the return-shape paragraph is the densest part and could be trimmed since there is no output schema to lean on.

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 fully specifies both return shapes, including the nested workspace forms and the refusal payload with available_workspaces. Combined with the usage rules and a 3-parameter, 100%-documented schema, an agent has everything needed to invoke and report results correctly.

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 semantics the schema doesn't fully convey: the two workspace arguments are mutually exclusive and passing neither transfers nothing, and library_url should come from list_libraries or an earlier refusal's available_workspaces.

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 ('Transfer a padlet to another of the user's workspaces') and anchors it to a known UI action ('like "Transfer board"'). It also explicitly distinguishes itself from the nearest sibling, remake_padlet, which is the copy alternative.

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 rules, the owner-only prerequisite, the copy-instead alternative (remake_padlet), a prohibited behavior ('Never pick a workspace for the user'), a call-frequency limit ('Only call this tool ONCE per user request'), and what to do on refusal with available_workspaces.

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