Skip to main content
Glama

Socializioz — AI Social Media Manager

Media Preflight Validation

invoke_media_preflight
Read-onlyIdempotent

Checks a post's media against its platform/content type before schedule, publish, or retry. Returns valid or the required fix.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>"
    },
    "name": "invoke_media_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesSocializioz post ID.
platformNoAssert saved platform; else 409.
content_typeNoAssert saved content_type; else 409.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / content_type / description
      Previous value: -"Optional feed|story|reel|video override."New value: +"Assert saved content_type; else 409."
    • changedInput schema / properties / platform / description
      Previous value: -"Optional destination override."New value: +"Assert saved platform; else 409."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the useful gate semantics and that outcomes are "valid or the required fix," but does not characterize the shape of the fix payload or whether media must already be attached, leaving behavior only partly disclosed beyond annotations.

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?

Two short sentences, zero filler, with the trigger conditions front-loaded and the return contract following. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only validator with no output schema, the description should clarify what "the required fix" actually contains and whether prerequisites like attached assets are needed. It gestures at the return contract but leaves an agent guessing about result shape before calling.

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%, including the explicit 409 assertion semantics for platform and content_type, so the schema carries the parameter burden. The description only echoes the platform/content_type dimensions and adds no format or value guidance beyond that baseline.

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?

States a specific verb and resource ("Checks a post's media") and scopes it to three named workflows: schedule, publish, and retry. An agent can tell this is a pre-flight gate rather than the act of scheduling or publishing, though it never names a sibling tool directly.

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 clear trigger conditions ("before schedule, publish, or retry"), which map onto the sibling tools invoke_schedule_post, invoke_publish_now, and invoke_retry_failed_publication. It stops short of explicit when-not guidance or naming an alternative to skip.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources