Socializioz — AI Social Media Manager

Create Draft Post

invoke_create_draft_post

Creates a DRAFT for one connected account. Requires social_account_id plus text or assets; use client_request_id to prevent duplicates.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Optional internal post title.
`message`	No	Main post body text.
`hashtags`	No	Hashtags without the leading #.
`asset_ids`	No	Existing workspace Asset IDs to attach.
`caption_ar`	No	Arabic caption variant.
`caption_en`	No	English caption variant.
`content_type`	No	feed\|story\|reel\|video; default feed.
`youtube_settings`	No	Optional YouTube-specific settings when social_account_id is a YouTube channel. Drafts may omit these; scheduling/publishing requires title, category_id, privacy_status, and an explicit self_declared_made_for_kids choice.
`client_request_id`	No	Idempotency key; reuse it to avoid duplicate drafts.
`social_account_id`	Yes	Target connected account ID from list_connected_accounts.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish this is a write operation. The description adds behavioral context: it is scoped to one connected account, it does not publish content, and passing client_request_id prevents duplicate drafts. No contradiction with the annotations is present.

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?

The description is compact and front-loaded: one sentence defines the operation and scope, and one follows up with prerequisites and idempotency. There is no wasted phrasing.

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 tool with 10 parameters and a nested youtube_settings object, the description plus 100% schema coverage is adequate. It does not describe output shape or explicitly route to follow-up tools like update_draft_post or publish_now, but the agent has enough to invoke 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 description coverage is 100%, so the baseline is 3. The description adds a useful combined-content requirement ('plus text or assets'), but most parameter meaning is already carried by the schema, including client_request_id's idempotency behavior.

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?

States a specific verb and object ('Creates a DRAFT') and the resource scope ('one connected account'). The word 'DRAFT' clearly distinguishes this from publishing, scheduling, or approving siblings.

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 clear context: the call creates only a draft for one connected account, and requires a social_account_id plus text or assets. It also mentions the client_request_id deduplication mechanism, though it doesn't explicitly name sibling tools such as update_draft_post or schedule_post.

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

All Socializioz — AI Social Media Manager tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

Most tools target a distinct resource and lifecycle state, so an agent can usually pick correctly. The main ambiguity is among the profile/context tools and the approve/schedule/publish family, but the descriptions give enough state-specific detail to avoid serious misselection.

Naming Consistency4/5

The set consistently uses an invoke_ prefix with snake_case and mostly follows a verb_noun pattern. It only deviates with names like media_preflight and x_live_read, which place the verb at the end or use noun phrases.

Tool Count2/5

With 33 tools, the server is well beyond the typical well-scoped range. It covers many distinct areas, but the high number of status-specific post tools and separate context/profile/workspace tools makes the surface feel bloated rather than cohesive.

Completeness3/5

The core social publishing workflow is covered well: create, edit, approve, schedule, publish, cancel, retry, and campaign planning. However, there are notable gaps such as no delete/archive for drafts, campaigns, or assets, and limited tools for inbox, comment, or broader analytics beyond the single X read gateway.

Resources

Need Help?