Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

post_text

Publish text content to one or more connected social media accounts immediately, with an optional first comment for hashtags.

Instructions

Post text content to one or more connected social media accounts immediately.

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": {
      "caption": "<caption>",
      "connections": "<connections>"
    },
    "name": "post_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYesThe text content to post
connectionsYesArray of connection slugs to post to (e.g. ["twitter-me", "linkedin-company"])
firstCommentNoOptional first comment to add after posting (e.g. hashtags)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses one useful trait — the post goes out immediately — but says nothing about confirmation/permission requirements, rate limits, whether a failure on one connection aborts the others, or whether the action is irreversible. For an unannotated write tool that is a significant gap.

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?

A single front-loaded sentence with no filler; the immediacy constraint appears early where an agent will see it. Nothing could be cut without losing information.

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 multi-target mutation tool with no annotations and no output schema, the description leaves the agent unable to predict outcomes: no statement about what is returned (post IDs? per-connection status?), what happens on partial failure, or whether the caller should verify with check_post_status. Incomplete relative to the tool's complexity.

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% and the schema already documents caption, connections, and firstComment with examples and a minItems constraint. The description only echoes the "one or more accounts" semantics of connections and adds nothing about caption length, slug format, or firstComment behavior.

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 ("Post"), a specific resource type ("text content"), and scope ("one or more connected social media accounts"), which naturally separates it from post_image, post_video, and schedule_post. It stops short of naming those siblings, so differentiation is inferred rather than stated.

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?

"Immediately" implies the tool publishes now rather than queuing, which hints at when to prefer it over a scheduling tool, but no alternative is named and no preconditions (connected/valid accounts, caption limits) are given. Usage is implied, not prescribed.

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