Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Whiteboard Tool Settings

update_whiteboard_tool_settings

  • Purpose: Update the whiteboard/sandbox tool settings. This tool can enable/disable ANY toolbar tool, configure AR lenses, and set video/screen recording limits.

  • Always call get_whiteboard_tool_settings tool first to get the current settings, then use this tool to update the settings.

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

  • Use whiteboard_tool_settings to enable or disable toolbar tools. Pass an array of { tool_id, enabled } objects. Only include the tools you want to change. Valid tool IDs include: "laser" (Pointer), "draw-nested" (Draw), "text" (Text), "note" (Note), "geo" (Shape), "arrow" (Connector), and padlet content tools prefixed with "padlet-" (e.g. "padlet-link", "padlet-image", "padlet-video_recorder", "padlet-screen_recorder", "padlet-audio_recorder", "padlet-photo_booth").

  • Use ar_lenses_enabled to control whether augmented reality filters are available in the video recorder.

  • Use video_length_limit to set the maximum recording length in seconds for video and screen recorder. Set to null to use the default/max limit based on the padlet owner's plan. Only the following values are allowed: 15, 30, 45, 60, 120, 180, 300, 600, 900, 1800, or null.

  • You can update all three (whiteboard_tool_settings, ar_lenses_enabled, video_length_limit) in a single call.

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.
ar_lenses_enabledNoWhether to enable augmented reality filters in the video recorder.
video_length_limitNoThe maximum recording length in seconds for video and screen recorder.
whiteboard_tool_settingsNoToolbar tools to enable or disable. Only include the tools you want to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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 sandbox/whiteboard padlet to update tool settings for",
-  "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.3/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, non-read-only, non-idempotent mutation, and the description goes beyond them by stating the return contract ({ success: true } or { success: false, message }) despite there being no output schema, plus the plan-dependent meaning of null for recording length. It stops short of stating permission requirements or whether omitted fields are left untouched.

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?

Purpose and the return contract are front-loaded, then bulleted guidance per parameter. It is longer than average, but the enumerated ID and value lists earn their space; a small amount of framing text ('Guidance for use:') could be trimmed.

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 with no output schema, the description covers when to read first, how to update partially, accepted values, and the shape of the response. Nothing an agent needs in order to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real value the schema lacks: the complete list of valid tool_id strings (schema only gives examples) and the closed set of permitted video_length_limit values (15–1800 or null), which matters since the schema declares no enums. wall_url is left entirely to the schema, which documents it well.

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?

States a specific verb and resource ('Update the whiteboard/sandbox tool settings') and enumerates the three controllable surfaces: toolbar tools, AR lenses, recording limits. It explicitly separates itself from its nearest sibling, get_whiteboard_tool_settings, though it says nothing about the many other update_padlet_* siblings.

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 sequencing ('Always call get_whiteboard_tool_settings first'), explicit partial-update rule ('Only include the tools you want to change'), an enumerated list of valid tool IDs, and the exact allowed values for video_length_limit including the null semantics. It even notes that all three settings can be changed in one call.

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