Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Delete Post Connection

delete_post_connection
Destructive

Delete a connection between two posts on a Freeform padlet.

  • Purpose: Remove an existing directional connection (arrow/line) between two posts.

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

  • Only works on Freeform format padlets.

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

Input Schema

NameRequiredDescriptionDefault
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.
connection_idYesThe id of the connection to delete. Must be a string representing an integer ID.

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. 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: -[
-  "connection_id"
-]New value: +[
+  "wall_url",
+  "connection_id"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description reinforces the directional-connection semantics and adds the Freeform-only constraint, which annotations do not convey. It does not describe behavior when the connection_id is invalid or already gone, so it is good but not exhaustive.

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 action, then clean bullets for purpose, return value, constraints, and prerequisite. Every bullet carries information, though the return-value bullet partly duplicates the obvious shape of a delete response.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully discloses the return contract ({ success, message }). Combined with the Freeform restriction and ID-sourcing hint, an agent has enough to call it correctly; only error-path behavior is left implicit.

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 both parameters are well documented in the schema, so the schema carries the load. The description adds only the provenance of connection_id (from get_padlet_content) and does not clarify wall_url format beyond what the schema already says — baseline 3.

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 ("Delete") and resource ("a connection between two posts") plus scope (Freeform padlets only). It distinguishes cleanly from create_post_connection, delete_comment, and the other delete_* siblings without the agent needing to inspect schemas.

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?

Explicitly names the prerequisite path ("Use get_padlet_content to get connection IDs before calling this tool") and a hard precondition ("Only works on Freeform format padlets"). It stops short of naming create_post_connection as the inverse or stating when-not to use it, but the context is clear.

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