Padlet

Update Padlet Sharing

update_padlet_sharing

Destructive

Changes who can open a padlet and what they can do: the roles of its library's students and teachers and of visitors, whether visitors must log in, the password, and whether it is listed on the dashboard or published on the user's profile and the web.

The change applies at once, for everyone. A visitor_role above "none" lets anyone with the link open the padlet.
Set student_role and teacher_role together.
require_password: true with no password keeps the padlet's password, or makes one.
Collaborators are catalog actions: invite_email_as_padlet_collaborator and update_delete_padlet_collaborator_user.
Pass only the settings that should change.
Returns { success: true, applied: [part, ...] }. A part listed under not_applied, as { part, code, reason }, did not change: tell the user why, and never say it changed. When no part changed, success is false and the message gives each part's reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wall_url": "<wall_url>"
    },
    "name": "update_padlet_sharing"
  }
}

Input Schema

Name	Required	Description
`password`	No	The password to access the padlet
`wall_url`	Yes	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.
`is_listed`	No	Whether the padlet is shown on the dashboard
`telemetry`	No	Optional. Padlet records this to improve its tools; it does not change what the tool does.
`is_published`	No	Whether the padlet is shown on user profile and web
`student_role`	No	The role to grant to the student. Values are: none, reader, commenter, writer, moderator, admin.
`teacher_role`	No	The role to grant to the teacher. Values are: none, reader, commenter, writer, moderator, admin.
`visitor_role`	No	The role to grant to the visitor. Values are: none, reader, commenter, writer, moderator.
`require_login`	No	Whether the padlet requires visitor to be a logged in user
`require_password`	No	Whether the padlet requires a password to access

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / telemetry

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional. Padlet records this to improve its tools; it does not change what the tool does.",
+  "properties": {
+    "intent": {
+      "description": "Explain the task and why you are calling this tool. Omit full queries, large inputs, personal information, and secrets.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds material context the annotations cannot: the change applies at once for everyone, a visitor_role above "none" opens the padlet to anyone with the link (a real security consequence), and require_password:true without a password preserves or generates one. It also documents the response contract, { success, applied } and not_applied entries with code and reason, plus the rule never to claim an unapplied part changed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded with the resource scope, followed by short bullets each carrying one operational rule. No sentence restates the tool name or wastes space, and the failure-handling bullet near the end is the right place for it.

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 10 parameters, three enums, a nested telemetry object, and no output schema, the description must carry the return-value burden and does so explicitly. Combined with the schema's full parameter coverage and the destructive/open-world annotations, an agent has everything needed to call it and to report results honestly.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine cross-parameter semantics the schema does not state: student_role and teacher_role must be set together, and require_password interacts conditionally with password. The remaining parameters are left entirely to their schema text.

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 first sentence names a specific verb (changes) plus the full set of resources it touches: student/teacher/visitor roles, login requirement, password, listing, and publishing. That enumeration distinguishes it cleanly from siblings like update_padlet_appearance, update_padlet_layout, and update_padlet_engagement without the agent needing to open any schema.

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 states explicit usage rules ("Pass only the settings that should change", "Set student_role and teacher_role together") and routes collaborator management elsewhere by naming the actual alternatives: invite_email_as_padlet_collaborator and update_delete_padlet_collaborator_user. An agent knows both when to call this and when to call something else.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Padlet tools Inspect

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.