Skip to main content
Glama

Get a post's client approval and comments

clipember_get_post_approval
Read-onlyIdempotent

Read the client's decision (none / approved / changes_requested, by whom and when), the preview link's expiry (never the URL itself), whether "publish only approved" is holding the posts, and the comments.

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>"
    },
    "name": "clipember_get_post_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesgroupId of the post (from clipember_create_post or clipember_list_scheduled_posts) — all its networks are shared together

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/ idempotentHint/destructiveHint=false, so safety is covered by structured data. The description does add real value beyond those: it discloses that the preview link's expiry is returned but never the URL itself, and that the 'publish only approved' setting can be blocking posts. However, it says nothing about behavior when no approval has been requested or the post is unpublished.

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?

A single sentence, front-loaded with the primary payload and using compact parentheticals to enumerate the decision states and the URL-withholding rule. Every clause carries information; only the nested punctuation makes it slightly harder to parse at speed.

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?

With no output schema, the description carries the return-shape burden and does it well by listing the five things returned. For a single-parameter read tool this is close to complete; the only gap is the empty/unshared-post edge case.

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% and the schema description for groupId already explains its provenance (from create_post or list_scheduled_posts) and the shared-across-networks semantics. The tool description adds nothing about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (a post's client approval) and enumerates exactly what will be read: decision state with enumerable values, actor/time, link expiry, publish gating, and comments. An agent knows precisely what comes back. It stops short of naming a sibling (e.g. clipember_list_post_comments, which reads only the comment thread) to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is implied by the enumerated returns — call it when you need the client's approval state for a known post — but there is no explicit when-to-use / when-not guidance, no statement of prerequisites (must the post have been shared with a client first?), and no pointer to the sibling that reads comments alone.

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