Skip to main content
Glama

import_youtube_music_history

Import Google Takeout YouTube watch history so Yit knows your music taste from day one; defaults to YouTube Music entries only.

Instructions

Imports the user's Google Takeout YouTube watch history (watch-history.json or .html) so Yit knows their taste from day one. By default only YouTube Music entries are imported.

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": {
      "file_path": "<file_path>"
    },
    "name": "import_youtube_music_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
include_regular_youtubeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a mutation-style import. It discloses that only YouTube Music entries are imported by default and that Google Takeout JSON/HTML files are supported, but it does not explain merge/duplicate behavior, overwrite semantics, permissions, file-size limits, or error handling.

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?

The description is two tight sentences with no wasted text. The primary action and default filtering behavior are front-loaded.

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?

An output schema exists, so return values need not be described. However, with no annotations and a mutation-style import operation, the description should probably mention prerequisites and how existing listening data is affected. It covers the core purpose, formats, and default filter but leaves meaningful behavioral gaps.

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 description coverage is 0%, so the description must compensate. It meaningfully clarifies the file_path parameter by naming accepted Google Takeout formats (watch-history.json or .html) and explains the effective behavior of include_regular_youtube by stating that only YouTube Music entries are imported by default.

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?

The description gives a specific verb and resource: importing Google Takeout YouTube watch history. It also states the product goal (seeding Yit's taste) and the default scope (YouTube Music entries only), so an agent can identify exactly what the tool does.

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 phrase 'so Yit knows their taste from day one' implies an onboarding/import use case, but it does not explicitly say when to use this tool, when not to use it, or what prerequisites are needed. No sibling tool covers the same import behavior, so the implied context is adequate but not strong.

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