Audora

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

TableJSON Schema

Name	Required	Description
`date`	No	The day it goes out, YYYY-MM-DD, inside the campaign's window and not in the past.
`time`	No	The time it goes out, HH:MM 24-hour, in the artist's own time zone.
`angle`	No	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.
`artist`	No	Only 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.
`caption`	No	The 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_run`	No	True to check the call and see what it would do, without writing anything.
`post_id`	Yes	The post's id (post_id from get_campaign or promo_this_week).
`hashtags`	No	Up to 12 hashtags, with or without #. Replaces the list.
`link_url`	No	A web address the post links to, or null to remove it.
`media_asset_id`	No	A 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_key`	No	Send the same key if you retry, and the change happens once.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

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"
+]

Changed1 schema field changedOct 5, 2026

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"
+}

First observedOct 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations covering safety/idempotency, the description adds real behavioral context: patch semantics ('send only what changes'), the permission requirement for scheduled posts, the boundary of what is mutable, and a return-value preview (schedule_check) despite no output schema. It does not explain what happens to fields omitted, but the coverage is well above the annotation baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then patch behavior and return shape, then the mutability constraints. No filler, and each sentence adds distinct information.

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 no-output-schema mutation tool with 11 parameters, the description covers the return value (schedule_check), dry_run, idempotency, permissions, and immutability boundaries. An agent has what it needs to call it 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 coverage is 100%, so every parameter is already documented in the schema. The description reinforces the key semantic that only changed fields should be sent and clarifies media must come from the Library, but largely restates the field list already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Change) and resource (a post) and enumerates exactly what can be changed: words, hashtags, link, day, time, media, angle. It is clearly a partial-update tool, which implicitly distinguishes it from add_post/keep_post/skip_post, but it never names a sibling explicitly.

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?

It gives strong when-not guidance: a scheduled post needs the schedule permission, and posts already handed to a platform's own scheduler or already published cannot be changed here. It does not point the agent to an alternative tool for those blocked cases, so it stops short of full routing guidance.

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

All Audora tools Inspect

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

Need Help?