Skip to main content
Glama

Pause scheduled post

pause_post

Pause a scheduled post: status becomes paused, scheduledAt is kept and nothing is published until resume_post. Only scheduled posts can be paused (publishing/published: 409 POST_NOT_PAUSABLE, not retryable). Requires a key with write scope.

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": {
      "id": "<id>"
    },
    "name": "pause_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe scheduled post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden and does well: it discloses the state transition (status becomes paused), that scheduledAt is preserved, that nothing publishes in the interim, the non-retryable 409 condition, and the write-scope auth requirement. The only missing piece is whether the pause is reversible or expires, though resume_post implies reversibility.

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?

Three compact clauses, each carrying new information: outcome, precondition/failure, and auth requirement. Nothing is repeated and the outcome is front-loaded.

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 single-parameter mutation tool with no annotations and no output schema, the description covers state effects, error semantics, and permissions. Only the response shape and whether an already-paused post is idempotent are left unstated.

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?

With one parameter at 100% schema coverage, the schema already documents id as 'The scheduled post id.' The description adds only the constraint that the id must reference a scheduled (not publishing/published) post, which is meaningful but marginal beyond the structured data.

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?

Opens with a specific verb+resource ('Pause a scheduled post') and immediately states the resulting status, so the agent knows exactly what the call does. The pairing with resume_post in the same sentence makes the counterpart operation unambiguous.

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?

Explicitly states the precondition ('Only scheduled posts can be paused') and the exact failure mode with status code and retryability ('publishing/published: 409 POST_NOT_PAUSABLE, not retryable'). It also names the operation that reverses it, giving the agent a clear routing signal among siblings.

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