Skip to main content
Glama

Add a post

add_post

Add a post to a campaign on one lane and day, as Promo's + does, with its words, the angle they take and a picture or video from the Library if you have them. It is a post on its own, not part of a moment, and a draft until it is scheduled. For more than one post, or the same post on several lanes, add_posts does it in one call.

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": {
      "campaign_id": "<campaign_id>",
      "lane": "<lane>",
      "date": "<date>"
    },
    "name": "add_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe day it goes out, YYYY-MM-DD, inside the campaign's window. A draft may be saved with a day gone by; Schedule asks for one still ahead (schedule_check says so).
laneYesWhere it goes.
testNoThe test this post is a variant of, or null to take it out: collab_starter (artist or audora: Who starts the Collab: the artist's post with Audora invited, or Audora's post with the artist invited). Audora pools each variant's posts at day 7 and calls the test once each variant has enough posts and one is clearly ahead; Admin shows the reading.
timeNoThe time it goes out, HH:MM 24-hour, in the artist's own time zone.
angleNoWhich of Audora's post angles the words take (the key names it: listener_pov is the listener's side of the song, tail_section a part of the track no other post used, hook_object an object the song names, and so on). Audora counts how each angle does for the artist, and promo_results' what_works shows the result. get_campaign shows each post's angle.
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
captionNoThe words of the post, as they will be published. The lane's limit and Audora's text rules apply (no placeholders, nothing that points back at another post).
dry_runNoTrue to check the call and see what it would do, without writing anything.
hashtagsNoUp to 12 hashtags, with or without #. Replaces the list.
link_urlNoA web address the post links to, or null to remove it.
campaign_idYesFrom list_campaigns.
media_asset_idNoA picture (for a picture post) or a video (for a video post) already in the artist's Library, by its media asset id. Audora does not make pictures or videos through this connection.
idempotency_keyNoSend the same key if you retry, and the change happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / test
      Added value: +{
      +  "description": "The test this post is a variant of, or null to take it out: collab_starter (artist or audora: Who starts the Collab: the artist's post with Audora invited, or Audora's post with the artist invited). Audora pools each variant's posts at day 7 and calls the test once each variant has enough posts and one is clearly ahead; Admin shows the reading.",
      +  "properties": {
      +    "test": {
      +      "enum": [
      +        "collab_starter",
      +        "sound",
      +        "format"
      +      ],
      +      "type": "string"
      +    },
      +    "variant": {
      +      "enum": [
      +        "artist",
      +        "audora",
      +        "official",
      +        "baked",
      +        "silent",
      +        "reel",
      +        "carousel"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "test",
      +    "variant"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"The day it goes out, YYYY-MM-DD, inside the campaign's window and not in the past."New value: +"The day it goes out, YYYY-MM-DD, inside the campaign's window. A draft may be saved with a day gone by; Schedule asks for one still ahead (schedule_check says so)."
  3. Changed1 schema field changed
    • changedInput schema / properties / angle / enum
      Previous value: -[
      -  "pin_angle.hook_object",
      -  "pin_angle.listener_pov",
      -  "pin_angle.lyric_line_on_beat",
      -  "pin_angle.occasion_day",
      -  "pin_angle.one_answerable_question",
      -  "pin_angle.ordinary_scene_contrast",
      -  "pin_angle.place_light_and_weather",
      -  "pin_angle.place_named_in_words",
      -  "pin_angle.release_fact_card",
      -  "pin_angle.repeat_what_worked",
      -  "pin_angle.scene_vocabulary",
      -  "pin_angle.story_line_that_nearly_went",
      -  "pin_angle.story_place",
      -  "pin_angle.tail_section",
      -  "pin_angle.uploaded_asset_hero"
      -]New value: +[
      +  "pin_angle.hook_object",
      +  "pin_angle.listener_pov",
      +  "pin_angle.lyric_line_on_beat",
      +  "pin_angle.occasion_day",
      +  "pin_angle.one_answerable_question",
      +  "pin_angle.ordinary_scene_contrast",
      +  "pin_angle.place_light_and_weather",
      +  "pin_angle.place_named_in_words",
      +  "pin_angle.release_fact_card",
      +  "pin_angle.repeat_what_worked",
      +  "pin_angle.scene_vocabulary",
      +  "pin_angle.show_coming_up",
      +  "pin_angle.story_line_that_nearly_went",
      +  "pin_angle.story_place",
      +  "pin_angle.tail_section",
      +  "pin_angle.uploaded_asset_hero"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / angle
      Added value: +{
      +  "description": "Which of Audora's post angles the words take (the key names it: listener_pov is the listener's side of the song, tail_section a part of the track no other post used, hook_object an object the song names, and so on). Audora counts how each angle does for the artist, and promo_results' what_works shows the result. get_campaign shows each post's angle.",
      +  "enum": [
      +    "pin_angle.hook_object",
      +    "pin_angle.listener_pov",
      +    "pin_angle.lyric_line_on_beat",
      +    "pin_angle.occasion_day",
      +    "pin_angle.one_answerable_question",
      +    "pin_angle.ordinary_scene_contrast",
      +    "pin_angle.place_light_and_weather",
      +    "pin_angle.place_named_in_words",
      +    "pin_angle.release_fact_card",
      +    "pin_angle.repeat_what_worked",
      +    "pin_angle.scene_vocabulary",
      +    "pin_angle.story_line_that_nearly_went",
      +    "pin_angle.story_place",
      +    "pin_angle.tail_section",
      +    "pin_angle.uploaded_asset_hero"
      +  ],
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive write with no idempotency guarantee; the description adds meaningful behavior on top: the result is a draft, it is not part of a moment, and media must already exist in the Library ('Audora does not make pictures or videos through this connection'). The draft-versus-scheduled distinction and the past-date allowance in the schema flesh this out further, though it does not mention permission requirements or rate limits.

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?

Three sentences, front-loaded with the core action, then the nature of the created object, then the alternative tool. The first sentence is a bit long and mixes several ideas, but nothing is redundant or wasted.

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 13-parameter write tool with no output schema, the definition covers purpose, creation semantics (draft, standalone), media sourcing limits, and the add_posts alternative, while the schema documents every parameter in depth. Remaining gaps are minor, such as what the call returns on success.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter already carries a detailed explanation, so the baseline is 3. The description restates the main inputs (caption, angle, media) but adds no syntax, formats, or constraints beyond what the schema supplies.

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?

Names a specific verb (add) and resource (a post) and pins down scope: one campaign, one lane, one day, with words, an angle, and optional Library media. It also states what the post is not ('a post on its own, not part of a moment'), which separates it from sibling concepts without requiring the 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?

Explicitly routes bulk work to add_posts ('For more than one post, or the same post on several lanes, add_posts does it in one call'), which is exactly the discrimination an agent needs. It also notes the result is a draft until scheduled. It does not cover other adjacent cases such as editing an existing post (update_post), but the guidance present is clear and actionable.

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