Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Get Padlet Access Settings

get_padlet_access_settings
Read-only

  • Purpose: Get the access settings for a padlet like student role, teacher role, visitor role, isListed (whether the padlet is shown on the dashboard), isPublished (whether the padlet is shown on user profile and web), if the padlet requires visitor to be a logged in user, the padlet's access password. Also return collaborators information.

  • What this tool returns: { success: true, access_settings: {...} } with complete access settings including collaborators and visitor role.

Guidance for use:

  • ALWAYS use this tool to get the access settings and collaborators information of a padlet before making changes.

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.

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 to get access settings for",
-  "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"
-]New value: +[
+  "wall_url"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/closed-world, so the description only needs to add what they don't. It does so usefully, disclosing the exact return envelope and that sensitive data (access password, collaborator list) is included – information an agent should know before echoing results. No permission/auth requirements are mentioned.

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?

Bulleted and front-loaded: purpose first, return shape second, usage guidance third. The field enumeration is long but each item is a real return field, so it earns most of its length; minor redundancy between the 'Purpose' list and the 'What this tool returns' line.

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 only one well-documented parameter and no output schema, the description supplies the missing return contract (success flag plus access_settings with collaborators). An agent has enough to call it and interpret the result; only auth/permission prerequisites are absent.

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 description coverage is 100% and the wall_url description already covers format, provenance, and exclusions (no breakout/submission link, no wall_id). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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+resource and enumerates the exact fields returned (student/teacher/visitor roles, isListed, isPublished, login requirement, access password, collaborators), which effectively separates it from the content/whiteboard settings siblings. It never explicitly contrasts itself with get_padlet_content_settings or update_padlet_access_settings, so differentiation is implicit rather than stated.

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?

Gives an explicit directive: 'ALWAYS use this tool ... before making changes', which clearly positions it as the read step preceding an access-settings update. It does not state when to skip it or what to use for other setting categories, leaving a small gap.

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