Skip to main content
Glama

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 — an HTML, SVG or XML file is rejected and deleted, whatever its name.

  4. Pass the URL complete_attachment_upload returns to a post's attachment in save_posts, a comment's attachment in save_comments, wallpaper_image_url of update_padlet_appearance or icon_image_url of update_padlet_heading.

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"). The extension sets the stored file's type, as in a browser upload.
telemetryNoOptional. Padlet records this to improve its tools; it does not change what the tool does.
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. HTML, SVG and XML files cannot be attached.

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. Changed3 schema fields changed
    • changedInput schema / properties / content_type / description
      Previous value: -"The file's MIME type. Must match the file's actual bytes — this is checked against the uploaded content, not taken on trust."New value: +"The file's MIME type. HTML, SVG and XML files cannot be attached."
    • removedInput schema / properties / content_type / enum
      Removed value: -[
      -  "image/jpeg",
      -  "image/png",
      -  "image/gif",
      -  "image/webp",
      -  "application/pdf",
      -  "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
      -  "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
      -  "application/vnd.openxmlformats-officedocument.presentationml.presentation",
      -  "application/msword",
      -  "application/vnd.ms-excel",
      -  "application/vnd.ms-powerpoint",
      -  "audio/mpeg",
      -  "audio/mp4",
      -  "audio/x-wav",
      -  "audio/ogg",
      -  "video/mp4",
      -  "video/quicktime",
      -  "video/webm"
      -]
    • changedInput schema / properties / file_name / description
      Previous value: -"The file's name, including its extension (e.g. \"diagram.png\"). Used for the stored file name and to tell Office documents from plain zips."New value: +"The file's name, including its extension (e.g. \"diagram.png\"). The extension sets the stored file's type, as in a browser upload."
  3. 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"
      +  ]
      +}
  4. 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."
  5. 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
  6. 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"
      +]
  7. 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"
      +]
  8. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only supply the generic safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds substantial behavior the annotations cannot express: Padlet downloads and verifies the chat-provided file, the local-file PUT must be exactly one request with no headers or form encoding and the body must equal `size_bytes`, nothing reaches the padlet until complete_attachment_upload, HTML/SVG/XML are rejected and deleted regardless of name, and uploads expire via `expires_at`.

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 content is front-loaded, split into clearly labeled modes, and every sentence carries operational weight — the numbered steps map one-to-one onto required actions. It is on the long side for a single tool, and the four-destination enumeration in step 4 could be compressed, but no sentence is filler.

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 stateful, multi-step upload handshake with a nested `file` object and no output schema, the description covers everything an agent needs: both entry modes, the exact HTTP mechanics, the mandatory follow-up call, the verification/rejection rule, and the two response shapes plus the error shape. Nothing about invoking it correctly is left to inference.

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?

Schema coverage is already high (83%), but the description still adds meaning the schema cannot: the mutual exclusivity between `file` and the file_name/content_type/size_bytes trio is stated operationally ('Pass that object here and do not PUT', 'Do not pass `file`'), and size is framed as a hard contract ('The body must be exactly `size_bytes` bytes long'). It also explains that `upload_url`/`uploaded_url` from the response are what complete_attachment_upload consumes, tying the two parameters to their downstream use.

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 opening sentence states a specific verb and resource ('Start uploading a file so it can be attached to a padlet'), then immediately splits into the two distinct operating modes: a chat-dropped `file` object versus a local file requiring a PUT. It explicitly names the sibling complete_attachment_upload and the conditions under which it must not be used, so an agent can route correctly 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?

Guidance is explicit and bifurcated: 'A file dropped into ChatGPT arrives as `file`. Pass that object here and do not PUT' versus the numbered three-step flow for a local file, plus the exclusion 'Do not call complete_attachment_upload for that file.' It also offers the alternative path ('An ordinary public web link that should remain a link can be passed directly to any of those destinations'), covering when not to use this tool at all.

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.