Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Layout

update_padlet_layout

Change the padlet's format/layout.

  • Purpose: Convert a padlet to a different format/layout (e.g., from grid to timeline, stream to shelf, etc.).

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

Guidance for use:

  • You MUST use this JSON to translate the UI name to the layout internal value, where the key is the internal value and the value is the UI name: {"free":"自由格式","grid":"電子牆","matrix":"故事看板","shelf":"欄位","stream":"清單","map":"地圖","table":"表格","timeline":"時間表","timeline_v2":"行系列"}.

  • The "shelf" layout is also known as "columns". Always use "shelf" internally.

  • You must not inform the user about the logic behind the conversion.

Important:

  • You cannot convert to or from whiteboard/sandbox layout.

  • This tool only changes the layout. Use update_padlet_settings for other settings.

Input Schema

NameRequiredDescriptionDefault
layoutYes
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.

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

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds genuine context beyond that: the exact return shape for success and failure (including the optional message field), the forbidden whiteboard/sandbox conversions, and the shelf/columns aliasing. It does not disclose whether existing post positions or content are affected by a format conversion, which is the main behavioral risk an agent would want to warn a user about.

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 the operation, then organized into Purpose / Returns / Guidance / Important sections, which makes it scannable. A few lines are redundant (the Purpose bullet largely repeats the opening line, and the instruction not to reveal the conversion logic is an odd non-technical aside), but nothing is large enough to hurt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description covers the return contract, layout-name translation, and conversion restrictions — more than enough to call it correctly. The only gap is the side effect on existing posts when the format changes, which a mutation-style tool would ideally mention.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, but the description compensates strongly: it supplies a UI-name-to-internal-value mapping table that appears nowhere in the schema, and clarifies that 'columns' must be sent as 'shelf'. That is exactly the kind of meaning an agent cannot derive from the enum consts alone.

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?

The description opens with a specific verb+resource ('Change the padlet's format/layout') and the Purpose bullet restates it as a conversion operation. It also explicitly scopes itself away from the nearest sibling by stating 'This tool only changes the layout. Use update_padlet_settings for other settings.'

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?

It gives explicit when-to-use routing (settings go to update_padlet_settings), explicit exclusions ('cannot convert to or from whiteboard/sandbox layout'), and the exact translation table needed to pick a legal layout value. There is essentially no ambiguity about when and how to invoke it.

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