Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

post_image

Publishes one or more images to selected social platforms from public URLs or media library IDs, with optional captions, first comments, and scheduling.

Instructions

Post one or more images to social platforms. Accepts public image URLs or media library IDs (24-character hex MongoDB ObjectIds).

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>",
      "images": "<images>"
    },
    "name": "post_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoCaption text for the post
imagesYesPublic image URLs or media library IDs (24-char hex ObjectIds)
connectionsYesConnection slugs to post to
scheduledAtNoISO 8601 datetime to schedule (omit to post immediately)
firstCommentNoOptional first comment (e.g. hashtags)
contentFormatNoContent format override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the whole burden and discloses almost nothing: no permission/connection requirements, no statement of what happens when posting to multiple connections (all-or-nothing vs partial success), no rate limits, and no indication that posting is immediate or destructive. Only the accepted input formats are mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler. The second sentence largely duplicates the schema's images description, which is the only minor waste.

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?

This is a mutating, multi-connection post operation with no annotations and no output schema, so the description should explain return/failure behavior and connection prerequisites. Instead it covers only input formats, leaving the agent without the context needed to call it safely.

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 documents all six parameters, including the 24-char hex ID format and the media-type strings. The description restates the images parameter rather than adding new meaning, so the baseline 3 applies.

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?

"Post one or more images to social platforms" gives a specific verb and resource, and the image focus implicitly separates it from post_text and post_video. It stops short of naming any sibling or stating how it differs from schedule_post or publish_draft.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. An agent must infer from the word "images" that this is the media-type variant rather than post_text/post_video, and nothing explains when to use this versus schedule_post or publish_draft.

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