Skip to main content
Glama

Archive a project

archive_project
DestructiveIdempotent

Archive a project: it stops running, no longer counts toward the plan's projects, and is deleted for good after 30 days unless someone restores it in the MeshArc app. Use it when the person wants a project gone and delete_project is refused with admin_only -- a connected app never has admin -- or to free a slot after create_project is refused with plan_limit. Nothing is lost on the day it is archived. Inputs: project_id from list_projects. confirm_name must repeat the project's name exactly as get_project shows it, or nothing is archived. Effect: it answers with the project, archived true and purgeAt the day it goes. Archiving twice keeps the first date. Needs write access; a read-only connection is refused with code 'read_only'.

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": {
      "project_id": "<project_id>",
      "confirm_name": "<confirm_name>"
    },
    "name": "archive_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesThe project's 32-character hex id, from list_projects.
confirm_nameYesThe project's name, exactly as get_project shows it.

Output Schema

NameRequiredDescriptionDefault
idNoThe project's 32-character hex id.
codeNoOnly on a failure: a machine-readable reason, e.g. read_only, validation, plan_limit or not_found.
hostNoThe site it covers; fixed at creation.
nameNoIts display name.
noteNoNo project_id only: how path globs work.
seedNoWhere its crawls start.
errorNoOnly when the call failed: what went wrong, in words an assistant can act on.
pagesNoPages its last finished run read, a number.
configNoIts settings as {key: value}; secrets such as chat_url come back masked. create_project and update_project list only the settings that differ from the defaults; get_project lists them all.
detailNoOnly on a failure: the API's own wording, when the error was rephrased.
statusNodraft, crawling, healthy or failing. On an error, the HTTP status code.
purgeAtNoWhen an archived project is deleted for good (ISO 8601), or null.
archivedNotrue for an archived project: it runs no more and is deleted on purgeAt unless restored.
coverageNoPercent of the site the last run reached; under 90 means removals are withheld.
settingsNoNo project_id only: every common setting as {key, meaning, default}.
webhooksNoget_project only: {url, events, deliveries}: where run and change events are POSTed, which events, and the last 10 deliveries, each {id, event, status (queued, retrying, delivered or failed), attempts, lastStatus, lastError, createdAt, deliveredAt}. The signing secret is never included.
lastRunAtNoWhen the last run started (ISO 8601), or null.
nextRunAtNoWhen the schedule runs it next, or null for manual.
retentionNoHow long runs are kept, e.g. '90d'.
schedulesNoNo project_id only: the valid schedules.
archivedAtNoWhen it was archived (ISO 8601), or null.
configNoteNocreate_project and update_project only: says that config lists only the non-default settings.
other_keysNoNo project_id only: further keys accepted but rarely needed.
scheduleKeyNomanual, hourly, daily or weekly.
webhookTestNoupdate_project with test_webhook only: {queued, id} when a test run.finished message was queued, or {error, status} when the API refused it, e.g. with no webhook URL saved.
changeSummaryNoThe last compared run in words, e.g. '3 new · 2 changed · 0 removed'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (destructiveHint=true, idempotentHint=true), and the description adds real context on top: a 30-day purge window, that nothing is lost on archive day, that write access is required and a read-only connection fails with 'read_only', and that re-archiving preserves the first purge date. It does not restate annotation fields, but the return-shape detail overlaps with the output schema rather than adding new behavior.

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 effect, then usage routing, then labeled Inputs and Effect blocks, which makes it scannable despite being dense. Minor waste: the confirm_name sentence largely repeats the schema's own description, and the return-shape sentence duplicates what the output schema already provides.

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?

Covers everything an agent needs for a destructive, idempotent tool: trigger conditions, validation failure mode, auth requirement with the specific error code, reversibility window, and expected response. With an output schema present, the extra return detail is a bonus rather than a gap-filler.

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 coverage is already 100%, so the bar is a baseline 3; the description earns above that by stating the consequence of a bad confirm_name ('or nothing is archived'), which is exact-match validation behavior the schema does not convey beyond saying 'exactly as get_project shows it'.

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 its semantics: 'it stops running, no longer counts toward the plan's projects, and is deleted for good after 30 days.' It also distinguishes itself from delete_project by naming the exact refusal condition (admin_only) that routes an agent here 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?

Gives explicit selection rules: use it when the user wants a project gone but delete_project returns admin_only, or to free a slot after create_project returns plan_limit. It also names the escape hatch (restore within 30 days) so the agent can set expectations rather than treat it as an immediate hard delete.

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.