Skip to main content
Glama

Archive article

archive-article
Destructive

Archive an article: its status becomes archived and its slug becomes archived-, freeing the old slug. The content is kept, and list-articles still returns it unless filtered by status. No tool here unarchives it. Confirm with the user first.

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": {
      "article_id": "<article_id>"
    },
    "name": "archive-article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesArticle ID from list-articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / article_id / description
      Previous value: -"Article ID"New value: +"Article ID from list-articles"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description goes much further: it enumerates the slug rename and the release of the old slug, confirms the content is retained, explains that list-articles still surfaces the item unless status is filtered, and warns that the action is not reversible within this toolset. That is exactly the extra context an agent needs before a destructive mutation.

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 sentences, each carrying distinct information, with the primary effect front-loaded and the confirmation warning placed last so it is read just before invocation. There is no filler.

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?

A destructive, non-open-world mutation with no output schema; the description covers the state changes, the retained content, the visibility side effect on list-articles, irreversibility, and the need for user confirmation. Nothing material is left for the agent to guess.

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 article_id parameter is fully documented in the schema, including the uuid pattern and the hint to get it from list-articles. The description adds no further parameter guidance, so the baseline of 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?

States a specific verb and resource plus the exact resulting state: status becomes archived and slug becomes archived-<id>. That detail distinguishes it from create-article, update-article and publish-article without needing to name them, and it is unambiguous about what 'archive' means here.

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 caution ('Confirm with the user first') and rules out an expectation of reversal ('No tool here unarchives it'), which is strong when/when-not guidance. It stops short of naming alternatives, e.g. that update-article should be used for content changes while this is for retirement, but the context is otherwise clear.

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