Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Archive post

archive_post
DestructiveIdempotent

Retire an article from the queue, the calendar, the planner, the link graph and next_write. Nothing is deleted: the body and the paid brief stay in the database and get_post still reads it. Without confirm this returns a dry run (degraded reason confirm-required) describing what would be retired: status, whether it has a body and how many words, and which calendar day it occupies; confirm: true applies it. Archiving is idempotent (alreadyArchived: true). If the result carries danglingTopicLink, a topic still points at the retired article. Use unschedule_post to only free the calendar day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
confirmNo
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: nothing is deleted and body/brief remain readable via get_post, the confirm-gated dry run returns a specific degraded reason, archiving is idempotent (alreadyArchived), and danglingTopicLink signals a residual topic reference. This goes well past destructiveHint/idempotentHint.

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?

Purpose and non-destructive guarantee are front-loaded, and every sentence carries distinct information (scope, dry run, idempotency, dangling link, alternative). The dense compound sentences with semicolons are efficient but border on cramped.

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?

With no output schema, the description still documents the return shape (dry-run fields: status, body presence, word count, calendar day) and result flags (alreadyArchived, danglingTopicLink). Nothing needed to invoke or interpret the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (workspaceId only), so the description must compensate. It thoroughly explains the confirm parameter's two modes but never explicitly defines id. It adds real meaning for confirm while leaving id contextually inferred.

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 (retire/archive) and resource (article) plus the exact scope of removal: queue, calendar, planner, link graph, and next_write. It distinguishes itself from the sibling unschedule_post by naming what that tool does instead.

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 tells the agent when to use this tool versus the alternative: 'Use unschedule_post to only free the calendar day.' It also explains the dry-run-vs-apply condition (confirm required to actually retire).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All seodraft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources