Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Analyze Post Attachments

analyze_post_attachments
Read-only

Analyzes the content of attachments (images, videos, audio, PDFs, documents) from posts on the padlet.

  • Purpose: Retrieve and analyze post attachment content so you can describe, summarize, or answer questions about what's in the attachments.

  • What this tool returns: { success: true, analysis: { posts: [{ post_id, attachments: [{ description }] }] } } with a structured analysis grouped by post_id; { success: true, message: "No valid attachments to analyze" } when none of the posts has an attachment it can read; otherwise { success: false, message: "..." }.

Guidance for use:

  • Use this tool when the user asks about the content of images, videos, audio, documents, or other attachments in posts.

  • Identify which posts have attachments before calling. If an EXPLICIT list of post_ids to analyze has been provided to you in the conversation, use those directly. Otherwise, call get_padlet_content first to discover them.

  • A post has an attachment if its "attachment" field contains a URL (not empty, not "poll"). Check BOTH the "attachment" field and "attachment_props" — some posts have a URL in "attachment" but empty "attachment_props".

  • Pass the post_ids of posts whose attachments you want to analyze. The tool will retrieve the attachment URLs automatically.

  • Pass at most 50 post IDs per call. If there are more, prioritize the most relevant posts.

  • Only analyzes attachments the current user has permission to view.

  • Do not use this tool if the user is not asking about attachment content.

  • Results are cached: previously analyzed attachments return cached descriptions without re-analyzing.

  • IMPORTANT: Only pass the query parameter when the user has a specific, targeted question about the attachment content (e.g. "What formula is on slide 3?", "What color is the logo?"). For general requests like "describe the attachments", "what's in the images", or "summarize the content", do NOT pass a query — omit it entirely so the tool returns a comprehensive generic description.

Input Schema

NameRequiredDescriptionDefault
queryNoOptional. A specific question about the attachments. Only provide this for targeted questions (e.g. 'What formula is on slide 3?'). Do NOT provide for general descriptions.
post_idsYesIDs of posts whose attachments to analyze. Get these from get_padlet_content.
wall_urlYesThe padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link, and not a padlet id: no tool takes a wall_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / wall_url / description
      Previous value: -"The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link."New value: +"The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link, and not a padlet id: no tool takes a wall_id."
  2. Changed2 schema fields changed
    • addedInput schema / properties / wall_url
      Added value: +{
+  "description": "The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link.",
+  "maxLength": 2048,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "post_ids"
-]New value: +[
+  "wall_url",
+  "post_ids"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent=false/destructive=false) by disclosing the three distinct response shapes including the 'No valid attachments to analyze' empty case, permission scoping ('Only analyzes attachments the current user has permission to view'), and caching behavior that changes repeat-call latency and cost. These are exactly the behavioral traits annotations cannot express.

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 shapes, then well-segmented bullets that each carry operational information. It is long, and the `query` guidance appears both in the return-shape section and in the closing IMPORTANT line, plus the schema repeats it — a small amount of redundancy, but nothing is padding.

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?

For a read-only analysis tool with no output schema, the description supplies the response structure verbatim, the empty and error cases, permission boundaries, batching limit, caching, and prerequisites. An agent has everything needed to invoke this correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it explains the retrieval path for post_ids, the 50-item cap and prioritization strategy, and the non-obvious conditional rule for `query` (omit entirely for general descriptions, supply only for targeted questions) with contrasted examples. That is semantics the schema alone does not convey.

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 (analyzes) and resource (attachment content from posts), enumerates the attachment types covered (images, videos, audio, PDFs, documents), and names the sibling it depends on (get_padlet_content) for discovery. An agent can distinguish this from get_padlet_content or export_padlet 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 says when to use it (user asks about attachment content), when not to ('Do not use this tool if the user is not asking about attachment content'), and what to do instead when post IDs are unknown (call get_padlet_content first). Adds hard operational limits (max 50 post IDs per call, prioritize if more) and a precise rule for identifying which posts qualify via the attachment/attachment_props fields.

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