Skip to main content
Glama

Update Padlet Layout

update_padlet_layout

Changes how a padlet arranges its posts: its format, whether posts are grouped into sections, and their sort order.

  • layout takes the internal name, the one get_padlet reports as padlet_settings.format. By the name the user sees: {"Freeform":"free","Wall":"grid","Grid":"matrix","Columns":"shelf","Stream":"stream","Map":"map","Table":"table","Timeline":"timeline","Rows":"timeline_v2"}. A sandbox padlet cannot change format.

  • 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_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutNo
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.
telemetryNoOptional. Padlet records this to improve its tools; it does not change what the tool does.
posts_sort_byNoHow 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 the padlet's 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.
sections_enabledNoToggle sections visibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +}
  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, 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."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 the padlet's 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. Changed1 schema field changed
    • changedInput schema / properties / layout / oneOf
      Previous value: -[
      -  {
      -    "const": "free",
      -    "description": "Freeform canvas where posts can be positioned and resized anywhere on an infinite workspace."
      -  },
      -  {
      -    "const": "grid",
      -    "description": "Classic layout where posts are arranged in columns."
      -  },
      -  {
      -    "const": "matrix",
      -    "description": "Posts arranged in a uniform, structured grid layout with equal-sized cells."
      -  },
      -  {
      -    "const": "shelf",
      -    "description": "Classic layout where posts are arranged in columns, but arranged by sections."
      -  },
      -  {
      -    "const": "stream",
      -    "description": "Single column with continuous flow of posts"
      -  },
      -  {
      -    "const": "map",
      -    "description": "Posts displayed as pins on a geographic map."
      -  },
      -  {
      -    "const": "table",
      -    "description": "Posts displayed in a spreadsheet-like table format with rows and columns."
      -  },
      -  {
      -    "const": "timeline",
      -    "description": "Posts arranged chronologically along a horizontal timeline."
      -  },
      -  {
      -    "const": "timeline_v2",
      -    "description": "Posts arranged chronologically along a horizontal timeline."
      -  }
      -]New value: +[
      +  {
      +    "const": "free",
      +    "description": "Freeform: posts can be positioned and resized anywhere on an infinite workspace."
      +  },
      +  {
      +    "const": "grid",
      +    "description": "Wall: posts packed edge to edge in a brick-like layout."
      +  },
      +  {
      +    "const": "matrix",
      +    "description": "Grid: posts in rows of equal-sized boxes."
      +  },
      +  {
      +    "const": "shelf",
      +    "description": "Columns: posts stacked in vertical columns, one column per section."
      +  },
      +  {
      +    "const": "stream",
      +    "description": "Stream: posts in a single top-to-bottom feed."
      +  },
      +  {
      +    "const": "map",
      +    "description": "Map: posts displayed as pins on a geographic map."
      +  },
      +  {
      +    "const": "table",
      +    "description": "Table: posts as rows of a spreadsheet-like table."
      +  },
      +  {
      +    "const": "timeline",
      +    "description": "Timeline: posts placed along a horizontal line to show chronological order."
      +  },
      +  {
      +    "const": "timeline_v2",
      +    "description": "Rows: posts laid out in a horizontal row, one row per section when sections are on."
      +  }
      +]
  4. Changed3 schema fields changed
    • addedInput schema / properties / posts_sort_by
      Added value: +{
      +  "description": "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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / sections_enabled
      Added value: +{
      +  "description": "Toggle sections visibility.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "wall_url",
      -  "layout"
      -]New value: +[
      +  "wall_url"
      +]
  5. 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."
  6. 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",
      -  "layout"
      -]New value: +[
      +  "wall_url",
      +  "layout"
      +]
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-destructive, non-idempotent mutation, and the description adds meaningful context beyond them: partial-apply semantics, the shape of the return, the sandbox format restriction, and the instruction to report not_applied reasons rather than claim success. It does not cover permissions or whether other settings are left untouched on partial failure, but the behavioral disclosure is well above the annotation baseline.

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?

Front-loaded one-line purpose followed by short, scannable bullets covering the format mapping, partial updates, and return handling. The name-to-value mapping largely restates the schema's const descriptions, which is a small redundancy, but the structure is efficient overall.

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 mutation tool with no output schema, the description supplies the return shape ({ success, applied, not_applied } with code/reason) and the failure-reporting obligation, plus the sandbox constraint. Combined with an 80%-covered schema, an agent has everything needed to call it and interpret the result.

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 80%, so the baseline is 3, but the description adds the mapping between user-facing format names and the internal values get_padlet reports as padlet_settings.format, which the schema alone does not connect. It also clarifies the partial-update contract for the optional settings. The telemetry parameter and sort-value details are left entirely to the schema.

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 specific verb and resource (changes how a padlet arranges its posts) and enumerates the exact scope: format, sections grouping, and sort order. That scope cleanly separates it from siblings like update_padlet_appearance, update_padlet_engagement, and update_padlet_sharing without needing to name them.

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?

Gives a real usage rule ('Pass only the settings that should change') and a hard exclusion (a sandbox padlet cannot change format), plus a pointer to get_padlet for the correct layout value. It stops short of naming sibling tools or explicitly saying when to prefer them, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.