Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Map Style

update_padlet_map_style

Update the padlet's map style.

  • Purpose: Change the theme of a map padlet.

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

  • You MUST ONLY use this tool in padlets in the "map" format.

  • Use this tool when the user requests to change the map style specifically, or the wallpaper/background of a "map" padlet.

  • You MUST ALWAYS return a different map style than the current one.

  • Besides updating the theme, you MUST also guide the user on how to choose a different one.

  • After calling this tool, you MUST include the map style widget in your response using this exact format:

  • Example response: "You can update the map styles through the "Settings" panel. "

  • This is the list of supported themes:

  • Id: 100, Name: The Usual, Color scheme: light

  • Id: 101, Name: Silver, Color scheme: light

  • Id: 102, Name: Black Metal, Color scheme: dark

  • Id: 103, Name: Medieval, Color scheme: light

  • Id: 104, Name: Retro, Color scheme: light

  • Id: 105, Name: Tron, Color scheme: dark

  • Id: 106, Name: Night, Color scheme: dark

  • Id: 107, Name: Amusement Park, Color scheme: light

  • Id: 108, Name: Video Game, Color scheme: light

  • Id: 109, Name: Satellite, Color scheme: light

  • Id: 110, Name: Watercolor, Color scheme: light

Input Schema

NameRequiredDescriptionDefault
theme_idYesThe id of the theme to update the padlet to.
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",
-  "theme_id"
-]New value: +[
+  "wall_url",
+  "theme_id"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive mutation, and the description goes further by specifying the return shape ({ success: true } or { success: false, message }) even though no output schema exists. It also imposes post-call requirements (include the pdlt-widget snippet, guide the user). It stops short of stating permission/auth requirements or what happens with an invalid theme id.

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 bullet structure is front-loaded and scannable, and the theme list earns its length because no enum exists in the schema. There is minor redundancy between the opening line and the 'Purpose' bullet, and some agent-instruction content (widget format, example response) pads the length.

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?

With no output schema, the description supplies the return contract itself, plus format restrictions, valid theme values, and required follow-up behavior. An agent has everything needed to invoke it correctly and know what to do afterward.

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 100%, so the baseline would be 3, but the description adds a full table of 11 supported theme ids with names and color schemes — essential information the schema lacks since theme_id has no enum. wall_url semantics are covered by its schema description, so nothing is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 the padlet's map style', 'Change the theme of a map padlet') and constrains it to map-format padlets. It does not explicitly distinguish itself from the close sibling update_padlet_wallpaper, which it even mentions via 'wallpaper/background', leaving a small ambiguity an agent must resolve.

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 conditions ('when the user requests to change the map style specifically, or the wallpaper/background of a "map" padlet') and a hard precondition ('ONLY use this tool in padlets in the "map" format'). It also adds a behavioral constraint (always pick a style different from the current one) that prevents a common misuse.

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