Skip to main content
Glama

Resume paused post

resume_post

Resume a paused post. Without arguments it keeps the original time; if that time has passed core-api answers 409 SCHEDULED_AT_IN_PAST with a suggested slot, so ask the user for a new time (scheduledAt), or use mode "next_slot". mode "now" publishes immediately and is rejected with 403 unless the key has the POSTS_AUTO_APPROVE scope. 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": "resume_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe paused post id.
modeNo"now" publishes immediately and needs the POSTS_AUTO_APPROVE scope (otherwise 403); use only when the user explicitly asked for it. "next_slot" uses the next free queue slot. Cannot be combined with scheduledAt.
scheduledAtNoNew publish time, ISO 8601 with zone. Required when the original time has passed. Must be at least 10 minutes from now, otherwise SCHEDULED_TOO_SOON (not retryable; the error names the earliest allowed time).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so unusually well: it discloses the default no-arg behavior, the exact 409 SCHEDULED_AT_IN_PAST error and its suggested slot, the 403 caused by missing POSTS_AUTO_APPROVE, and the baseline write-scope requirement. These are error-level and permission-level facts an agent cannot obtain from structured fields and that directly change the next action.

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 compact sentences that front-load the happy path before the error branches, with no filler. Minor redundancy: the POSTS_AUTO_APPROVE scope requirement and the 403 outcome appear in both the description and the schema.

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 three-parameter mutation with no output schema and no annotations, the description covers default behavior, failure modes, and permission prerequisites thoroughly. What remains unstated is the success response shape and whether resuming an already-published or deleted post behaves differently, both of which an agent might need.

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 schema already documents the mode enum, the 403 scope condition, the incompatibility with scheduledAt, and the 10-minute minimum with SCHEDULED_TOO_SOON. The description re-states much of that rather than adding new meaning, so it sits at the baseline for a fully documented schema.

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?

States a specific verb and resource ("Resume a paused post") with the implicit counterpart pause_post made obvious by the word "paused." An agent can distinguish this from reschedule_post or update_post without opening a schema, since the object being acted on is precisely scoped.

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?

Gives a clear decision tree: call with no args to keep the original time, fall back on a 409 to ask the user for scheduledAt or use mode "next_slot", and reserve mode "now" for explicit requests because it needs POSTS_AUTO_APPROVE. The one gap is that it never contrasts itself with the reschedule_post sibling, so an agent holding a past-due paused post has no stated reason to prefer one over the other.

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