Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Pin Post

pin_post

Pin/unpin a post to the top of the padlet/section it belongs to.

  • Purpose: Pin/unpin a post to the top of the padlet/section it belongs to.

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

Guidance for use:

  • post_id should be an integer ID. It should be available through get_padlet_content tool. Things like new_1, new_abc are not valid post ids.

  • If a post was newly created using ID starting with "new_", the number part of that ID is NOT the correct post id. ALWAYS use get_padlet_content tool to get the correct post id.

Input Schema

NameRequiredDescriptionDefault
post_idYesThe integer id of the post to pin/unpin. It should be available through get_padlet_content tool.
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.
should_pinYesWhether to pin the post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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 wall containing the post to pin/unpin",
-  "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",
-  "post_id",
-  "should_pin"
-]New value: +[
+  "wall_url",
+  "post_id",
+  "should_pin"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent). The description adds return-value behavior, including the failure shape, and warns about invalid post IDs, which goes beyond 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.

Conciseness3/5

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

The critical ID guidance is front-loaded, but the opening sentence is duplicated verbatim by the 'Purpose' bullet, creating clear waste. The return-value details are useful because no output schema exists.

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?

No output schema exists, so the description appropriately explains the success/failure return shape. The ID-acquisition pitfall is well covered, and the schema fully documents wall_url. Minor gap: no use-case routing against sibling tools.

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 adds useful post_id validation context beyond the schema, explicitly warning that new_* IDs are invalid and must be resolved through get_padlet_content.

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 (pin/unpin) and resource (a post) plus where it is moved (top of the padlet/section). It does not explicitly distinguish itself from siblings, but the action is unique enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Gives clear prerequisite guidance: obtain the integer post_id via get_padlet_content, and do not use temporary new_* IDs. It does not explain when to pin/unpin versus other post-management siblings such as update_posts.

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