Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Create Post Connection

create_post_connection

Create a connection (arrow/line) between two posts on a Freeform padlet.

  • Purpose: Draw a directional connection from one post to another.

  • What this tool returns: { success: true, connection_id: "123" } on success; otherwise { success: false, message: "..." }.

  • Only works on Freeform format padlets.

  • Use get_padlet_content to get post IDs before calling this tool.

  • label is optional (max 50 characters). Omit it if no label is needed.

  • You cannot connect a post to itself.

  • Duplicate connections (same from_post_id and to_post_id) are not allowed.

Input Schema

NameRequiredDescriptionDefault
labelNoOptional label for the connection (max 50 characters).
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.
to_post_idYesThe id of the destination post.
from_post_idYesThe id of the source post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the Freeform padlet.",
-  "type": "string"
-}
    • 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",
-  "from_post_id",
-  "to_post_id"
-]New value: +[
+  "wall_url",
+  "from_post_id",
+  "to_post_id"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent write. The description adds the concrete failure modes (duplicate connections, self-connection) that explain the non-idempotent hint, plus the exact return shape { success, connection_id } — value the annotations do not carry.

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 a one-line purpose, then scannable bullets carrying distinct constraints. Slight redundancy where the '- Purpose:' bullet restates the opening sentence, but no other waste.

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?

No output schema exists, and the description supplies the return values, the format precondition, ID-sourcing step, and error cases. An agent has everything needed to call this correctly on the first attempt.

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

Parameters3/5

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

Schema coverage is 100% and the wall_url/from_post_id/to_post_id parameters are fully documented in the schema. The description only restates the label's 50-character limit and its optionality, adding little beyond schema text, so the baseline 3 applies.

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 ('Create a connection (arrow/line) between two posts') plus the directional/format scope ('Freeform padlet'). It is clearly distinguishable from delete_post_connection and create_posts without opening a 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 prerequisites and constraints: only works on Freeform padlets, use get_padlet_content first to obtain post IDs, no self-connections, duplicates rejected, label optional. This is close to a full when/when-not specification.

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