Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Title and Description

update_padlet_title_description

Update only the padlet's title and description.

  • Purpose: Update a padlet's metadata: title and description only.

  • 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 title and/or description.

  • Do not include posts, sections, wallpaper, or settings.

  • description is NOT supported for sandbox/whiteboard padlets. For sandbox padlets, only title can be updated. Do NOT pass description for sandbox padlets.

  • Communication: The user can see the result of the function call, so NEVER send a message before calling the function. After calling the function, respond with a concise one sentence confirmation.

Input Schema

NameRequiredDescriptionDefault
titleNoUpdate the title of the padlet.
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_dataNoOlder form of title and description. Send title and description at the top level instead.
descriptionNoUpdate the description of the padlet. Not supported for sandbox/whiteboard padlets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Update the description of the padlet. Not supported for sandbox/whiteboard padlets.",
+  "type": "string"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "description": "Update the title of the padlet.",
+  "type": "string"
+}
    • changedInput schema / properties / wall_data / description
      Previous value: -"Only include padlet_title and/or padlet_description. For sandbox/whiteboard padlets, only padlet_title is supported."New value: +"Older form of title and description. Send title and description at the top level instead."
    • changedInput schema / required
      Previous value: -[
-  "wall_url",
-  "wall_data"
-]New value: +[
+  "wall_url"
+]
  2. 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."
  3. 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"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish a non-readonly, non-destructive mutation; the description adds real context beyond them: the exact return shapes ({ success: true } vs. { success: false, message }), the sandbox-specific rejection of description, and the communication protocol. It stops short of stating access requirements (who may update a padlet) or what happens to fields left out, which is the main remaining behavioral gap.

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?

The structure is well front-loaded with a one-line scope statement followed by purpose, return value, and usage rules; a scanning agent gets the essentials immediately. There is minor redundancy between the opening sentence and the Purpose bullet, which prevents a perfect score.

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 no output schema, the description appropriately supplies return shapes and error behavior, plus the sandbox caveat and the post-call confirmation convention. It is nearly complete for a narrow metadata mutation, though it omits any note on required edit permissions or behavior when both fields are omitted.

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 description coverage is 100% and the schema itself documents the sandbox limitation, so the baseline is 3; the description earns an extra point by steering the caller to send only top-level title/description rather than the legacy nested wall_data object. It does not explain the required wall_url semantics, but that is fully covered in the schema.

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 states a specific verb and resource ('Update only the padlet's title and description') and immediately scopes the operation to two named metadata fields. Against a large sibling set of update_padlet_* tools (appearance, icon, layout, wallpaper, settings), this makes the boundary unmistakable.

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 inclusion rules ('Include only title and/or description'), explicit exclusions (posts, sections, wallpaper, settings), and a hard conditional: never pass description for sandbox/whiteboard padlets. It also prescribes the surrounding interaction pattern (do not message before the call, confirm in one sentence after).

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