Skip to main content
Glama

Schedule Content

schedule_content

Schedule social media posts for LinkedIn, Instagram, X, or TikTok by specifying content, platform, and date/time to save to a publishing queue.

Instructions

Save content to the publishing queue (content-queue.json). Stores the post with platform, scheduled date/time, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe post content to schedule
platformYesTarget platform
scheduled_dateYesScheduled date (YYYY-MM-DD)
scheduled_timeNoScheduled time (HH:MM, default 09:00)09:00

Implementation Reference

  • The handler function for schedule_content which reads the current queue, creates a new queue item, adds it, and writes the updated queue to the file.
      async ({ content, platform, scheduled_date, scheduled_time }) => {
        const queue = readQueue();
        const item: QueueItem = {
          id: generateId(),
          content,
          platform,
          scheduled_date,
          scheduled_time,
          status: "pending",
          created_at: new Date().toISOString(),
        };
    
        queue.push(item);
        writeQueue(queue);
    
        const output = [
          "Contenu ajoute a la file d'attente !",
          "",
          `ID: ${item.id}`,
          `Plateforme: ${platform}`,
          `Date: ${scheduled_date} a ${scheduled_time}`,
          `Statut: pending`,
          `Longueur: ${content.length} caracteres`,
          "",
          `Total en file: ${queue.length} posts`,
          `Fichier: ${QUEUE_FILE}`,
        ].join("\n");
    
        return {
          content: [{ type: "text" as const, text: output }],
        };
      },
    );
  • src/index.ts:888-902 (registration)
    The registration of the schedule_content tool with its title, description, and input schema.
    server.registerTool(
      "schedule_content",
      {
        title: "Schedule Content",
        description:
          "Save content to the publishing queue (content-queue.json). " +
          "Stores the post with platform, scheduled date/time, and status.",
        inputSchema: {
          content: z.string().describe("The post content to schedule"),
          platform: z.enum(["linkedin", "instagram", "x", "tiktok"]).describe("Target platform"),
          scheduled_date: z.string().describe("Scheduled date (YYYY-MM-DD)"),
          scheduled_time: z.string().default("09:00").describe("Scheduled time (HH:MM, default 09:00)"),
        },
        annotations: { readOnlyHint: false, openWorldHint: false, destructiveHint: false },
      },
Behavior3/5

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

Annotations already indicate this is a non-destructive write operation (readOnlyHint=false, destructiveHint=false). The description adds value by specifying the storage location (content-queue.json) and revealing that a 'status' field is tracked (not visible in inputs), but omits timezone handling, idempotency, or validation behavior.

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?

Two sentences, front-loaded with the core action. The second sentence earns its place by introducing the 'status' tracking concept, though it partially overlaps with the schema. Efficient but could be slightly more precise ('post' vs 'content' parameter).

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

Completeness3/5

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

Adequate for a 4-parameter tool with complete schema annotations. However, given this is a scheduling tool with no output schema, the description should clarify what indicates success (return value) and timezone handling for the scheduled_time parameter. Gaps remain for operational completeness.

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?

With 100% schema description coverage, the baseline is 3. The description lists some parameters ('platform, scheduled date/time') but doesn't add semantic nuance beyond the schema (e.g., timezone assumptions, content length limits). Mentioning 'status' doesn't help interpret inputs since it's not an input parameter.

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 clearly states the action (save) and target (publishing queue/content-queue.json), and implies the workflow stage by mentioning the queue. However, it doesn't explicitly differentiate from 'draft_post' (a sibling tool), which could cause confusion about when to draft versus schedule.

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 guidance provided on when to select this tool over alternatives like 'draft_post' or 'repurpose_content'. The description assumes the agent knows the content marketing workflow without indicating prerequisites (e.g., 'use this after content is finalized').

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/gomessoaresemmanuel-cpu/content-distribution-mcp'

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