Skip to main content
Glama
fav-devs

Sociona MCP Server

by fav-devs

schedule_post

Schedule a social media post for future publication on X, Instagram, or Threads. Set content, date, and optional media attachments.

Instructions

Schedule a post for future publication

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYes
contentYesPost content
scheduledForYesISO 8601 datetime (e.g., 2025-10-14T10:00:00Z)
mediaUrlsNoOptional media URLs to attach

Implementation Reference

  • Handler function that schedules a post: fetches accounts, finds the matching platform account, then calls POST /schedule API with accountId, platform, content, scheduledFor, and mediaUrls.
    private async schedulePost(args: any) {
      const { accounts } = await this.apiRequest('GET', '/accounts');
      const account = accounts.find((a: any) => a.provider === args.platform);
    
      if (!account) {
        throw new Error(`No ${args.platform} account connected. Available accounts: ${accounts.map((a: any) => a.provider).join(', ')}`);
      }
    
      const result = await this.apiRequest('POST', '/schedule', {
        accountId: account.id,
        platform: args.platform,
        content: args.content,
        scheduledFor: args.scheduledFor,
        mediaUrls: args.mediaUrls || [],
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `✅ Post scheduled for ${args.scheduledFor} on ${args.platform}!\nScheduled Post ID: ${result.scheduledPost.id}`,
          },
        ],
      };
    }
  • Schema registration for schedule_post tool defining input properties: platform (enum X/INSTAGRAM/THREADS), content (string), scheduledFor (ISO 8601 string), and optional mediaUrls (string array). Required: platform, content, scheduledFor.
    {
      name: 'schedule_post',
      description: 'Schedule a post for future publication',
      inputSchema: {
        type: 'object',
        properties: {
          platform: {
            type: 'string',
            enum: ['X', 'INSTAGRAM', 'THREADS'],
          },
          content: {
            type: 'string',
            description: 'Post content',
          },
          scheduledFor: {
            type: 'string',
            description: 'ISO 8601 datetime (e.g., 2025-10-14T10:00:00Z)',
          },
          mediaUrls: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional media URLs to attach',
          },
        },
        required: ['platform', 'content', 'scheduledFor'],
      },
  • src/index.ts:30-130 (registration)
    Tool registration via ListToolsRequestSchema handler, listing schedule_post as one of the available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'publish_post',
          description: 'Publish a social media post immediately',
          inputSchema: {
            type: 'object',
            properties: {
              platform: {
                type: 'string',
                enum: ['X', 'INSTAGRAM', 'THREADS'],
                description: 'Social media platform',
              },
              content: {
                type: 'string',
                description: 'Post content/text',
              },
              mediaUrls: {
                type: 'array',
                items: { type: 'string' },
                description: 'Optional media URLs to attach',
              },
            },
            required: ['platform', 'content'],
          },
        },
        {
          name: 'schedule_post',
          description: 'Schedule a post for future publication',
          inputSchema: {
            type: 'object',
            properties: {
              platform: {
                type: 'string',
                enum: ['X', 'INSTAGRAM', 'THREADS'],
              },
              content: {
                type: 'string',
                description: 'Post content',
              },
              scheduledFor: {
                type: 'string',
                description: 'ISO 8601 datetime (e.g., 2025-10-14T10:00:00Z)',
              },
              mediaUrls: {
                type: 'array',
                items: { type: 'string' },
                description: 'Optional media URLs to attach',
              },
            },
            required: ['platform', 'content', 'scheduledFor'],
          },
        },
        {
          name: 'get_accounts',
          description: 'Get list of connected social media accounts',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
        {
          name: 'get_posts',
          description: 'Get recent posts published via the API',
          inputSchema: {
            type: 'object',
            properties: {
              limit: {
                type: 'number',
                description: 'Number of posts to retrieve (max 100)',
                default: 50,
                minimum: 1,
                maximum: 100,
              },
            },
          },
        },
        {
          name: 'cancel_scheduled_post',
          description: 'Cancel a scheduled post before it publishes',
          inputSchema: {
            type: 'object',
            properties: {
              postId: {
                type: 'string',
                description: 'The ID of the scheduled post to cancel',
              },
            },
            required: ['postId'],
          },
        },
        {
          name: 'get_post_stats',
          description: 'Get statistics about your posts',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
      ],
    }));
  • src/index.ts:140-141 (registration)
    Call routing in CallToolRequestSchema: when name is 'schedule_post', invokes the schedulePost handler method.
    case 'schedule_post':
      return await this.schedulePost(args);
Behavior2/5

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

No annotations exist, so the description carries full burden. It only states the basic action without disclosing important behavioral traits such as permission requirements, error handling, idempotency, or constraints on future dates. The description adds minimal behavioral context.

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?

The description is a single short phrase, efficient and clear. It is appropriately sized and front-loaded, though it sacrifices detail for brevity. An extra sentence on behavior would improve completeness.

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?

Given 4 parameters (3 required), no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, or validation rules for the parameters. More context is needed for correct invocation.

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 75% (content, scheduledFor, mediaUrls have descriptions). The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the verb 'schedule' and the resource 'post', with the temporal qualifier 'for future publication'. It differentiates from siblings like 'publish_post' (immediate) and 'cancel_scheduled_post' (opposite action).

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?

The description provides no guidance on when to use this tool versus alternatives like 'publish_post'. There is no mention of prerequisites, exclusions, or context for scheduling vs immediate posting.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fav-devs/sociona-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server