Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Settings

update_padlet_settings

Update only the padlet's settings.

  • Purpose: Toggle padlet settings like sections, comments, reactions, and add custom fields.

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

Guidance for use:

  • Include only the fields you need to change under "settings".

  • For comments setting, use settings.comments_enabled = true/false.

  • Do not include posts/sections/title/description/wallpaper in this tool.

  • To change the padlet format/layout, use the update_padlet_layout tool instead.

  • Sections cannot be disabled on shelf (columns) format padlets. To remove sections from a shelf padlet, use the update_padlet_layout tool to change the format to grid first.

Reactions guidance (check reactions_migrated in get_padlet_content tool):

  • If reactions_migrated is true:

    • Use 'emoji' for reactions with an emoji_preset (either heart, thumbs_up, classic or all).

    • For voting/rating functionality, use custom_post_fields with field_type: 'vote', 'rating', or 'score'.

    • Do NOT use legacy reaction types (like, vote, star, grade) - they are not supported on migrated walls.

  • If reactions_migrated is false:

    • You can use any reaction type: none, like, vote, star, grade, or emoji.

Input Schema

NameRequiredDescriptionDefault
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.
wall_dataYesOnly include settings that need changing

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

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) by documenting the return contract — `{ success: true }` or a `{ success: false, message }` hash — and by disclosing server-side validation behavior (legacy reaction types are rejected on migrated walls). It does not cover permission/auth requirements or whether omitted settings are preserved, which keeps it short of a 5.

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?

Well organized with Purpose / Returns / Guidance headers and bullets, and the purpose is front-loaded. It is longer than strictly necessary: the comments_enabled bullet and the emoji_preset enumeration duplicate schema text that the agent already receives, adding bulk without new information.

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, but the description supplies the return shape and error case itself, and it covers the tricky nested custom_post_fields / selection_options territory indirectly via field_type guidance. For a partial-update mutation with a nested object parameter, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the nested settings properties are already well documented, so the baseline is 3. The description does add marginal value over the schema — the reactions_migrated dependency and the emoji_preset/custom_post_fields pairing for voting — but much of it (comments_enabled = true/false, emoji_preset options) restates what the schema already says.

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 ("Update only the padlet's settings") and immediately scopes it against the large sibling set by naming update_padlet_layout as the tool for format/layout changes and listing what this tool must not touch (posts, title, description, wallpaper). An agent can distinguish it from update_padlet_content_settings, update_padlet_appearance, and update_padlet_layout without opening any 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 when-to-use rules are given: include only fields that change, use update_padlet_layout for format changes, and change a shelf padlet to grid first before removing sections. It also gives a conditional decision procedure (check reactions_migrated via get_padlet_content, then choose emoji vs legacy reaction types), which is exactly the alternative-routing guidance this dimension rewards.

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