Skip to main content
Glama

Resume publishing to an account

clipember_resume_account
Idempotent

Resume a paused account. Queued posts go out at their scheduled times. Posts whose time came while the account was paused are NOT published late: they become failed (reason account_paused) so you can reschedule them. The result says how many. Workspace owner or admin only.

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": {
      "connectionId": "<connectionId>"
    },
    "name": "clipember_resume_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesAccount id from clipember_list_platform_connections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the real side effects: queued posts resume on schedule, posts that came due while paused are not published late but flipped to failed with reason account_paused, and rescheduling is the required follow-up. That is precisely the non-obvious behavior an agent could not infer from the schema or hints.

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?

Four short sentences, front-loaded with the action and immediately followed by the consequence that matters most (missed posts become failed, not published). Dense with no filler, though the final permission sentence would read slightly better placed before the consequence.

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

Completeness5/5

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

No output schema exists, and the description covers the return value ("The result says how many"), the permissions required, and the state transition semantics of the posts involved. Nothing an agent needs in order to call and interpret this tool is missing.

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 coverage is 100% and the single parameter already carries a description pointing at clipember_list_platform_connections for the id. The description adds no format or sourcing detail beyond that, so the baseline 3 applies.

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?

"Resume a paused account" is a specific verb plus resource, and the following sentences define exactly what resuming does. It is unambiguously the inverse of clipember_pause_account and cannot be confused with any get/update sibling.

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 condition for use (an account that is paused) is explicit, and the description adds the gating prerequisite "Workspace owner or admin only", which an agent needs before attempting the call. It does not explicitly name the pause counterpart or state when not to call it, keeping it short of a full routing statement.

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