Skip to main content
Glama

Comment on a post for the team

clipember_add_post_comment

Leave an internal comment on a post group for the team (for example a note on the caption or why it was moved). The post's author and earlier commenters see it in their notifications; clients never do. Write it as yourself on the user's behalf only when they asked you to.

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": {
      "groupId": "<groupId>",
      "body": "<body>"
    },
    "name": "clipember_add_post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe comment (up to 2000 characters)
groupIdYesThe groupId of the post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint false, destructiveHint false, idempotentHint false); the description adds genuinely non-derivable behavior: who gets notified (author and earlier commenters) and who never sees it (clients). The visibility/notification disclosure is the most valuable part, though it does not mention whether duplicate comments are deduplicated or whether the comment can be edited afterward.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The audience/notification fact comes first and the consent rule closes it, so the agent reads the most decision-relevant information before the caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, audience, notification effects, and consent. The one omission is any hint of what the call confirms or returns after a successful comment, which would help an agent report back.

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 both groupId and body are already documented with length constraints and UUID format. The description only echoes the 'post group' concept and the 'comment' concept, adding no format or constraint detail beyond the schema; 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 ('Leave an internal comment on a post group for the team') and the qualifier 'internal' separates it from any client-facing messaging, which an agent can act on immediately. The parenthetical examples ('a note on the caption or why it was moved') pin down the real-world intent rather than restating the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases and a clear consent rule ('Write it as yourself on the user's behalf only when they asked you to'), plus an audience constraint (clients never see it) that shapes when this tool is appropriate. It stops short of naming the read-side counterpart or stating an explicit when-not-to-use condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources