Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Search Padlets

search_walls
Read-only

Search for padlets in the user's account using semantic search.

  • Purpose: Find relevant padlets based on a search query. This allows discovering padlets by their content, not just by browsing recent padlets.

  • What this tool returns: { success: true, results: [...] } with an array of matching padlets containing title, description, url, and other relevant information.

Guidance for use:

  • Use this tool to find specific padlets when the user mentions content or topics (e.g., "my project padlet", "padlet about climate change").

  • The search uses semantic/vector search, so it understands meaning, not just exact keyword matches.

  • Results are ranked by relevance to the search query.

  • Only returns padlets the current user has access to (owned by them or shared with them).

  • Pass a result's url as wall_url to get_padlet_content and to every other tool that takes a padlet.

  • If no results are found, consider using list_padlets to browse recent padlets instead.

Results are nearest matches, not exact ones:

  • This tool always returns the closest padlets it can find. It does NOT return an empty list just because the padlet the user asked for does not exist, so a non-empty response is not evidence that the padlet was found.

  • Before using a result, check that its title and description actually match what the user asked for. If none of them do, tell the user you could not find that padlet — never silently substitute the nearest result.

  • Never write to, share, invite anyone to, grade, freeze, or delete anything on a result whose title does not clearly match the user's request. Confirm which padlet they meant first.

  • A padlet created moments ago may not be indexed yet. When the user refers to a padlet from earlier in this conversation, reuse its url directly instead of searching for it, and use list_padlets for recently created or updated padlets.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 15, max: 50)
queryYesThe search query to find relevant padlets (e.g., 'project planning', 'math homework', 'team meeting notes')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), but the description adds behavior the annotations cannot express: semantic/vector ranking, access scoping, nearest-match behavior that never returns an empty list, and indexing lag for newly created padlets. These are genuine decision-relevant traits beyond structured fields.

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?

Purpose and return shape are front-loaded and the bulleted guidance is scannable. It is somewhat longer than necessary — the 'Purpose:'/'What this tool returns:' labels and the restated return caveat add bulk — but nearly every line carries actionable instruction.

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 supplies the return shape ({ success, results: [...] } with title, description, url). It also covers indexing timing, access scope, and result reliability, leaving no operational question unanswered.

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%, so query and limit (default 15, max 50) are already fully documented in the schema. The description adds no parameter-level meaning such as query phrasing advice or limit tradeoffs beyond what the schema states, so the baseline 3 applies.

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 ('search for padlets in the user's account using semantic search') and explicitly contrasts with list_padlets for browsing recent items. An agent can distinguish it from every sibling without opening a 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?

Gives explicit when-to-use triggers ('when the user mentions content or topics'), names the alternative list_padlets for the no-results case, and instructs reusing a url from conversation instead of searching for recently created padlets. The nearest-match warning adds an explicit 'when not to trust results' rule.

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