Padlet

by com.padlet

Overview Discussions Admin

Create Posts

create_posts

Create new posts on a padlet.

Purpose: Add new posts to a padlet.
What this tool returns: { success: true, created_post_ids: { "new_1": "123", "new_2": "456" } } on successful creation, mapping temporary "new_" ids to real post ids; otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.
When some posts or fields could not be applied, the result also has not_applied, a list of { post_id, reason }. Tell the user which posts or fields did not change and why, using the reason, and never say a listed change was made.
When the result has awaiting_approval_post_ids, those posts wait for the padlet's approval or content check, so tell the user others cannot see them yet.

Guidance for use:

post_id is optional. It is the key of the post in created_post_ids and must start with "new_" (e.g. "new_1", "new_abc"). A post sent without one is keyed by its position, "new_1" for the first. Never use integer ids for new items.
Requires write permission on the padlet.
If setting an attachment, you must either:
1. include both attachment_type AND attachment_search
2. include attachment as a valid URL. Pass a chat-dropped file as file to start_attachment_upload. Use start_attachment_upload plus complete_attachment_upload for a local file when the client can issue an HTTP PUT. An ordinary public web link may be passed directly as attachment.
Poll and other attachments using attachment and attachment_search fields are mutually exclusive. Do not include both in the same post.
If the padlet's settings use the "map" format, you MUST include location_data with latitude, longitude, and location_name.
Create posts under a section:
- Create the section first using the update_section tool, or make sure the section already exists.
- The update_section tool returns created_section_ids mapping temporary "new_" ids to real section ids (e.g. { "new_1": "123" }). Use these real ids as section_id when creating posts.
- If you don't have the real section id, use the get_padlet_content tool to look it up.
- NEVER use "new_" prefixed ids as section_id — they will be rejected.
Post color:
- Only the following colors are allowed: red, orange, green, blue, purple. There are a few exceptions:
  - If 'yellow' is provided, use 'orange' instead.
  - "white" and "black" values are only allowed if and only if the padlet color scheme is "light" and "dark" respectively. The counterpart color should not be allowed and be rejected instead. Use the padlet_settings -> color_scheme field to get the padlet color scheme with the get_padlet_content tool.

Input Schema

Name	Required	Description	Default
`posts`	Yes	Array of posts to create.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026
- addedInput schema / properties / posts / items / properties / post_id / pattern
```
Added value: +"^new_"
```
- addedInput schema / properties / posts / items / properties / section_id / pattern
```
Added value: +"^\\d*$"
```

Changed3 schema fields changedOct 23, 2026

changedInput schema / properties / posts / items / properties / post_id / description

Previous value: -"REQUIRED. Must be a string starting with 'new_' (e.g. 'new_1', 'new_abc'). Never use plain integers for new posts."New value: +"Optional. Must be a string starting with 'new_' (e.g. 'new_1', 'new_abc'). Never use plain integers for new posts. Left out, the post is keyed by its position in created_post_ids: 'new_1' for the first."

removedInput schema / properties / posts / items / required
```
Removed value: -[
-  "post_id"
-]
```

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

Changed3 schema fields changedOct 13, 2026

removedInput schema / properties / wall_id

Removed value: -{
-  "description": "The id of the wall to create the posts on",
-  "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"
-]New value: +[
+  "wall_url",
+  "posts"
+]

First observedOct 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare a non-read-only, non-idempotent, open-world write, but say nothing about outcomes. The description supplies the success payload shape (created_post_ids mapping 'new_' keys), the failure shape, the not_applied list with per-post reasons and an instruction never to claim an unapplied change succeeded, and awaiting_approval_post_ids invisibility. That is materially new behavioral information rather than a restatement of annotations.

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 with the purpose and organized into scannable labeled bullets (return values, guidance, sections, color), so structure is strong. It is somewhat long and a few passages, particularly the post_id 'new_' rule and the location_data requirement, largely repeat what the schema descriptions already say.

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 write tool with a deeply nested 12-field post object and no output schema, the description covers return values, partial-failure semantics, approval states, permission prerequisites, and cross-tool dependencies (start_attachment_upload, complete_attachment_upload, get_padlet_content, update_section). Nothing an agent needs before calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds semantics the schema does not encode: post_id must start with 'new_' and never be an integer, 'new_' ids are never valid as section_id, attachment vs attachment_search exclusivity, and the yellow->orange and white/black color substitutions tied to the padlet color_scheme. These are non-obvious constraints an agent would otherwise violate.

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 and resource ('Create new posts on a padlet') and the implication of 'new' separates it from the update_posts sibling. It never names update_posts explicitly as the alternative for modifying existing posts, so the sibling routing is inferred rather than stated.

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?

Goes well past implied usage: it states the write-permission prerequisite, the exact either/or rules for attachments, the mutual exclusivity of attachment and attachment_search, the required section-creation ordering (create_section -> update_section -> real id -> posts), the mandatory location_data for map-format padlets, and the color allow-list with exceptions. An agent has concrete conditions for every branch.

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.

Create Posts

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources