Skip to main content
Glama

Schedule a draft

schedule_post_from_draft

Put an approved asset in the publish queue for a given account and time. Creates a queue item a human can still cancel.

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": {
      "content_item_id": "<content_item_id>",
      "social_account_id": "<social_account_id>"
    },
    "name": "schedule_post_from_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduled_forNoISO-8601 timestamp; omit to publish on the next pass
content_item_idYes
social_account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation creates a queue item and that a human can still cancel it, distinguishing enqueueing from immediate or irreversible publication. It does not explain approval failures, duplicate scheduling, or other error behavior.

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?

Two short sentences front-load the operation and then add the important queue-item and cancellation properties. There is no filler or unnecessary repetition of schema details.

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 flat three-parameter enqueue operation, the description and schema collectively cover the prerequisite, target, timing behavior, and cancelability. With no output schema, the absence of result information and unspecified duplicate or approval-failure behavior leave minor completeness gaps.

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 only 33% schema description coverage, the description partially compensates by associating the required identifiers with an approved asset and a target account. However, it does not explicitly map 'asset' to content_item_id, clarify that the input represents a draft/content item, or explain where either ID is obtained.

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 gives a concrete action and resource: putting an approved asset into the publish queue for a specified account and time. Clarifying that it creates a queue item is helpful, but the description does not explicitly differentiate the operation from sibling draft-creation or schedule-management tools.

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?

The word 'approved' supplies a meaningful prerequisite, while the account and time wording establishes the scheduling context. It lacks explicit when-not guidance or alternatives for cases such as unapproved content or an item that is already queued.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources