Skip to main content
Glama

company request post approval

company_request_post_approval
DestructiveIdempotent

Request a new client review round as Manager. Save all draft edits and finish media uploads first. Clients can approve, decline with an optional comment, or request changes with a comment. Changed text, channels or media invalidates approval; changing publishing settings, including TikTok autoAddMusic, also requires a new review. Optional scheduledTime schedules this version automatically after approval through the existing scheduler. Omit it to keep the approved post as a draft. If the time passes before approval, the decision is saved but the post stays a draft; choose a new time. Changing the time of a pending review requires a new round; after approval, use the existing reschedule/unschedule commands. Returns a private bearer review link for manual sharing only; do not autonomously send it or infer client approval. On a lost response retry the identical body and idempotencyKey.

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": {
      "workspaceId": "<workspaceId>",
      "postGroupId": "<postGroupId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "company_request_post_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
postGroupIdYesExact ID returned by a Company tool; never a personal platformId
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
scheduledTimeNoOptional future UTC publication time, e.g. 2026-12-01T12:00:00.000Z. Set only when the user wants automatic scheduling after client approval. Omit for manual publication.
idempotencyKeyYesStable visible-ASCII key, 1–255 characters, no comma/whitespace. On lost response retry the IDENTICAL body and key; never mint a new key
managerCommentNoOptional saved-post review instructions for the client

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scheduledTime
      Added value: +{
      +  "description": "Optional future UTC publication time, e.g. 2026-12-01T12:00:00.000Z. Set only when the user wants automatic scheduling after client approval. Omit for manual publication.",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the return value is a private bearer review link for manual sharing only, the agent must not autonomously send it or infer approval, and retries after a lost response must use the identical body and idempotencyKey. It also explains scheduledTime outcomes and approval invalidation rules, adding substantial context not present in the annotations.

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 description is front-loaded with purpose and remains dense with relevant rules, with no obvious filler. It is somewhat paragraph-heavy for a complex operation, but the length is justified by the number of behavioral constraints it must convey.

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 complex mutation tool with no output schema, the description covers permissions, prerequisites, client decision flows, invalidation conditions, scheduling behavior, idempotency, and safe handling of the returned review link. Nothing critical for correct invocation appears to be missing.

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 100%, so the schema carries the primary parameter documentation. The description still adds useful meaning for scheduledTime and idempotencyKey, including scheduling-after-approval behavior and safe retry semantics, though it does not elaborate on managerComment beyond what the schema already provides.

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: 'Request a new client review round as Manager.' It clearly distinguishes the tool from siblings such as company_get_post_approval, company_cancel_post_approval, and reschedule/unschedule commands by focusing on initiating a new review round.

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 explicitly states prerequisites like saving draft edits and finishing media uploads, and explains when a new round is required versus when to use existing reschedule/unschedule commands. It also covers client outcomes and invalidation triggers, giving clear when-to-use and when-not-to-use guidance.

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.