Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update or Delete Padlet Collaborator

update_delete_padlet_collaborator_user
Destructive

  • Purpose: Update/delete a padlet collaborator user.

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

Guidance for use:

  • ALWAYS use the get_padlet_access_settings tool first to get the current access settings, including collaborators so you can get information like user id and role.

  • Only role can be updated.

  • Use the is_deleting parameter to indicate whether to delete the collaborator user. true means delete, false means update.

Input Schema

NameRequiredDescriptionDefault
roleYesThe role to grant to the collaborator. Values are: reader, commenter, writer, moderator, admin. If is_deleting is true, this is ignored.
user_idYesThe id of the user to update/delete as a collaborator for the padlet
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.
is_deletingYesWhether to delete the collaborator user. `true` means delete, `false` means update.

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 update/delete the collaborator user 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",
-  "user_id",
-  "role",
-  "is_deleting"
-]New value: +[
+  "wall_url",
+  "user_id",
+  "role",
+  "is_deleting"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description goes beyond them by disclosing the return contract ({ success: true } vs. { success: false, message }) and the fact that only one field is mutable. It doesn't state that a delete is irreversible or warn about the required permissions, which would be valuable for a destructive op.

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 with purpose, then return shape, then guidance — a sensible order with no filler prose. Minor redundancy: the is_deleting semantics are stated in both the description and the schema's own parameter description.

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 destructive four-parameter mutation with no output schema, the description covers purpose, prerequisites, mutation scope, the delete-vs-update switch, and the return shape. An agent has everything needed to call it correctly in sequence with get_padlet_access_settings.

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 schema carries the definitions; the description adds provenance for user_id (obtainable from get_padlet_access_settings), the 'only role can be updated' restriction on role, and reiterates the is_deleting true=delete/false=update mapping. That is modest added meaning above a baseline 3.

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 pair and resource: 'Update/delete a padlet collaborator user', which is unambiguous. It does not, however, contrast itself with the closely related sibling update_padlet_access_settings, so an agent must infer the boundary between per-collaborator role changes and whole-padlet access changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a hard prerequisite ('ALWAYS use the get_padlet_access_settings tool first') and a constraint ('Only role can be updated'). It also explains the is_deleting discriminator. It stops short of naming when to prefer this over invite_email_as_padlet_collaborator or update_padlet_access_settings.

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