Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

schedule_posts

Schedule multiple text posts in one bulk call, each sent to selected connections at its own time. Returns created counts and per-item errors to simplify batch posting.

Instructions

Schedule MANY text posts in one call (bulk). Each item becomes its own scheduled post. Returns how many were created and any per-item errors. Use this instead of calling schedule_post repeatedly.

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": {
      "posts": "<posts>"
    },
    "name": "schedule_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsYesThe posts to schedule (1-500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and delivers the key behavioral fact for a bulk mutation: the call returns a created count plus per-item errors, so partial success is possible rather than all-or-nothing. It does not cover permission/auth requirements, rate limits, or constraints on scheduledAt (e.g., must be in the future), leaving some gaps.

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?

Three short sentences, front-loaded with the bulk scope, then the per-item behavior, then the return shape. No filler and no repetition of the name.

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

Completeness4/5

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

For a bulk write tool with no annotations and no output schema, the definition still conveys purpose, alternative routing, and return/failure semantics, which is most of what an agent needs. It falls short of complete because atomicity, permission requirements, and validation rules for scheduledAt are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the nested fields (text, title, connections, scheduledAt) are already documented and the baseline would be 3. The description adds genuine meaning beyond the schema by explaining that each element of the posts array produces its own separate scheduled post, clarifying array semantics rather than batch-combining.

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?

States a specific verb (schedule), resource (text posts), and scope (MANY/bulk, one call), then clarifies that each array item becomes an independent scheduled post. This lets an agent distinguish it from the single-item sibling schedule_post without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use this instead of calling schedule_post repeatedly' names the alternative and the condition (multiple posts) that selects this tool. The only minor omission is an explicit reverse rule for the single-post case, which is strongly implied.

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