Skip to main content
Glama
Sign In
@fopost/mcp

@fopost/mcp

Official
by fopost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schedule_post

Schedule or publish social media posts by providing body text, target account IDs, and an optional ISO 8601 time. Set publish_now to true for immediate publishing, or omit the schedule time to save as a draft.

Instructions

Create and schedule a post. Pass the body text, target account ids, and an ISO 8601 schedule_at. Omit schedule_at to save as draft. Use publish_now=true to publish immediately after creation.

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": {
      "workspace_id": "<workspace_id>",
      "content": "<content>",
      "account_ids": "<account_ids>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsNo
contentYesPost body text
media_urlsNoPre-uploaded media URLs from /api/v1/media/upload
account_idsYesTarget social account ids (uuids)
publish_nowNo
schedule_atNoISO 8601 timestamp; omit to save as draft
workspace_idYesWorkspace id (uuid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the mutation (create/schedule) and the two behavior branches (draft vs immediate publish), but does not mention side effects, return values, or error handling. It adds useful context but lacks depth for a mutation tool with no annotations.

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 sentences with front-loaded main action and clear variations. Each sentence earns its place; no waste or repetition.

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 7-parameter creation tool with no output schema, the description covers the essential actions and branches. It omits explicit mention of required workspace_id and doesn't describe the response, but the schema provides required fields and the variations are clear. Slightly incomplete but adequate for typical use.

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 71%; description clarifies content, account_ids, and schedule_at format (ISO 8601), and adds behavior for publish_now. However, it says nothing about workspace_id, labels, or media_urls, which are only partially covered by schema descriptions. The description adds value but does not fully compensate for the uncovered parameters.

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 ('Create and schedule') and resource ('a post'), with clear scope. It distinguishes from siblings like delete_post and edit_post by naming the creation/scheduling action and its variations.

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

Usage Guidelines4/5

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

Provides explicit usage conditions: omit schedule_at to save as draft, use publish_now=true for immediate publication. Gives clear context on when to use the tool, though it does not explicitly name alternatives or exclusions—but the primary use case is well-defined.

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

Deploy Server

Other Tools