Skip to main content
Glama

company create post

company_create_post
Idempotent

Create an Agency draft without scheduling or publishing. Personal create_post is not interchangeable. 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>",
      "idempotencyKey": "<idempotencyKey>",
      "draft": "<draft>"
    },
    "name": "company_create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
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 already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, yet the description still adds real behavior: which platform targets are supported and that others are silently skipped, backend platform-specific length checks, and the absence of status/scheduledTime/mediaUrls fields. The retry protocol is spelled out, though the description does not say what an actual skipped-target response looks like.

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?

Dense but front-loaded: the core purpose and the sibling distinction come first, then constraints, then the media/scheduling handoff, then the retry rule. Nearly every clause carries operational information, though the media/verify/retry material could be tightened slightly.

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 tool with a deeply nested draft object and no output schema, the description covers the main decision points and explicitly delegates verification to company_get_post and format rules to company_get_platforms. The remaining gap is that outcome/return shape and partial-failure behavior are left implicit.

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 67% schema description coverage the schema does much of the work, but the description adds non-obvious meaning: platforms must be exact keys copied from company_list_channels, an empty array yields a channel-less draft, and draft.firstComment takes a single object (or null to clear) rather than an array. That is genuine value beyond the schema text.

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?

"Create an Agency draft without scheduling or publishing" names the specific verb (create), the resource (Agency draft) and the scope limit (no schedule, no publish). The second sentence explicitly separates it from the personal `create_post` sibling, so an agent can route correctly without opening either schema.

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?

Gives concrete when-to-use and when-not-to rules: not interchangeable with personal create_post, empty platforms for a channel-less draft, use company_schedule_post for scheduling, use company_get_post to verify, and retry with the identical body on a lost response. Alternatives are named with the condition that selects them.

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.