Skip to main content
Glama
Sign In

Padlet

by com.padlet
OverviewDiscussionsAdmin

Find Padlets

find_padlets
Read-only

Finds the user's padlets: given words, the padlets that best match them, and given none, the user's most recently updated padlets.

  • Without query, returns { success: true, padlets: [...] }: padlets the user made, most recently updated first.

  • With query, returns { success: true, results: [...], count }: padlets the user made or can open, ranked by how well their content matches.

  • Each padlet has its title, description and url. Pass the url as wall_url to get_padlet and to every other tool that takes a padlet.

  • A search always returns the nearest padlets, even when none is the one asked for. Check a result's title and description before using it. If none clearly matches, say you could not find the padlet, and never write to, share, grade, freeze or delete a padlet whose title does not clearly match.

  • A padlet made moments ago may not be searchable yet. Reuse its url from earlier in the conversation, or list without query.

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": "find_padlets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost padlets to return. A list returns 20 by default and up to 100, a search 15 by default and up to 50.
queryNoWords to search the user's padlets for. Leave out to list recent padlets.
telemetryNoOptional. Padlet records this to improve its tools; it does not change what the tool does.

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a safe read, but the description adds return shapes for each mode ({success, padlets} versus {success, results, count}) and ranking semantics. It also discloses two non-obvious traits: a search always returns nearest-neighbor results even when nothing truly matches, and a freshly made padlet may not be indexed yet.

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?

The opening sentence comes first, followed by bullets that each carry one operational fact, so an agent can scan it quickly. There is mild repetition between the lead sentence and the first two bullets about what gets returned, which keeps it just short of fully tight.

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 by specifying the response envelope for both modes. The 3 parameters are all documented in the schema, and the risky follow-on actions are called out.

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 real meaning beyond the schema by tying the presence or absence of the query string to both the result set and the response shape. The limit and telemetry parameters get no additional treatment, which is fine because their schema descriptions are complete.

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?

The first sentence names a specific verb (finds) and resource (the user's padlets) and immediately splits the two modes: query present versus query absent. It clearly separates this from get_padlet by framing this tool as the discovery step whose url feeds the getter.

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?

Explicit when-to-use guidance for both modes, plus a concrete handoff rule (pass the url as `wall_url` to get_padlet and other tools). It also gives an exclusion policy: verify title and description, and never write, share, grade, freeze or delete a padlet whose title does not clearly match.

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