· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →socializioz v1.0.0
Run Social media From ChatGPT
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Show my connected social accounts
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
One conversation. Real execution. Manage your social media directly from ChatGPT, with full control over your campaigns, connected accounts, content, approvals, scheduling, and publishing. Plan campaigns, turn ideas into posts, review and approve content, schedule or reschedule posts, manage media, and publish to your social platforms — without leaving ChatGPT.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: socializioz-content-operations description: Plan, draft, review, schedule, publish, and organize social media work through Socializioz. Use for Socializioz workspace and brand orientation, connected-account selection, evidence-safe campaign strategy, platform and content-format decisions, campaign plans, post drafts, media preparation, approval workflows, scheduled publishing, immediate publishing, publication retries, and authorized X research. --- # Socializioz Content Operations Use Socializioz as the source of truth for the active workspace, brand, connected accounts, posts, campaigns, media, approvals, and publication state. Read [references/tool-map.md](references/tool-map.md) before a multi-step operation or whenever exact action boundaries are unclear. Read [references/marketing-practice.md](references/marketing-practice.md) when planning strategy, choosing platforms or formats, writing content, selecting timing, or evaluating claims. ## Orient before acting 1. Call `invoke_get_user_profile` before a multi-step workflow. 2. If the active workspace is unclear, use `invoke_list_user_workspaces` and ask the user to choose by friendly workspace name. 3. Read `invoke_get_brand_profile` and `invoke_list_connected_accounts` before creating brand-specific content or choosing a publishing target. 4. If the requested client or brand conflicts with the active Brand Profile, ask whether to continue for the external client or switch to the connected brand. 5. For an external client, plan without binding content to the active connected brand. Bind or publish only after the user chooses the intended connected account. 6. Use account capability and health flags as authoritative; never assume a platform connection can publish. 7. Do not expose raw internal identifiers. Retain returned identifiers only for follow-up tool calls. ## Decide before creating 1. Identify the objective, audience, offer, campaign or one-off scope, target platforms, language, and available evidence. 2. Choose platforms and formats from the objective and available assets; do not mechanically duplicate identical copy across every channel. 3. Use campaigns and campaign plan items for coordinated initiatives. Use a direct draft for a one-off post. 4. Preserve explicit user wording, language, audience, constraints, and blocked terms. 5. Never invent performance metrics, customer results, case studies, certifications, market facts, trends, or competitor behavior. 6. Mark unsupported claims with an explicit verification placeholder and ask for evidence before presenting them as facts. 7. Treat proposed posting times as hypotheses unless supported by the user's own verified data. State the timezone. ## Draft and review - Create an unpublished draft before approval, scheduling, or publishing unless the user explicitly requests an immediate eligible publication. - Create one draft per connected destination account. Adapt the hook, length, CTA, hashtags, and format to that platform. - Keep campaign planning, plan-item conversion, drafting, approval, scheduling, and publishing as distinct lifecycle steps. - After a write, report only what the tool result confirms. Never describe a draft as scheduled or a scheduled post as published. - Before another lifecycle action, use `invoke_get_post` when the current post state or available action flags may have changed. ## Prepare media 1. Prefer existing workspace assets found with `invoke_list_workspace_assets` and `invoke_get_asset`. 2. For a public HTTPS media source, use `invoke_import_media_from_url` before attaching it. 3. Attach media only to the intended draft with `invoke_attach_assets_to_post`. 4. Run `invoke_media_preflight` before scheduling, publishing, or retrying a media post. 5. Never assume a chat attachment is automatically available to an MCP tool. Use a host-provided file reference only when the tool call actually receives one; otherwise request a public HTTPS URL or use an existing workspace
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 4 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_6a760fb673f481918fe419964ecf7085
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.