Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_search

Read-only

Search a Tube Archivist archive by full text across videos, channels, and playlists to locate specific content. Read-only queries return matching archive items without modifying data.

Instructions

Full-text search across videos, channels, and playlists. Reads only. Actions: search (GET /api/search/).

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

Input Schema

NameRequiredDescriptionDefault
queryNoquery
actionYesTube Archivist operation to call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so 'Reads only' largely restates them. The added value is modest: the underlying endpoint (GET /api/search/) confirms a non-mutating call, but nothing is said about result limits, pagination, or how matches are ranked.

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 short sentences, front-loaded with the scope statement, with no filler. The trailing 'Actions: search (GET /api/search/)' fragment is slightly mechanical boilerplate for a tool with exactly one action, but it costs little.

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 two-parameter, single-action search tool with full schema coverage and no output schema, the description supplies what is needed to call it correctly. Return-shape and result-size expectations are the only meaningful omissions, and those are minor here.

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 both parameters are already documented in structured form. The description adds no meaning beyond the schema for 'query' (no syntax, matching rules, or length guidance) and does not explain the single-valued action enum.

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 states a specific verb and scope: 'Full-text search across videos, channels, and playlists.' That distinguishes it from the item-oriented siblings such as ta_video and ta_channel, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the text-search entry point, but there is no statement of when to prefer it over ta_video/ta_channel/ta_playlist lookups or any exclusion. The single action 'search' is listed but not framed as guidance.

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