Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Add Comment to Post

add_comment_to_post

Add a comment to a post given the post id.

  • Purpose: Add a comment to a post given the post id.

  • What this tool returns: { success: true, comment_id: "123" } on successful comment addition; otherwise a hash with success set to false and an optional message, e.g. { success: false, message: "..." }.

  • When the result also has awaiting_approval: true, the comment waits for the padlet's approval or content check, so tell the user others cannot see it yet.

Guidance for use:

  • post_id should be a string that represents an integer ID, i.e. only contain digits. If you don't know the integer ID, try getting the padlet's content first.

  • When the result has expected: true, the comment can't be added as things stand (for example, comments are turned off). Tell the user the message instead of retrying.

  • Pass attachment when the user wants a file or link on the comment. A comment may carry text, an attachment, or both.

Input Schema

NameRequiredDescriptionDefault
post_idYesThe id of the post to add a comment to. Must be a string that represents an integer ID, i.e. only contain digits. If you don't know the integer ID, try getting the padlet's content first.
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.
attachmentNoA file or link to attach: the url an upload tool returned, or any public https address.
comment_bodyNoThe text body of the comment to add. Use only plain text, no markdown or HTML.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / post_id / pattern
      Added value: +"^\\d+$"
  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 / properties / attachment
      Added value: +{
+  "description": "A file or link to attach: the url an upload tool returned, or any public https address.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "wall_url",
-  "post_id",
-  "comment_body"
-]New value: +[
+  "wall_url",
+  "post_id"
+]
  4. Changed2 schema fields changed
    • 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: -[
-  "post_id",
-  "comment_body"
-]New value: +[
+  "wall_url",
+  "post_id",
+  "comment_body"
+]
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the coarse profile (mutation, non-idempotent, open-world), and the description adds real behavioral context beyond them: the exact success payload shape, the failure hash shape, the `awaiting_approval` moderation state where others cannot yet see the comment, and the `expected: true` non-retryable condition. That is exactly the extra context a caller needs for a write with a moderation queue.

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 one-line purpose, then returns, then guidance — a scannable structure. It loses a point for redundancy: the opening sentence is repeated verbatim as the "Purpose:" bullet, and the post_id digit rule appears twice more.

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?

With no output schema, the description takes on return-value disclosure itself and does so fully: success shape, failure shape, approval-pending state, and the hard-stop `expected` case. Combined with 100%-covered params, an agent has everything needed to call and interpret it.

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 100%, so the baseline is 3. The description goes slightly beyond the schema by stating the cross-parameter relationship — a comment may carry text, an attachment, or both — which the per-field schema descriptions do not express. The post_id digits rule is restated from the schema and earns no additional credit.

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 ("Add a comment to a post") plus the key input (post id), so the action is unambiguous. It never names the sibling it is distinct from (delete_comment, get_padlet_content), so a reader must infer the boundary rather than being told.

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?

The Guidance section gives actionable routing: if the integer ID is unknown, get the padlet's content first; if the result has expected:true (e.g. comments disabled), report the message instead of retrying; pass `attachment` when the user wants a file or link. There is no explicit "do not use this when…" exclusion, but the alternative tool and its triggering condition are named.

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