Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Wallpaper

update_padlet_wallpaper

Update only the padlet's wallpaper/background image.

  • Purpose: Search for and update the padlet's wallpaper based on a description.

  • 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 exactly one of wallpaper_description, to search for an image, or image_url, to use a picture the user gave or you made: the url an upload tool returned, or a public https address of an image.

  • The description should be a short phrase about the visual subject (1-3 words). Focus on what the image should depict, NOT the medium or surface.

  • Good examples: "math equations", "sunset ocean", "tropical plants", "galaxy stars".

  • Bad examples: "math equations chalkboard mathematics", "winter holiday snow background". Do NOT include words like "chalkboard", "whiteboard", "poster", "banner", "background", "wallpaper".

  • Do not include posts, sections, title, description, or settings.

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

  • If a padlet is in "map" format, NEVER use this tool.

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_dataYesInclude wallpaper_description or image_url, not both

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
    • changedInput schema / properties / wall_data / description
      Previous value: -"Only include wallpaper_description"New value: +"Include wallpaper_description or image_url, not both"
    • addedInput schema / properties / wall_data / properties / image_url
      Added value: +{
+  "description": "A picture to use as the wallpaper: the url an upload tool returned, or a public https address of an image.",
+  "type": "string"
+}
    • removedInput schema / properties / wall_data / required
      Removed value: -[
-  "wallpaper_description"
-]
  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.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the return shape for success and failure, the communication protocol before and after calling, and the important map-format restriction. These are meaningful behavioral traits not already captured by readOnlyHint, destructiveHint, idempotentHint, or openWorldHint.

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 guidance is front-loaded and most sentences earn their place, especially the examples and map-format warning. It is somewhat verbose with bullet structure and some repetition between the purpose line and schema, but it remains scannable and practical.

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?

For a mutation tool without an output schema, the description supplies the missing pieces an agent needs: return format, input selection rules, example phrasing, and a hard exclusion for map-format padlets. Nothing essential for correct invocation appears to be missing.

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 already 100%, but the description adds substantial semantic guidance beyond the schema: exactly one of the two image inputs must be supplied, the description should be a 1-3 word visual subject, and examples of good versus bad wording are provided. This materially improves correct parameter construction.

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 wallpaper/background image. It clearly distinguishes this tool from adjacent siblings such as update_padlet_appearance, update_padlet_icon, and update_padlet_layout by emphasizing that only wallpaper is changed.

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 selection guidance: include exactly one of wallpaper_description or image_url, use image_url for uploaded or public images, and never use this tool for map-format padlets. It also clarifies what not to include, such as posts, sections, title, description, or settings.

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