@omnisocials/mcp-server 1.3.5 → 1.3.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -191,6 +191,15 @@ Full API docs: [docs.omnisocials.com](https://docs.omnisocials.com)
|
|
|
191
191
|
|
|
192
192
|
## Changelog
|
|
193
193
|
|
|
194
|
+
### 1.3.6
|
|
195
|
+
|
|
196
|
+
- Metadata-only republish of 1.3.5 to refresh the README on npmjs.com. No code changes from 1.3.5.
|
|
197
|
+
|
|
198
|
+
### 1.3.5
|
|
199
|
+
|
|
200
|
+
- **Fixed:** YouTube Shorts `title`, `tags`, `privacy_status`, `category_id`, `made_for_kids`, `notify_subscribers`, and `contains_synthetic_media` now actually take effect when publishing through MCP/API. Previously the publisher silently ignored these and every Short went live as "YouTube Short" with default privacy. Companion server fix — clients on 1.3.4 also benefit once the backend deploys; 1.3.5 only refreshes the tool descriptions.
|
|
201
|
+
- Tool descriptions clarify that the `youtube` options block only applies when `type` is `"reel"` and `youtube` is among the selected channels, and that `title` falls back to `"YouTube Short"` when omitted.
|
|
202
|
+
|
|
194
203
|
### 1.3.4
|
|
195
204
|
|
|
196
205
|
- **Prevent accidental publishing.** Tool descriptions now front-load the difference: `create_post` is explicitly the **draft** path, `create_and_publish_post` carries a `STOP` gate listing every phrasing ("draft", "schedule", "review first", "save it", etc.) that should make the agent fall back to `create_post`. Default is "create draft" whenever there's ambiguity.
|
package/package.json
CHANGED