Skip to main content
Glama

Carry out a posting schedule

schedule_clips_execute

Publish planned clips to connected YouTube and TikTok accounts at set times, finalizing the schedule. Posts go public and cannot be undone.

Instructions

Actually schedule the posts worked out by schedule_clips_plan. This posts publicly and cannot be undone.

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": {
      "clip_ids": "<clip_ids>"
    },
    "name": "schedule_clips_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_dayNo
clip_idsYes
hashtagsNo
start_atNo
gap_hoursNo
platformsNo
every_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does the most important work by disclosing that posts go out publicly and cannot be undone. However, it says nothing about permissions, rate limits, failure/partial-failure behavior, or what identifies the scheduled result, which leaves meaningful gaps for a 7-parameter mutation tool.

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 short sentences, front-loaded with the action and followed by the critical consequence; no wasted wording. Slightly terse given the complexity it must cover.

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?

For a 7-parameter, irreversible mutation tool with no annotations, no output schema, and undocumented parameters, the description is too thin: it never explains scheduling cadence, timing options, or what the caller gets back to track the job.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions no parameters at all. The ambiguous ones -- per_day, gap_hours vs every_hours, start_at, clip_ids -- receive no clarification, so an agent must guess their interaction entirely.

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 names a specific action ('actually schedule the posts') and explicitly ties it to the sibling planning tool schedule_clips_plan, making the plan/execute split obvious 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 Guidelines4/5

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

It clearly implies this should be called with the output of schedule_clips_plan, which gives solid when-to-use context, but it offers no exclusions or guidance about other execution-style siblings such as publish_plan_execute.

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