Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_notify

Destructive

List, add, or remove webhook URLs on Tube Archivist scheduled tasks; write actions require confirm=true and writes enabled, otherwise previews as a dry-run.

Instructions

Read and edit webhook URLs stored on scheduled tasks. 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: list (GET /api/task/notification/), add (POST /api/task/notification/), remove (DELETE /api/task/notification/).

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_notify"
  }
}

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.
documentNodocument

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real value beyond the annotations by disclosing the two-part write gate: confirm=true AND TUBEARCHIVIST_ALLOW_WRITES=true, otherwise the call degrades to a dry-run with no HTTP write sent. That materially qualifies the destructiveHint=true annotation. It stops short of describing the response shape or what a dry-run returns, keeping it from a 5.

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, front-loaded with purpose, then the write-gating rule, then the action enumeration. No redundant phrasing and nothing buried at the end.

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

Completeness4/5

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

For a 3-parameter tool with full schema coverage and no output schema, the description covers purpose, safety gating, and action mapping well. The notable gap is that the free-form 'document' payload (required for add) is never explained, and no return-value expectations are set beyond 'no HTTP write is sent' on dry-runs.

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 100%, so baseline is 3, but the description adds meaning by mapping each action enum value to a specific HTTP method and endpoint, and reiterating the confirm semantics with the string-'true' rejection caveat. It does not clarify the opaque 'document' object's expected contents for the add action, which is the one remaining semantic gap.

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+resource combination ('Read and edit webhook URLs stored on scheduled tasks') and enumerates the three concrete operations with their HTTP endpoints. An agent can distinguish this from ta_task (task management) without opening any schema.

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 description implies usage through the action list (list/add/remove) and explains the confirm gate, but never states when to prefer this over ta_task or other siblings, nor any prerequisites such as needing a task ID. Guidance is inferable rather than explicit.

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