Skip to main content
Glama

Send a post for client approval

request_approval
Destructive

The approval flow: a client reviewer (not a Shager user) gets a link, opens it on their phone without logging in, sees the post per account and approves it or asks for changes (with a comment). The post moves to IN_REVIEW; get_approval shows the decision (APPROVED or CHANGES_REQUESTED); revoke_approval takes the link back while it is pending; an APPROVED post can be scheduled as long as its content is unchanged. An approval requested by an agent never schedules the post by itself, even when it has a date: once get_approval shows APPROVED, call schedule_post. Returns the link to send (and a WhatsApp link when the reviewer has a phone); send_email emails it. When the workspace has approval_required, Shager emails the link to the reviewer itself (reviewer_email and send_email: true are required) and the link is not returned, so the agent can't approve its own post. Useful anyway when a human should look first. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>",
      "reviewer_name": "<reviewer_name>"
    },
    "name": "request_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
send_emailNo
workspace_idYesWorkspace id from list_workspaces
reviewer_nameYes
reviewer_emailNo
reviewer_phoneNo
idempotency_keyNoAny unique string you choose (REST: the Idempotency-Key header works too). Retrying with the same key and body returns the first result instead of creating a second one. Kept 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructive, open-world, non-idempotent), it discloses the state transition to IN_REVIEW, that an agent-requested approval never auto-schedules even with a date, and that under approval_required the link is withheld and Shager emails the reviewer itself. Those are non-obvious side effects an agent must know before calling a mutating tool.

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?

Every sentence carries operational information (flow, follow-ups, return values, workspace mode, sandbox limit), so little is wasted. The trade-off is that it is one dense, run-on paragraph rather than a front-loaded purpose statement followed by structured detail.

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?

With no output schema, the description compensates by stating what is returned (the link, plus a WhatsApp link when a phone is given) and noting the case where no link comes back. Combined with the scheduling follow-up, workspace-mode behavior, and sandbox restriction, an agent has everything needed to call and act on 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?

Schema coverage is only 29%, but the description compensates for the ambiguous ones: send_email emails the link, reviewer_email is required under approval_required, and reviewer_phone yields a WhatsApp link. reviewer_name and post_id are left to the schema, and idempotency_key is only documented by the schema itself, so a small gap remains.

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 establishes a specific verb+resource (requesting client approval for a post) and explicitly separates it from get_approval, revoke_approval, and schedule_post. An agent can tell this is the tool that initiates the review flow and returns the reviewer link, not the one that reads the decision or schedules.

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?

It states exactly when to use it ('Useful anyway when a human should look first'), what to do afterwards ('once get_approval shows APPROVED, call schedule_post'), and which sibling handles each follow-up step. It also gives an explicit condition and exclusion: not available in an unclaimed sandbox, and under approval_required the agent cannot approve its own post.

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