Padlet

Update Padlet Engagement

update_padlet_engagement

Changes how people respond on a padlet: comments, reactions and their emoji set, and whether posts and comments show their author and time.

get_padlet's padlet.padlet_settings.reactions_migrated decides the reactions. When true, use "emoji" with an emoji_preset, or "none", and add a vote, rating or score custom field with update_padlet_post_fields to let people vote or rate. When false, every reaction type works.
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_engagement"
  }
}

Input Schema

Name	Required	Description
`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.
`reactions`	No	Type of reaction. If reactions_migrated is true, only use 'emoji' or 'none'. Legacy types (like, vote, star, grade) are only valid when reactions_migrated is false.
`telemetry`	No	Optional. Padlet records this to improve its tools; it does not change what the tool does.
`emoji_preset`	No	Emoji preset when reactions is 'emoji'. Options: heart, thumbs_up, classic, or all.
`comments_enabled`	No	Toggle ability to comment on posts.
`show_post_attribution`	No	Toggle whether the author name, role, and timestamp is displayed on each post.
`show_comment_attribution`	No	Toggle whether the commenter name, role, and timestamp is displayed on each comment.

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 only say this is a non-read-only, non-destructive mutation with idempotentHint=false; the description goes well beyond that by disclosing partial-application semantics (applied vs. not_applied with code and reason), the failure shape when nothing changed, and an explicit instruction never to report an unapplied part as changed. That is exactly the mutation-risk context an agent needs and cannot get from the structured fields.

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?

Front-loaded purpose sentence, then three bullets that each carry distinct information (migration gate, partial-update rule, return contract). No filler, no restatement of the tool name or title.

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 ({ success, applied, not_applied }) and what each failure field means. Combined with the migration prerequisite and nested telemetry handled by the schema, an agent has everything needed to call this correctly for a 7-parameter mutation.

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; the description earns an extra point by tying reactions and emoji_preset to the reactions_migrated flag read from get_padlet and by naming the update_padlet_post_fields workaround for voting. The cross-parameter dependency is partly repeated from the schema's reactions description, which keeps it from a 5.

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?

States a concrete verb ('Changes how people respond') plus the exact settings affected: comments, reactions and emoji set, and post/comment attribution. The enumeration makes the boundary against update_padlet_appearance, update_padlet_layout and update_padlet_sharing self-evident without needing to open their schemas.

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?

Explicitly routes the agent: read padlet.padlet_settings.reactions_migrated from get_padlet first, then choose 'emoji'/'none' plus a custom field via update_padlet_post_fields when migrated, versus all reaction types when not. It also states the partial-update rule ('Pass only the settings that should change'), so both when-to-use and how-to-compose are covered.

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.