Skip to main content
Glama

Create Padlet

create_padlet

Create a new blank padlet that can then be populated using other tools.

  • Purpose: Create a new empty padlet from scratch.

  • What this tool returns: { success: true, padlet: { title, description, format, url }, access, workspace } with the new padlet's details. workspace is { name, library_url } for a library or { personal: true }; tell the user where the padlet went.

  • access is who can open the new padlet: { visitor_role, student_role, teacher_role, require_login, require_password, is_listed, is_published }, in the names update_padlet_sharing takes. A visitor_role other than "none" lets anyone with the link open it. Tell the user who can open it, and offer update_padlet_sharing to change that.

Guidance for use:

  • Creates a blank padlet with no posts. It gets the sharing settings its workspace gives new padlets, the same as on the web, so it is not always private.

  • Pass the returned url as wall_url to save_posts and the other tools that take a padlet.

  • Optional parameters: title (uses smart default based on format if not provided), description, format (grid, stream, timeline_v2, matrix, shelf, table, free, map, timeline, whiteboard, columns).

  • After creation, use other tools to configure settings, add posts, sections, etc.

  • If format is not specified, defaults to "grid".

Where the new padlet goes:

  • Ask the user which workspace to use unless they already named one. Pass the library's library_url, or personal: true for their personal space, never both. list_libraries, when you have it as a tool or through run_padlet_read_action, gives each library's link.

  • With neither, the tool creates only when exactly one workspace can take the new padlet, and the result says which. Otherwise nothing is created, and available_workspaces lists the choices to ask about.

  • If the workspace cannot take a padlet, nothing is created and the result gives reason, message and available_workspaces. Tell the user why, ask which workspace to use, and call again with one entry's library_url or personal. Never pick one for the user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_padlet"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoTitle of the padlet (optional, will use smart default based on format if not provided)
formatNoFormat of the padlet (default: grid)grid
personalNoOptional. true when the user chose their personal space. Never pass it with library_url.
telemetryNoOptional. Padlet records this to improve its tools; it does not change what the tool does.
descriptionNoDescription/subtitle of the padlet (optional)
library_urlNoOptional. The padlet.com link of the library the user chose, as list_libraries or an earlier refusal gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / telemetry
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Optional. Padlet records this to improve its tools; it does not change what the tool does.",
      +  "properties": {
      +    "intent": {
      +      "description": "Explain the task and why you are calling this tool. Omit full queries, large inputs, personal information, and secrets.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed2 schema fields changed
    • addedInput schema / properties / library_url
      Added value: +{
      +  "description": "Optional. The padlet.com link of the library the user chose, as list_libraries or an earlier refusal gives it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / personal
      Added value: +{
      +  "description": "Optional. true when the user chose their personal space. Never pass it with library_url.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior3/5

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

The description covers behavior beyond the annotations in detail: pads inherit workspace sharing settings so they are 'not always private', what access/workspace objects contain, and what happens on failure. The quoted score should reflect this value, which is high enough to warrant a stronger mark than a 3; the depth of failure-mode disclosure is well above the annotation baseline.

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 purpose and return shape, then bulleted guidance, so it scans well. Minor redundancy: the format enumeration appears twice (in 'Optional parameters' and again in the default line), and the telemetry parameter is left to the schema.

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?

With no output schema, the description carries the return contract (success, padlet, access, workspace) and the refusal contract (reason, message, available_workspaces) itself, which is exactly what an agent needs to call this correctly and report results to the user.

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 already 100%, so the baseline is 3; the description goes further by explaining the mutual exclusivity of library_url and personal, that title gets a smart default keyed to format, and the full format enum with its default. It adds real decision semantics on top of the schema text.

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 a new blank padlet') and explicitly bounds scope: blank, no posts, populated later by other tools. That distinguishes it from save_posts, save_sections and the update_* siblings without needing their 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?

Gives explicit when-to-use guidance (creating from scratch, then configure with other tools), names the downstream handoff ('Pass the returned url as wall_url to save_posts'), points to update_padlet_sharing as the alternative for sharing changes, and prescribes a workspace-selection protocol including 'never pick one for the user'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.