Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Get Padlet Content Settings

get_padlet_content_settings
Read-only

  • Purpose: Get the content settings of a padlet like content moderation mode and content (copy) protection setting.

  • What this tool returns: { success: true, content_settings: {...} } with complete content settings data including content moderation mode and content protection setting.

Guidance for use:

  • Content moderation mode is to decide which posts and comments require approval. The "all" value may also be referred to as "manual" by users because it means all posts and comments require manual approval.

  • Content protection (also known as copy protection - use this term when talking to users) setting is to decide if the padlet's content can be remade, downloaded, and exported.

  • is_remakeable is to decide if the padlet's content can be remade.

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 content 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.6/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive, so the description's added value is in disclosing the return envelope ({ success, content_settings }) and the meaning of each setting — notably that "all" is what users call "manual" and that copy protection is the user-facing term. That is genuine context beyond the structured fields, though it omits error behavior for invalid or inaccessible padlets.

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?

Front-loaded purpose and return shape are good, but the closing line about is_remakeable restates the content-protection point already made and adds little, and the content-protection concept is explained in two separate bullets. Mild redundancy dilutes otherwise clean bullets.

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, describing the return envelope is necessary and done well, and the setting semantics are explained. A reader still lacks detail on what each setting's possible values are beyond the single "all"/"manual" case, but the definition is sufficient to call the tool correctly.

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 single wall_url parameter is thoroughly documented in the schema, including what it is not. The description adds no parameter-level detail, so the baseline of 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?

The description opens with a specific verb+resource (get the content settings of a padlet) and names the fields involved, making it immediately distinguishable from the sibling update_padlet_content_settings. It stops short of explicitly naming that sibling, but the read-vs-write split is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It offers valuable interpretive guidance (moderation mode values, copy protection terminology) but says nothing about when to call this tool versus alternatives such as get_padlet_settings-style siblings or update_padlet_content_settings. Usage is implied from the name rather than stated.

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