Skip to main content
Glama

Pause publishing to an account

clipember_pause_account
Idempotent

Stop publishing to one connected account (like Buffer's Pause Queue) — for a brand crisis or a mistake in queued posts. Its queued posts wait instead of going out; new posts can still be scheduled to it. Nothing is deleted. Undo with clipember_resume_account. connectionId comes from clipember_list_platform_connections. 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_pause_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesAccount id from clipember_list_platform_connections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (non-destructive, idempotent, not read-only), the description discloses the actual side effects: queued posts wait rather than publish, new posts can still be scheduled, nothing is deleted, and the action is reversible via resume. It also states the authorization constraint (workspace owner or admin), which the annotations do not carry.

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?

Four short clauses, front-loaded with the action and its effect, then the reversal path, then the parameter source and permission gate. No filler sentences; every clause carries distinct information.

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?

For a single-parameter state-change tool, the definition covers effect, reversibility, permissions, and parameter origin, and there is no output schema demanding return-value explanation. An agent can invoke it correctly from this text alone.

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 connectionId parameter already documents that it comes from clipember_list_platform_connections, so the description's identical pointer adds no new meaning such as format, lookup syntax, or error behavior.

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 opens with a specific verb and resource, 'Stop publishing to one connected account,' and grounds it with a familiar analogy (Buffer's Pause Queue), which immediately separates it from sibling clipember_resume_account.

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

Usage Guidelines5/5

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

It explicitly names the triggering situations (brand crisis, mistake in queued posts), names the undo alternative clipember_resume_account, and tells the agent where connectionId comes from, so both when and how are covered without inference.

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