Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

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 }, 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.

Guidance for use:

  • Creates a blank padlet with default settings (private, no posts).

  • Pass the returned url as wall_url to update_padlet_settings 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.

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.
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 / additionalProperties
      Added value: +false
  2. 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"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only tell the agent this is a non-read-only, non-destructive, non-idempotent write. The description adds real substance: defaults are private with no posts, the exact return envelope including the workspace shape, and the two distinct failure modes (ambiguous workspace, workspace cannot accept a padlet) with what each result contains. Missing is any mention of permissions/quota errors, which keeps it off a 5.

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?

Well structured with labeled sections and the core action front-loaded. The 'Where the new padlet goes' bullets restate each other somewhat (the third bullet re-explains the refusal case already implied by the second), costing a little density, but every section is scannable and purposeful.

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?

No output schema exists, and the description compensates by spelling out the return object including the nested workspace variants. Combined with the default-state disclosure, the follow-up tool chain, and both failure paths, an agent has everything needed to call this correctly and to report the outcome 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 100%, so the baseline is 3, but the description adds meaning beyond it: the mutual exclusivity of library_url and personal is framed as a rule with a consequence, the 'neither provided' case is explained as conditional creation with an available_workspaces fallback, and it directs where library_url comes from. The format enum and title smart-default are restated from the schema, which is redundant but not harmful.

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?

Opens with a specific verb+resource ('Create a new blank padlet') and immediately scopes it against siblings: this makes an empty padlet, whereas create_padlet_arcade_activity and remake_padlet are different operations and update_padlet_settings configures an existing one. An agent can distinguish it without opening the schema.

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?

Explicitly states the post-creation workflow ('Pass the returned url as `wall_url` to update_padlet_settings'), enumerates optional params, and gives a full decision procedure for the workspace ambiguity case including the instruction to ask the user rather than choose. Names the alternative path (list_libraries / run_padlet_read_action) for resolving library links.

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