Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Padlet Post Sort

update_padlet_post_sort

Update the display ORDER of posts in the padlet (e.g. newest first, oldest first, alphabetical, by custom field).

  • Purpose: Change the sort order of posts. This tool does NOT organize or categorize posts by content, topic, or theme. To do that, create sections and move relevant posts into them using update_section and update_posts instead.

  • 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:

  • 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.

Sorting by custom fields:

  • Sortable custom field types: vote, rating, score, number, date, text, single_select, multi_select.

  • On reactions_migrated walls, vote/rating are custom fields. Use custom_prop sorting instead of reactions_asc/reactions_desc.

  • To sort by a custom field, use the format: custom_prop:{field_id}:{asc or desc}

  • Get the field_id from the custom_fields in get_padlet_content (each field has a field_id).

  • Example: To sort by a vote field with field_id "abc123" in descending order, use "custom_prop:abc123:desc".

Emoji reactions:

  • Emoji reactions (e.g. heart, thumbs up) are NOT sortable. They don't have a single numeric value that can be ranked.

  • If reactions_migrated is true and the padlet uses emoji reactions, sorting by likes/reactions is not possible. Inform the user that emoji reactions cannot be sorted, and suggest adding a vote custom field if they need sortable likes.

  • NEVER use reactions_asc or reactions_desc on reactions_migrated walls.

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.
posts_sort_byYesHow to sort posts. Standard values: reactions_asc, reactions_desc, manual_new_posts_first, manual_new_posts_last, date_published_asc, date_published_desc, post_subject_asc, post_subject_desc, shuffle. For sorting by custom fields (vote, rating, score, number, date, text, single_select, multi_select), use the format: custom_prop:{field_id}:asc or custom_prop:{field_id}:desc. Get the field_id from the custom_fields in get_padlet_content. On reactions_migrated walls, use custom_prop sorting for vote/rating fields instead of reactions_asc/reactions_desc. If user does not specify order, pick one that you think would work well.

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. Changed1 schema field changed
    • changedInput schema / properties / posts_sort_by / description
      Previous value: -"How to sort posts. Standard values: reactions_asc, reactions_desc, manual_new_posts_first, manual_new_posts_last, date_published_asc, date_published_desc, post_subject_asc, post_subject_desc, shuffle. For sorting by custom fields (vote, rating, score, number, date, text, single_select), use the format: custom_prop:{field_id}:asc or custom_prop:{field_id}:desc. Get the field_id from the custom_fields in get_padlet_content. On reactions_migrated walls, use custom_prop sorting for vote/rating fields instead of reactions_asc/reactions_desc. If user does not specify order, pick one that you think would work well."New value: +"How to sort posts. Standard values: reactions_asc, reactions_desc, manual_new_posts_first, manual_new_posts_last, date_published_asc, date_published_desc, post_subject_asc, post_subject_desc, shuffle. For sorting by custom fields (vote, rating, score, number, date, text, single_select, multi_select), use the format: custom_prop:{field_id}:asc or custom_prop:{field_id}:desc. Get the field_id from the custom_fields in get_padlet_content. On reactions_migrated walls, use custom_prop sorting for vote/rating fields instead of reactions_asc/reactions_desc. If user does not specify order, pick one that you think would work well."
  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",
-  "posts_sort_by"
-]New value: +[
+  "wall_url",
+  "posts_sort_by"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the non-destructive mutation annotation, the description discloses the return shape, sortable custom field types, the custom_prop format, and the important reactions_migrated caveat. It also clarifies that emoji reactions cannot be ranked numerically.

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 is front-loaded and the bulleted structure makes the guidance easy to scan. There is some redundancy, especially repeated schema details and the reactions_migrated warning appearing twice, but the length is mostly justified by the tool's customization rules.

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 two-parameter mutation tool with no output schema, the description covers the essential return behavior, sortable values, custom-field handling, reactions limitations, and alternatives. An agent has enough information to invoke it correctly without needing further discovery.

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 both parameters are already well documented. The description repeats much of the schema's standard sort values and custom_prop format, adding only a concrete example and fallback guidance when the user does not specify an order.

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 description states a specific verb and resource: updating the display order of posts in a padlet, with examples such as newest first and alphabetical. It also explicitly distinguishes this from organizing posts by content and names the tools to use for that separate task.

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 gives explicit when-to-use and when-not-to-use guidance, including routing categorization work to update_section and update_posts. It also supplies detailed guidance for custom-field sorting and emoji reactions, including the reactions_migrated restriction.

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