Skip to main content
Glama

Approve a teammate's post or ask for changes

clipember_decide_team_approval
Idempotent

As the workspace owner or an admin, approve a post a member asked to approve (its drafts go into the queue at their time, also after an earlier request_changes; any whose time already passed, or a group last saved as a draft, stay drafts and the notice says why) or send it back with a note (request_changes; queued posts of the group go back to drafts). Approval never makes a TikTok choice: a TikTok post without its choice still waits in the TikTok queue. Decide only when the user told 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>",
      "decision": "<decision>"
    },
    "name": "clipember_decide_team_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note for the member
groupIdYesThe groupId of the post
decisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive mutation, and the description adds genuinely new behavior: approved drafts enter the queue at their scheduled time, drafts whose time has passed or that were saved as drafts stay drafts with a stated reason, request_changes pushes already-queued posts of the group back to drafts, and TikTok posts still need their own choice. That is unusually rich side-effect disclosure. It stops short of confirming idempotency or permission-failure behavior, and the request_changes revert-to-draft side effect sits in mild tension with destructiveHint=false, though it is a status change rather than data loss, so no contradiction is flagged.

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

Conciseness3/5

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

The content is dense and mostly earns its place, and the main action is front-loaded in the title and opening clause. The execution is poor, however: a single run-on sentence with a deeply nested parenthetical about draft/queue rules makes the key caveats hard to extract on a first read, and some clauses could be split into short standalone sentences without losing information.

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 three-parameter mutation with no output schema, it covers what matters most: required role, the user-consent gate, both decision branches, and the downstream queue/draft effects including the TikTok exception. Gaps are minor but real — it does not say what the note field is for beyond 'a note for the member', nor what a failed decision returns, though the 'notice says why' phrasing hints at the response shape.

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 67%: note and groupId carry descriptions, while decision's enum values have no per-value documentation in the schema. The description compensates by explaining what approve versus request_changes actually do, which meaningfully disambiguates the enum. It adds little on note (e.g. whether it is required or surfaced for request_changes), so this lands near the baseline rather than above it.

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?

The description gives specific verbs and resource: approve a member's pending post, or send it back with a note via request_changes, naming both enum values of the decision parameter. It is clearly the decision counterpart to the get_team_approval/get_post_approval readers, though it never names those siblings explicitly, so an agent must infer the read-vs-decide split from the titles alone.

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?

It supplies a real precondition (caller must be workspace owner or admin) and an explicit gating rule: 'Decide only when the user told you to.' That is strong when-to-use guidance. What is missing is the complementary route — nothing says to use clipember_get_team_approval first to discover pending requests, so discovery is left implicit.

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