Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Create Automation

create_automation

  • Purpose: Create automations on a padlet.

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

Guidance for use:

  • Automations are scheduled actions to be executed in the future. They must not be scheduled to execute on a past date.

  • The automation instructions should be calculated based on the user's timezone and current time. However, the scheduled_at timestamp must be converted to UTC.

  • Do not inform the user about timezone handling. You must use a human-friendly format when displaying dates.

  • After calling this tool, you MUST include the automations widget in your response using this exact format:

  • Example response: "I've created a freeze automation scheduled for tomorrow at 9AM. "

Input Schema

NameRequiredDescriptionDefault
actionYesThe action to schedule.
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.
scheduled_atYesThe time at which the automation is going to be executed, in UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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 padlet where the automation is going to be created.",
-  "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",
-  "action",
-  "scheduled_at"
-]New value: +[
+  "wall_url",
+  "action",
+  "scheduled_at"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=false), it discloses the return shape for both success and failure, a validation constraint (no past dates), timezone handling rules, and a mandatory post-call widget that must appear in the response. That is substantial behavior an agent could not infer from structured fields.

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?

Purpose and return format are front-loaded, and the guidance bullets each carry actionable content. It is slightly long with the example response and multiple formatting directives, but none are wasted.

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 three-parameter mutation with no output schema, the description covers return values, temporal validation, timezone semantics, and required follow-up UI — an agent has everything needed to call it correctly and respond properly.

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, and the description earns an upgrade: it explains that scheduled_at is computed in the user's timezone but transmitted as UTC, and that the human-facing display should be friendly and not mention timezone mechanics. That adds operational meaning beyond the schema's terse 'in UTC'.

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 automations on a padlet' — with the enum-visible action set (freeze/unfreeze) implied. It is clearly distinguishable from sibling tools like freeze_padlet (immediate action) and get_padlet_automations (read).

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?

Provides strong conditions: automations are future-scheduled actions, must not be scheduled in the past, and scheduled_at must be computed from the user's timezone then converted to UTC. It does not, however, name an alternative for immediate freezes (e.g. freeze_padlet), so the when-not-alternatives dimension is incomplete.

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