Skip to main content
Glama

Repeat a post

clipember_repeat_post

Repeat a post (its whole group: every account it goes to) daily, weekly or monthly, at the same local time, until a date and/or for a number of posts in total. Each next post is created once the previous one is out, with every check of a new post (plan, how far ahead the plan schedules, the Free monthly limit, client approval). TikTok posts are repeated WITHOUT the person's audience choice — each one waits in the TikTok queue for them.

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": {
      "groupId": "<groupId>",
      "frequency": "<frequency>"
    },
    "name": "clipember_repeat_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many posts in total, the first included
untilNoNo posts after this time (ISO 8601)
groupIdYesgroupId of the post (from clipember_create_post or clipember_list_scheduled_posts)
timezoneNoIANA time zone to keep the local time in; default UTC
frequencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: each next post is created only after the previous one is out, and every new post goes through plan, scheduling-horizon, Free monthly limit, and client-approval checks. It also calls out the TikTok-specific behavior where posts are repeated without the person's audience choice and wait in the TikTok queue.

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 front-loaded with the core action and recurrence semantics, and the parenthetical list of checks is dense but relevant. It is somewhat long and run-on, but most sentences carry useful behavioral information.

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 complex recurring-post tool with no output schema, the description covers the main behavior, constraints, and TikTok exception well. It leaves some edge cases unstated, such as precedence when both until and count are provided and what happens on failure.

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 80%, so the schema already documents most parameters. The description adds some meaning, such as keeping the same local time and the relationship between until and count, but it does not explain the count minimum or clarify what happens when both until and count are supplied.

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 and resource: "Repeat a post" and clarifies that the whole group of accounts is included. It also specifies the recurrence options (daily, weekly, monthly), which distinguishes it from one-off creation 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?

It clearly establishes the recurring-post context and the stopping conditions (until a date and/or a total count). However, it does not explicitly say when not to use it or name the sibling stop_repeat tool as the alternative for ending a repeat.

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