Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

post_video

Publish a video to selected social platforms using a public URL or media library ID, with optional captions, scheduling, first comments, and format overrides.

Instructions

Post a video to social platforms. Accepts a public video URL or a media library ID (24-character hex MongoDB ObjectId).

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": {
      "connections": "<connections>",
      "video": "<video>"
    },
    "name": "post_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoCaption text for the post
videoYesPublic video URL or media library ID (24-char hex ObjectId)
connectionsYesConnection slugs to post to
scheduledAtNoISO 8601 datetime to schedule (omit to post immediately)
firstCommentNoOptional first comment
contentFormatNoContent format override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions accepted video identifiers but omits whether posts publish immediately, permission requirements, failure behavior, or side effects on connected accounts.

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 two short sentences, front-loaded with the primary action. Every sentence provides relevant information without unnecessary wording.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It identifies the purpose and video input format but leaves posting behavior, scheduling implications, and connection effects unexplained.

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 schema already explains all six parameters, including video URL/media ID format. The description restates the video input format but adds no meaning beyond the schema.

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?

The description states a specific verb and resource: 'Post a video to social platforms.' This clearly distinguishes it from sibling tools such as post_image and post_text without requiring the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied by the name and first sentence, but there is no explicit guidance on when to use this versus schedule_post, publish_draft, or other posting tools. No alternatives or exclusions are named.

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