Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_task

Destructive

Read Tube Archivist task results, start or stop tasks, and manage schedules; write actions run only with confirm=true and writes enabled, otherwise return a dry-run preview.

Instructions

Read task results, start or stop tasks, and manage schedules. Writes run only when confirm is true and TUBEARCHIVIST_ALLOW_WRITES=true. Otherwise the call is a dry-run and no HTTP write is sent. Actions: results (GET /api/task/by-name/), results_by_name (GET /api/task/by-name/{task_name}/), start (POST /api/task/by-name/{task_name}/), get (GET /api/task/by-id/{task_id}/), command (POST /api/task/by-id/{task_id}/), schedules (GET /api/task/schedule/), schedule_get (GET /api/task/schedule/{task_name}/), schedule_upsert (POST /api/task/schedule/{task_name}/), schedule_delete (DELETE /api/task/schedule/{task_name}/).

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": {
      "action": "<action>"
    },
    "name": "ta_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesTube Archivist operation to call.
confirmNoBoolean true runs the write when TUBEARCHIVIST_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
task_idNotask_id
documentNodocument
task_nameNotask_name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the description's added value is in disclosing the environment-variable write gate and the dry-run fallback — genuinely non-obvious behavioral context. It stops short of saying what schedule_delete removes or whether deleting a running task's schedule affects an in-flight run.

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?

Two terse sentences with the capability summary and the safety gate front-loaded, followed by a scannable action list. The endpoint-per-action enumeration partially duplicates the action enum already in the schema, which is the only wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-action, five-parameter mutation tool with no output schema, the definition covers the write safety story but omits per-action parameter requirements and the shape of `document`. An agent would not know from the description alone what to pass to schedule_upsert or what a results response looks like.

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 description coverage is 100%, so the schema already documents every parameter and even the confirm semantics. The action-to-endpoint mapping adds real meaning about which action targets a name versus an ID, but the description never explains the nested `document` object that `schedule_upsert` presumably requires. Baseline 3 given the schema carries most of the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb-plus-resource summary ("Read task results, start or stop tasks, and manage schedules") and enumerates all nine actions with their HTTP endpoints, which cleanly separates it from siblings like ta_system or ta_maintenance. Minor deduction because it advertises stopping tasks while the action enum contains only `start` and no stop action, so one claimed capability is unrealizable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The write gate (confirm=true plus TUBEARCHIVIST_ALLOW_WRITES=true, otherwise dry-run) is clearly stated and tells the agent how to invoke writes safely. However, there is no guidance on when to choose this tool over siblings, nor when to prefer `results` versus `results_by_name`, or `get` versus `results_by_name` — the agent must infer the selection rules from the endpoint paths.

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