Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Start Attachment Upload

start_attachment_upload

Start uploading a file so it can be attached to a padlet.

A file dropped into ChatGPT arrives as file. Pass that object here and do not PUT. Padlet downloads and verifies it, and the returned url is ready for any destination in step 4. Do not call complete_attachment_upload for that file.

A local file, when you can read it and send an HTTP PUT (with curl, for instance):

  1. Call this tool with the file's real size in bytes and its content type. Do not pass file.

  2. PUT the raw bytes to the upload_url you get back. One request, no headers, no form encoding — for example curl -T /path/to/file "<upload_url>". The body must be exactly size_bytes bytes long.

  3. Call complete_attachment_upload with the same wall_url and the uploaded_url from this tool. Nothing reaches the padlet until you do, and the file is verified at that point — a file whose bytes do not match the content type you declared is rejected and deleted.

  4. Pass the URL complete_attachment_upload returns to a post's attachment in create_posts or update_posts, the attachment of add_comment_to_post, or image_url of update_padlet_wallpaper or update_padlet_icon.

An ordinary public web link that should remain a link can be passed directly to any of those destinations.

Returns { success: true, upload_url: "...", uploaded_url: "...", expires_at: "..." } for a local file, { success: true, url: "...", file_name: "...", content_type: "...", size_bytes: 123 } for a chat-dropped file, or { success: false, error_code: "...", message: "..." }.

Input Schema

NameRequiredDescriptionDefault
fileNo
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.
file_nameNoThe file's name, including its extension (e.g. "diagram.png"). Used for the stored file name and to tell Office documents from plain zips.
size_bytesNoThe file's real size in bytes. Measure it; do not estimate. The padlet's per-file limit is enforced against it.
content_typeNoThe file's MIME type. Must match the file's actual bytes — this is checked against the uploaded content, not taken on trust.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / dependentRequired
      Removed value: -{
-  "content_type": [
-    "file_name",
-    "size_bytes"
-  ],
-  "file_name": [
-    "content_type",
-    "size_bytes"
-  ],
-  "size_bytes": [
-    "file_name",
-    "content_type"
-  ]
-}
    • addedInput schema / if
      Added value: +{
+  "anyOf": [
+    {
+      "required": [
+        "file_name"
+      ]
+    },
+    {
+      "required": [
+        "content_type"
+      ]
+    },
+    {
+      "required": [
+        "size_bytes"
+      ]
+    }
+  ],
+  "not": {
+    "required": [
+      "file"
+    ]
+  }
+}
    • addedInput schema / properties / file_name / minLength
      Added value: +1
    • addedInput schema / then
      Added value: +{
+  "required": [
+    "file_name",
+    "content_type",
+    "size_bytes"
+  ]
+}
  2. 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."
  3. Changed2 schema fields changed
    • addedInput schema / dependentRequired
      Added value: +{
+  "content_type": [
+    "file_name",
+    "size_bytes"
+  ],
+  "file_name": [
+    "content_type",
+    "size_bytes"
+  ],
+  "size_bytes": [
+    "file_name",
+    "content_type"
+  ]
+}
    • addedInput schema / properties / size_bytes / minimum
      Added value: +1
  4. Changed2 schema fields changed
    • addedInput schema / properties / file
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "download_url": {
+      "description": "The HTTPS URL from which Padlet should download the file.",
+      "type": "string"
+    },
+    "file_id": {
+      "description": "Optional metadata from the chat provider. Padlet does not read it.",
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "wall_url",
-  "file_name",
-  "content_type",
-  "size_bytes"
-]New value: +[
+  "wall_url"
+]
  5. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the padlet the file will be attached to.",
-  "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",
-  "file_name",
-  "content_type",
-  "size_bytes"
-]New value: +[
+  "wall_url",
+  "file_name",
+  "content_type",
+  "size_bytes"
+]
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the mutation/open-world/idempotency profile; the description adds the genuinely load-bearing behavior: the returned URL is not usable until complete_attachment_upload runs, the file is downloaded and verified by Padlet, a size/content-type mismatch causes rejection and deletion, upload URLs expire (returned as expires_at), and the PUT body must be exactly size_bytes long. That is far beyond what the annotations convey.

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 core instruction and then organized as numbered steps for the local-file path, which is the right shape for a multi-stage handshake. It is long and the return-shape paragraph is dense, but nearly every sentence carries operational weight; only minor trimming (e.g., repeating the destination list) would be possible.

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-step upload with a nested `file` object and no output schema, the description supplies the missing pieces: both return shapes, the error shape, the expiry field, and the required follow-up call plus the downstream tools that consume the URL. An agent has everything needed to complete the flow correctly.

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 already 80%, so the baseline is 3; the description adds the exclusivity rule ('Pass that object here and do not PUT' vs 'Do not pass file') that explains why the if/then schema branches exist, and stresses that size_bytes must be measured rather than estimated. It doesn't enumerate the content_type enum or explain file_name's Office-vs-zip use, which the schema already covers.

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?

Opens with a concrete verb+resource: 'Start uploading a file so it can be attached to a padlet.' It immediately distinguishes itself from complete_attachment_upload and from the post/comment/wallpaper tools that consume the resulting URL, so an agent can place it in the workflow without opening any schema.

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?

Gives explicit branching conditions: a chat-dropped `file` object goes here with no PUT and no complete_attachment_upload call, while a local file goes here with file_name/content_type/size_bytes followed by an HTTP PUT and a call to complete_attachment_upload. It even carves out a third case — an ordinary public web link should be passed directly to a destination and not uploaded at all.

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