Padlet

Search Padlet Actions

search_padlet_actions

Read-onlyIdempotent

Finds Padlet actions that are not tools of their own, among the actions this account may run. They cover padlet administration (a padlet's summary, content and moderation settings, collaborators, submission forms, custom post fields, breakout links, freezing, remaking, transferring, exporting, archiving and trashing, restoring deleted posts and whiteboard tools), automations, grading and LMS grade sync, arcade activities, pinning and connecting posts, post reactions and poll votes, the account, its folders and the current time, library administration (the library's name, bio and avatar, members, invites and pending invites, classes and their members, onboarding, sign-in, approved domains, permissions, content safety and attachment types) and padlet and library analytics. Search here before telling the user Padlet cannot do something, and before using a listed tool that only comes close to what the user asked. Each match gives its name, summary, arguments, an example and the tool to run it with: run_padlet_read_action, run_padlet_write_action or run_padlet_destructive_action. Run a match directly with that tool. Use describe_padlet_action only when you need an action's full rules.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_padlet_actions"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	A few words for what the user wants to do.
`resource`	No	Optional. Only actions on this resource, such as padlet, post, library or account.
`telemetry`	No	Optional. Padlet records this to improve its tools; it does not change what the tool does.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

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"
+}

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds the key missing piece: what a match returns (name, summary, arguments, example, and the tool to run it with). It stops short of stating result limits, pagination, or what happens when nothing matches, so not 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?

Action-relevant guidance is front-loaded and the closing sentence on which run_* tool to use is tight. The single massive parenthetical catalog is dense and hard to parse, but it does earn its place by letting the agent recognize a domain match without an extra call.

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?

There is no output schema, and the description compensates fully by explaining the shape of each match and the routing to the execution tools. Combining that with 100% schema coverage and annotations, an agent has everything needed to call this 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 description coverage is 100%, so query/resource/telemetry are already documented; baseline is 3. The description adds the useful nuance that results are limited to what 'this account may run' and that resource names include padlet, post, library and account, but does not explain query phrasing beyond what the schema says.

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 ('Finds') and resource ('Padlet actions that are not tools of their own'), then immediately bounds the scope ('among the actions this account may run'). The enumerated domains make it unmistakable versus the run_* siblings, which execute rather than search.

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 triggers ('before telling the user Padlet cannot do something, and before using a listed tool that only comes close'), names the follow-up path (run_padlet_read_action / write / destructive), and names the one alternative with its condition ('Use describe_padlet_action only when you need an action's full rules').

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

All Padlet tools Inspect

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.