Skip to main content
Glama
Sign In

Audora

by music.audora
OverviewDiscussionsAdmin

Change a post

update_post

Change a post's words, hashtags, link, day, time, its picture or video (from the Library), or the angle its words take. Send only what changes. Returns the post with schedule_check: what Schedule would decide now. A post already scheduled can be changed only with the schedule permission; one already handed to its platform's own schedule (Facebook, YouTube) or one that went out cannot be changed here.

Input Schema

NameRequiredDescriptionDefault
dateNoThe 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).
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.
post_idYesThe post's id (post_id from get_campaign or promo_this_week).
hashtagsNoUp to 12 hashtags, with or without #. Replaces the list.
link_urlNoA web address the post links to, or null to remove it.
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
    • 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)."
  2. 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"
+]
  3. 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"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the boolean safety profile; the description goes much further by disclosing the permission gate for scheduled posts, the hard boundary for posts already pushed to Facebook/YouTube or published, the partial-update contract, and the return payload (the post plus schedule_check). Nothing here contradicts readOnlyHint=false or destructiveHint=false.

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, each with a distinct job: what can change, how to send it, and what comes back plus the constraints. Front-loaded with the mutable field list. Slightly dense in the first sentence but no filler.

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?

No output schema exists, so the description must describe the return value, and it does ('the post with schedule_check: what Schedule would decide now'). Combined with permission requirements and the cases where the call is rejected, an agent has everything needed to invoke this correctly.

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%, so the schema already documents all 11 parameters, including the enum values for angle and the Library constraint on media_asset_id. The description's field list largely restates what the schema covers; 'Send only what changes' is the one genuine semantic addition. Baseline 3 applies.

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 (Change) and resource (a post), then enumerates exactly which fields are mutable (words, hashtags, link, day, time, picture/video, angle). An agent can immediately distinguish this from add_post, keep_post, and skip_post without opening any 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?

Gives explicit partial-update guidance ('Send only what changes') and clear when-not conditions: a post already handed to its platform's own schedule or already published cannot be changed here, and a scheduled post needs the schedule permission. It does not name a sibling alternative for the excluded cases, so it falls just short of the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Audora toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources