Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Appearance

update_padlet_appearance

Update the padlet's visual appearance: color scheme, post size, or font.

  • Purpose: Change how the padlet looks (color scheme, post size, font).

  • 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 want to change.

  • color_scheme: "light" or "dark". Not supported for sandbox or map padlets.

  • post_size: "standard" or "wide". Not supported for canvas, table, or sandbox padlets.

  • font: Only use this if the user explicitly specifies a font by name. If the user just wants to browse or change the font without specifying which one, do NOT call this tool — instead return the font selector widget.

    • You MUST use this JSON to translate the UI name to the font internal value for non-sandbox padlets, where the key is the UI name and the value is the internal value: {"Alps":"alps","Thames":"thames","Niagara":"niagara","Fuji":"fuji"}.

    • You MUST use this JSON to translate the UI name to the font internal value for sandbox padlets, where the key is the UI name and the value is the internal value: {"Modern":"alps","Classic":"thames","Playful":"shantell","Technical":"courier"}.

  • Do not use this tool for behavioral settings (comments, reactions, sections, custom fields) — use update_padlet_settings instead.

Input Schema

NameRequiredDescriptionDefault
fontNoSet the padlet font using the internal font name. Refer to the instructions for the mapping between UI names and internal values.
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.
post_sizeNoSet the post width. Not supported for canvas, table, or sandbox padlets.
color_schemeNoSet the padlet color scheme. Not supported for sandbox or map padlets.

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

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations (which only say non-readonly, non-destructive, non-idempotent) by documenting the exact response contract — { success: true } or { success: false, message } — despite no output schema existing. It also discloses that partial updates are supported ('Include only the fields you want to change') and which padlet types reject each field, which the annotations cannot convey.

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 summary sentence followed by labeled sections (Purpose, returns, Guidance) and bulleted per-field rules, which is easy to scan. Slight redundancy: the Purpose bullet and the return-value line restate the opening sentence, and the two embedded JSON maps add bulk, but neither is padding.

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 4-parameter mutation tool with no output schema, the description covers return values, partial-update semantics, per-type compatibility limits, name-to-value translation, and sibling routing. An agent has everything needed to invoke it correctly without inspecting the schema.

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 meaning the schema cannot: two complete UI-name-to-internal-value font mapping tables (differing for sandbox vs non-sandbox padlets) and an explicit warning that the font parameter takes an internal value, not the UI label. This prevents a concrete, likely agent error.

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?

Opens with a specific verb + resource and enumerates exactly the three visual facets it mutates (color scheme, post size, font). It explicitly differentiates from siblings: 'Do not use this tool for behavioral settings ... use update_padlet_settings instead,' and the scope cleanly excludes wallpaper, layout, and icon tools.

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?

Gives explicit when-to-use rules ('only use this if the user explicitly specifies a font by name'), a when-NOT-to-use rule ('if the user just wants to browse ... do NOT call this tool — instead return the font selector widget'), and names the correct alternative for behavioral settings. Per-field padlet-type restrictions are stated for both color_scheme and post_size.

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