Skip to main content
Glama

Stop repeating a post

clipember_stop_repeat
DestructiveIdempotent

Stop a repeat. Posts it already created stay scheduled — cancel them separately if needed.

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": {
      "repeatId": "<repeatId>"
    },
    "name": "clipember_stop_repeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
repeatIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is mostly covered. The description adds a genuinely useful caveat about residual state — existing scheduled posts survive the stop — but says nothing about whether the repeat can be restarted, whether the stop is permanent, or what permissions are required for a destructive mutation.

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 with zero filler; the core action is front-loaded and the important caveat follows immediately. Nothing is redundant or padded.

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?

For a simple single-parameter mutation with annotations covering safety, the description is mostly sufficient, and the residual-scheduled-posts note is the key operational detail. It falls short on how to obtain the repeatId and on any confirmation of what the call returns or whether the stop is reversible.

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

Parameters2/5

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

There is one required parameter, repeatId, with 0% schema description coverage; the schema only constrains its UUID format. The description never mentions the parameter, so the agent gets no help on where to source a repeatId or what happens with an invalid/nonexistent one — a gap the schema does not fill.

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?

"Stop a repeat" names a specific verb and resource, and the second sentence clarifies the boundary of the operation (it halts future repetition but leaves already-created posts scheduled). It does not explicitly name siblings like clipember_repeat_post or clipember_cancel_scheduled_post, so the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase "cancel them separately if needed" implicitly routes the agent to a cancellation tool for the leftover scheduled posts, which is useful guidance. However, no sibling is named, there are no stated prerequisites (e.g., where to obtain the repeatId), and no explicit exclusions for when this tool should not be used.

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