Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Grade Posts

grade_posts
Destructive

Grade posts on a padlet by saving a numeric score per post, and optionally an overall written comment per student.

  • Purpose: Create or update Score grades for one or more posts. Optionally save one written feedback comment per student.

  • What this tool returns: { success: true, graded_count: N } on success; { success: false, message: "..." } on failure.

  • You must call get_padlet_content first to read the posts before grading.

  • Only wall builders and admins can grade posts.

  • Scores must be integers between 0 and the wall's max_score. Read max_score from padlet_settings -> grading_settings -> max_score in the get_padlet_content result.

  • For student_comments: a student may have multiple posts — provide ONE comment per student using any one of their post_ids to identify them.

Input Schema

NameRequiredDescriptionDefault
gradesYesArray of grades to save, one entry per post.
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.
student_commentsNoOptional. One overall written feedback comment per student. A student may have multiple posts — provide exactly one entry per student using any one of their post_ids to identify them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the padlet containing the posts to grade.",
-  "type": "integer"
-}
    • 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: -[
-  "wall_id",
-  "grades"
-]New value: +[
+  "wall_url",
+  "grades"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the create-or-update nature of grading, the permission gate, the score bounds check, and the exact success/failure response shape despite no output schema. The one gap is that it never states that an existing score is overwritten and that the prior value is not recoverable.

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 lead sentence followed by scannable bullets, each carrying a distinct operational fact. The 'Purpose:' bullet largely restates the lead sentence and the student_comments bullet overlaps the schema text, so it is slightly longer than necessary.

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 mutation tool with no output schema, the description supplies everything an agent needs: the mandatory read-first step, actor permissions, value-range source, comment-to-student mapping, and both success and failure response shapes.

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 baseline is 3; the description earns above that by explaining where max_score comes from (padlet_settings -> grading_settings -> max_score) and by clarifying that one comment entry per student may reference any of that student's post_ids. Some of the student_comments guidance duplicates the nested schema description, limiting it to a 4.

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 (grade posts by saving numeric scores), plus the optional secondary effect (one overall written comment per student). It is clearly distinguishable from add_comment_to_post and sync_grades_to_lms by the 'numeric score per post' framing and the return shape.

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 prerequisites ('must call get_padlet_content first'), permission requirements ('only wall builders and admins'), and validation bounds ('integers between 0 and the wall's max_score', with the location of max_score spelled out). It also routes the comment-per-student case with a concrete rule rather than leaving it to inference.

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