Skip to main content
Glama

company update post

company_update_post
DestructiveIdempotent

Update an existing Agency draft. Save edits before media, client review or scheduling; changed text, channels or publishing settings (including TikTok autoAddMusic) invalidates client approval. Empty platforms allows a channel-less draft. Copy channel keys from company_list_channels. draft.firstComment accepts one {text, platforms?}; null clears it on update. Supported: linkedin (profiles and Pages), twitter, threads, bluesky, mastodon; other targets are skipped. Backend checks platform-specific length. No status, scheduledTime or mediaUrls fields: upload via company_reserve_media/company_complete_media, then use company_schedule_post. Verify with company_get_post. 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>",
      "draft": "<draft>"
    },
    "name": "company_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
postGroupIdYesExact ID returned by a Company tool; never a personal platformId
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
idempotencyKeyYesStable visible-ASCII key, 1–255 characters, no comma/whitespace. On lost response retry the IDENTICAL body and key; never mint a new key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / draft / properties / platformSettings / properties / tiktok / properties / allowComments / description
      Added value: +"Default false for new posts. Enable comments only after the creator explicitly opts in; Company updates replace platformSettings when supplied; include saved choices you want to retain."
    • addedInput schema / properties / draft / properties / platformSettings / properties / tiktok / properties / allowDuet / description
      Added value: +"Default false for new posts. Enable Duet only after the creator explicitly opts in; Company updates replace platformSettings when supplied; include saved choices you want to retain."
    • addedInput schema / properties / draft / properties / platformSettings / properties / tiktok / properties / allowStitch / description
      Added value: +"Default false for new posts. Enable Stitch only after the creator explicitly opts in; Company updates replace platformSettings when supplied; include saved choices you want to retain."
  2. Changed4 schema fields changed
    • addedInput schema / properties / draft / properties / platformSettings / properties / instagram / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose AI-generated content: adds Instagram's \"AI info\" label. Required by Meta for realistic AI-generated or AI-altered video, audio or images; cannot be changed after publishing. Default false",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / draft / properties / platformSettings / properties / tiktok / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose AI-generated content: adds TikTok's \"Creator labeled as AI-generated\" label. Required for realistic AI-generated video or images. Default false",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / draft / properties / platformSettings / properties / twitter
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "aiGenerated": {
      +      "description": "Self-disclose AI-generated media (X \"Made with AI\"). Sent only when the post attaches media. Default false",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / draft / properties / platformSettings / properties / youtube / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose altered or synthetic content (status.containsSyntheticMedia). Required for realistic AI-generated or AI-altered video or audio. Default false",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / draft / properties / repostSourceSnapshot
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "authorName": {
      +          "anyOf": [
      +            {
      +              "maxLength": 300,
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "capturedAt": {
      +          "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"
      +        },
      +        "commentary": {
      +          "maxLength": 30000,
      +          "type": "string"
      +        },
      +        "postedId": {
      +          "pattern": "^urn:li:(?:share|ugcPost):[0-9]{1,32}$",
      +          "type": "string"
      +        },
      +        "publishedAt": {
      +          "anyOf": [
      +            {
      +              "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"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "required": [
      +        "postedId",
      +        "commentary",
      +        "capturedAt"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Copy the chosen finder item sourceSnapshot verbatim, matched to linkedin.repostParentUrn. Saves an original-post preview for client review; null clears it. It is descriptive and does not change the LinkedIn original or publishing permissions."
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / draft / properties / platformSettings / properties / tiktok / properties / autoAddMusic
      Added value: +{
      +  "description": "Photo Direct Post only. Opt in with true to let TikTok automatically choose music; Publora cannot select or preview a specific track. False disables music and is allowed when switching to video. Omission preserves existing behavior. Videos never send this parameter.",
      +  "type": "boolean"
      +}
  5. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, so the safety profile is partly given, but the description adds a consequence not present in structured data: changed text, channels or publishing settings invalidates client approval. It also discloses that unsupported targets are silently skipped and that the backend enforces platform length limits. It does not say whether settings omitted from platformSettings are wiped, which matters for a destructive update.

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 the core action and the save-order warning, then moves to platform and field constraints. It is dense and every clause carries operational meaning, though the platform support list and skip note sit somewhat awkwardly mid-paragraph.

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 destructive, deeply nested, four-required-parameter mutation with no output schema, the description covers sequencing, idempotency, supported targets and verification. The remaining gap is replacement semantics for platformSettings and platformContents on update, which the schema hints at but never states outright.

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 description coverage is 75%, so the schema already carries substantial meaning, but the description adds real value: empty platforms semantics, the instruction to copy channel keys from company_list_channels, firstComment accepting exactly one object with null clearing it, and the explicit absence of status/scheduledTime/mediaUrls fields. That last point prevents a common misuse that the schema alone would only imply by omission.

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?

"Update an existing Agency draft" gives a specific verb plus a scoped resource (Agency draft), which cleanly separates it from company_create_post and company_get_post. The description immediately adds the constraint set that distinguishes an edit operation from a create.

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 ordering explicitly ("save edits before media, client review or scheduling") and routes every adjacent concern to a named sibling: media via company_reserve_media/company_complete_media, scheduling via company_schedule_post, verification via company_get_post, channel keys via company_list_channels. The retry rule for a lost response closes the loop with a concrete condition.

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.