Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

schedule_post

Schedule a text post for a specific date and time across chosen social connections, and add an optional first comment for hashtags.

Instructions

Schedule a text post to publish at a specific date and time.

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>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYesThe text content to post
connectionsYesArray of connection slugs
scheduledAtYesISO 8601 datetime when to publish (e.g. "2026-06-15T09:00:00Z")
firstCommentNoOptional first comment (e.g. hashtags)

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, the description carries the full disclosure burden and does little: it does not say whether the post is queued and editable before firing, what happens on failure, whether connections require prior reconnection, or timezone expectations for scheduledAt. Only the bare 'deferred mutation' nature is conveyed.

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?

A single front-loaded sentence with no filler, and the essential scope (text post, scheduled time) comes first. It is efficient but borders on under-specified rather than tight, since nothing else follows.

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 4-parameter, 3-required mutation tool with no annotations and no output schema, so the description should explain what the call returns (a scheduled post id?), whether the schedule can be changed later, and failure conditions. None of that is present, leaving a significant gap for a write operation.

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 caption, connections, scheduledAt, and firstComment are already documented with formats and an example — baseline 3 applies. The description adds no extra meaning, such as whether connections are account slugs versus platform names or whether caption length is constrained per platform.

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?

The description states a specific verb and resource — schedule a text post — plus the deferred timing, so the agent knows this creates a future publication rather than an immediate one. It does not distinguish itself from plausible siblings like post_text (immediate) or schedule_posts (possibly bulk), leaving the boundary to be inferred.

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?

No when-to-use guidance is given: nothing says to prefer this over post_text for immediate publishing, over schedule_posts for multiple posts, or that scheduledAt must be in the future. The agent must guess the selection criteria from tool names alone.

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