Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_user

Destructive

Retrieve Tube Archivist account details and per-user view preferences, or update them with explicit confirmation; unconfirmed writes are dry-run previews.

Instructions

The account behind the token and per-user view preferences. 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: account (GET /api/user/account/), me (GET /api/user/me/), update (POST /api/user/me/).

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

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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, so the safety profile is known; the description adds genuinely new behavior by explaining the dry-run gate and that no HTTP write is sent unless both conditions hold. It does not say what an 'update' overwrites or whether omitted fields are cleared, which is the main remaining gap for a destructive tool.

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?

Three tight sentences, front-loaded with what the tool is, then the write gate, then the action list. The opening fragment ('The account behind the token and per-user view preferences') is slightly clipped but no sentence is wasted.

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 3-parameter, no-output-schema tool the action and confirm story is adequately covered. The gap is the nested 'document' payload for update, which is undocumented in both schema and description, leaving the agent unable to know what fields to send.

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 schema itself already spells out the confirm semantics in detail, so the description largely duplicates it. It does add value by mapping each enum action to an HTTP method/path, but it says nothing about the 'document' object, whose schema description is only the tautology 'document'.

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?

The description names a concrete resource (the account behind the token plus per-user view preferences) and enumerates the three selectable actions with their HTTP endpoints. It is clear enough to separate 'account'/'me' reads from an 'update' write, though it never distinguishes itself from sibling admin tools such as ta_config or ta_system.

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?

Strong guidance on the write-vs-dry-run condition (confirm true plus TUBEARCHIVIST_ALLOW_WRITES), which tells the agent exactly when a mutation will actually occur. However, there is no guidance on when to pick this tool over siblings, nor any statement about which action to prefer for a given intent beyond the endpoint list.

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