Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Freeze Padlet

freeze_padlet

  • Purpose: Freeze or unfreeze a padlet.

  • What this tool returns: { success: true } on successful freeze/unfreeze; otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.

  • When a padlet is frozen:

    • New posts cannot be added.

    • Existing posts cannot be edited or deleted.

    • Comments and reactions will be disabled.

    • Settings cannot be modified.

Guidance for use:

  • Use only if the user has requested to freeze now. For scheduled freezes, use the "create_automation" 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.
operation_typeYesThe operation to perform. Either to freeze or unfreeze the padlet. Possible values are: freeze, unfreeze

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 to freeze/unfreeze",
-  "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",
-  "operation_type"
-]New value: +[
+  "wall_url",
+  "operation_type"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it enumerates the concrete consequences of freezing: no new posts, no edits or deletes on existing posts, comments and reactions disabled, settings locked. It also documents the return shape ({success: true} vs. {success: false, message}), which matters since no output schema exists.

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 purpose followed by return value, effects, and usage guidance in scannable bullets; every section carries information. The '- Purpose:'/'Guidance for use:' scaffolding is slightly templated but not wasteful.

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; with high schema coverage, it correctly refrains from re-documenting parameters and instead spends its space on effects and routing. Nothing needed 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.

Parameters3/5

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

Schema coverage is 100%, so wall_url's format guidance and the freeze/unfreeze enum are already fully documented in the schema. The description only restates the binary operation and adds nothing about the parameters beyond what structured data provides, so baseline 3 applies.

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 opens with a specific verb+resource ('Freeze or unfreeze a padlet') and immediately distinguishes the operation pair via the enum-driven 'operation_type'. An agent can separate it from the many update_* siblings at a glance.

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 an explicit when-to-use rule ('Use only if the user has requested to freeze now') and names the alternative for the other case ('For scheduled freezes, use the "create_automation" tool'). This is exactly the routing guidance a sibling-heavy tool set needs.

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