Skip to main content
Glama

Read a post's team approval

clipember_get_team_approval
Read-onlyIdempotent

Read whether a post group (groupId from clipember_list_scheduled_posts) is waiting for your team's approval: state (none, pending = needs approval, approved, changes_requested), who asked and who decided, the note, whether "Members' posts need approval" is on (required), whether you can decide (canDecide: owner or admin) and whether your own posts need approval (yourPostsNeedApproval).

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_team_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe groupId of the post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the bar is lower, and the description still adds real behavior: the meaning of each state value ('pending = needs approval'), the permission rule behind canDecide ('owner or admin'), the workspace-level flag 'Members' posts need approval', and yourPostsNeedApproval. It does not address error conditions such as an unknown groupId or an unapproved/absent approval record.

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?

The single sentence is front-loaded with the action and then lists return fields in a parenthetical, so the critical information is read first. It is dense but nearly every clause carries meaning (state values, permission rule, workspace flags); a short break into a second sentence would improve readability without changing content.

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 one-parameter read tool with no output schema, the description effectively functions as the output contract by enumerating each returned field and its possible values. Combined with annotations covering the safety profile, an agent has everything needed to call it and interpret the result.

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?

With one parameter at 100% schema coverage, the baseline is 3, and the description earns above that by documenting provenance the schema does not: the groupId is a post-group identifier obtained from clipember_list_scheduled_posts, not a post ID. No format or validity details are added, but the schema already carries the UUID pattern.

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?

The description opens with a specific verb and resource ('Read whether a post group... is waiting for your team's approval') and then enumerates exactly what is returned (state, who asked, who decided, the note, canDecide, yourPostsNeedApproval). Naming clipember_list_scheduled_posts as the source of groupId and scoping everything to team approval makes it distinguishable from clipember_get_post_approval and the decide tool without opening a schema.

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?

Usage context is clear: call this to learn whether a group is blocked on team approval and whether you personally can act (canDecide: owner or admin), which implies it precedes clipember_decide_team_approval. It also points to clipember_list_scheduled_posts for obtaining the groupId. It stops short of explicitly naming the decide tool as the follow-up or stating any exclusion versus clipember_get_post_approval.

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