Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Icon

update_padlet_icon

Update only the padlet's icon, which is also used as its favicon.

  • Purpose: Update a padlet's icon only.

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

Guidance for use:

  • Use this tool only if the user requests to update the padlet icon and they do specify a search term or particular preference.

  • Name the padlet and include exactly one of icon_search_query, to search, or image_url, to use a picture the user gave or you made: the url an upload tool returned, or a public https address of an image.

  • Communication: The user can see the result of the function call, so NEVER send a message before calling the function. After calling the function, respond with a concise one sentence confirmation.

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.
image_urlNoA picture to use as the icon: the url an upload tool returned, or a public https address of an image.
icon_search_queryNoA query to search for an icon, prefer short and simple queries like 'train', 'car' if you think there is an emoji that can be used since we search both online images and an emoji manifest.

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. Changed2 schema fields changed
    • addedInput schema / properties / image_url
      Added value: +{
+  "description": "A picture to use as the icon: the url an upload tool returned, or a public https address of an image.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "wall_url",
-  "icon_search_query"
-]New value: +[
+  "wall_url"
+]
  3. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the wall to update",
-  "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",
-  "icon_search_query"
-]New value: +[
+  "wall_url",
+  "icon_search_query"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely new context: the exact return shape ({ success: true } or { success: false, message }), plus the interaction protocol (don't message before calling, confirm afterward). It does not say whether the previous icon is discarded or whether an existing uploaded image is retained, but for a low-risk icon swap that is a minor gap.

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?

The purpose sentence is front-loaded and the bullets split cleanly into purpose, return value, and usage rules, so an agent can scan to what it needs. It is slightly padded by the boilerplate communication instructions, and the header line partially duplicates the purpose bullet.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly compensates by spelling out both success and failure return shapes, and it covers the required wall_url pairing and the one-of icon source rule. It is complete enough to call correctly; only the prior-icon behavior on re-update is left unstated.

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 all three parameters are documented, which sets the baseline at 3. The description does add one constraint not expressible in the schema as written – exactly one of image_url or icon_search_query must be supplied, and image_url may come from an upload tool or a public https address – but it repeats the schema's own wording rather than adding much beyond it.

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?

The description states a specific verb and resource ('Update only the padlet's icon') and adds the useful detail that the icon doubles as the favicon. It scopes itself to icon-only (implying it is not the general appearance tool) but never names the obvious alternative, update_padlet_appearance, so the agent must infer the boundary from sibling names alone.

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?

It gives an explicit gate: use this tool only if the user asked to change the icon AND supplied a search term or preference. It also states the mutual-exclusivity rule ('include exactly one of icon_search_query or image_url') with a clear rationale for each, which is real routing guidance. What's missing is naming an alternative tool for the case where the user wants broader appearance changes.

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