Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Update Submission Form Settings

update_submission_form_settings

  • Purpose: Enable, disable, or configure the submission form link on a padlet. Submission forms allow collecting responses from users via a dedicated form.

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

Guidance for use:

  • Use this tool when the user wants to collect submissions or responses via a form link.

  • Configure where users are redirected after submitting: the padlet itself, a confirmation page, or another submission form.

  • Control whether login is required and set custom confirmation text.

  • Only set the parameters you want to change. Omit parameters to keep their current values.

  • Keep your message concise (1-2 sentences).

Input Schema

NameRequiredDescriptionDefault
enableYesWhether to enable or disable the submission form link
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.
requires_loginNoWhether users must be logged in to access the submission form.
confirmation_textNoCustom text shown on the confirmation page after submission.
redirect_locationNoWhere to redirect users after submitting: padlet (show the padlet), confirmation (show a confirmation page), or request_again (show another submission form).

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds real value beyond that by documenting the return contract ({ success: true } or success=false with an optional message) even though no output schema exists, and by spelling out patch semantics. It stops short of covering permissions/authorization requirements for editing a padlet's form settings, so it is not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bulleted layout is front-loaded with Purpose and the return shape, which is good. However, the closing line 'Keep your message concise (1-2 sentences)' is irrelevant to this tool — it looks copied from a comment/post tool and could mislead an agent — and the guidance bullets partly restate the schema, adding avoidable length.

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?

For a 5-parameter mutation with no output schema, the description covers purpose, call trigger, partial-update behavior, and the exact response shape, which is close to sufficient. The gaps are the stray unrelated instruction and the absence of any note about who may modify a padlet's form settings (owner vs collaborator), which matters for a settings mutation.

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 per-parameter documentation is already handled and the baseline is 3. The description goes one step further by explaining the update semantics (omitted parameters retain current values) and by restating the redirect destinations in human terms, which helps an agent pick enum values confidently.

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 description opens with a specific verb plus resource: enable, disable, or configure the submission form link on a padlet. That resource is clearly distinct from the neighboring settings tools (update_padlet_settings, update_padlet_content_settings, update_padlet_access_settings), so an agent can route without opening sibling schemas.

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?

It gives an explicit trigger ('when the user wants to collect submissions or responses via a form link') and then enumerates the concrete configurations: redirect destination, login requirement, confirmation text. It also states the partial-update rule ('Only set the parameters you want to change. Omit parameters to keep their current values'), which removes the main ambiguity for a mutation tool.

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