Skip to main content
Glama

Archive a draft

archive_content

[writes flayr data · write scope] Soft-archives an uncommitted draft or failed generation. Keeps its content and media; Restore is available in the Library Archive view. Repeating the call is safe. Refused (409) for ready, staged, scheduled or published content, or any posting queue, post or approval history. Needs write scope and the same owner/admin authority as Library archive. A brand-bound connection only reaches its own brand. (Wraps POST /api/v2/content/{id}/archive.)

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": "archive_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFormat: string; e.g. "id_123". Content id from GET /api/v2/content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Content id from GET /api/v2/content."New value: +"Format: string; e.g. \"id_123\". Content id from GET /api/v2/content."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Substantial value beyond the annotations: it discloses that content and media are retained, that restoration is possible, the exact 409 refusal conditions, the write-scope and owner/admin authority requirement, and brand-bound connection scoping. One tension: "Repeating the call is safe" sits awkwardly against idempotentHint=false, so an agent could misread repeated calls as no-ops; that ambiguity costs a point but is not a direct contradiction.

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?

Front-loaded with the operation and eligibility, then grouped into effects, idempotency, refusals, and auth — a logical order with no filler sentences. The bracketed scope tag and the raw endpoint wrapper are slightly noisy but genuinely informative for an API-shaped tool.

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 one-parameter mutation with no output schema, the description covers everything an agent needs: reversibility, retained data, failure conditions, required scope, and cross-brand reach. Nothing material about calling it correctly is 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?

Schema coverage is 100% and the single `id` parameter is fully documented in the schema, so the baseline applies. The description adds only that the id refers to a draft/failed-generation content item, which is marginal meaning beyond the schema's "Content id from GET /api/v2/content".

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?

"Soft-archives an uncommitted draft or failed generation" gives a specific verb, resource, and eligible-state scope, immediately separating it from hard deletes or publishing actions. The contrast with restore ("Restore is available in the Library Archive view") further pins down what the operation actually does.

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 refusal list (409 for ready, staged, scheduled, published content, posting queues, posts, approval history) is an explicit when-not-to-use statement that an agent can check before calling. What is missing is a positive routing instruction — it never names the sibling to use instead (e.g. delete_content for permanent removal, or cancel_scheduled_post for queued items), leaving the agent to infer alternatives.

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