Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Breakout Settings

update_breakout_settings

  • Purpose: Enable breakout room links on a padlet. Breakout rooms create individual links to each section, enabling collaborative group work.

  • What this tool returns:

    • { success: true } when breakout rooms are enabled successfully or already enabled.

    • { success: false, user_action_required: true, ... } when the padlet needs a layout change first. The message contains a breakout rooms widget that lets the user pick a compatible layout.

    • { success: false, message: "..." } on error.

Guidance for use:

  • Use this tool when the user wants to create separate links for each section of their padlet so different groups can work in different sections.

  • After calling this tool successfully, you MUST include the breakout rooms widget in your response using this exact format:

  • Example response: "I've enabled breakout rooms for your padlet. "

  • When this tool returns user_action_required, include the message content (which contains a breakout rooms widget with layout selection) in your response verbatim.

  • Keep your message concise (1-2 sentences) and always include the widget.

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.

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 padlet",
-  "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.4/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-read-only, non-destructive mutation) by enumerating three distinct return shapes, including the special precondition failure that requires user action, and the fact that an already-enabled padlet still returns success. It also imposes an output-format contract with the required widget markup.

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-loads purpose, then return values, then usage guidance in labeled bullets, which reads cleanly. The widget markup format is repeated three times (rule, example, and the user_action_required case), which is slightly redundant but arguably justified for exact-format compliance.

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?

No output schema exists, and the description fully compensates by documenting the return contract and the two failure modes. Combined with the post-call widget requirement, an agent has everything needed to call and handle the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds nothing about wall_url; the schema already documents it at 100% coverage, including what it is not (a breakout or submission link or padlet id). With a single well-documented parameter, the schema does all the work, so baseline 3 applies.

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 ('Enable breakout room links on a padlet') and explains what breakout rooms do, so an agent can immediately tell this apart from general settings tools. It does not name the sibling that performs the layout change, though the dependency on a layout is called out implicitly.

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 an explicit triggering condition ('when the user wants to create separate links for each section'), plus prescribed follow-up behavior after success, on the user_action_required branch, and on verbatim message handling. Little is left to inference about when and how to call it.

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