VidLens

Overview Schema Source Related Servers Discussions Admin

importComments

Import YouTube video comments into a local knowledge base to enable semantic search and analysis of viewer discussions.

Instructions

Import a video's comments into the local comment knowledge base for semantic search. Fetches comments via the existing comment pipeline and indexes them for searchComments. [~3-10s]

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": {
      "videoIdOrUrl": "<videoIdOrUrl>"
    },
    "name": "importComments"
  }
}

Input Schema

Name	Required	Description
`videoIdOrUrl`	Yes	YouTube video URL or ID
`collectionId`	No	Custom collection ID (default: comments-{videoId})
`maxTopLevel`	No	Max top-level comments to fetch
`includeReplies`	No	Include reply threads (default: true)
`maxRepliesPerThread`	No
`order`	No
`label`	No	Human-readable collection label
`activateCollection`	No	Set as active comment collection (default: true)
`dryRun`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.8Apr 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Provides valuable timing estimate '[~3-10s]', mentions side effects ('into the local comment knowledge base', 'indexes them'), and external dependency ('existing comment pipeline'). Missing idempotency details and error handling behavior.

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?

Two dense sentences plus timing metadata. Every element serves a purpose: first defines action/scope, second explains mechanism/relationship, bracket provides UX-critical latency expectations. Zero redundancy.

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 9-parameter indexing tool with complex lifecycle (collections, activation, dry-run), the description covers core import mechanics but omits explanation of collection management workflow, dryRun behavior, and return value structure (no output schema present to compensate).

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 67% (>50%), establishing baseline 3. Description adds no explicit parameter guidance to compensate for undocumented fields like 'dryRun' and 'maxRepliesPerThread'. Mentions 'video' implicitly mapping to videoIdOrUrl, but adds no syntax or format details beyond schema.

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?

Specific verb 'Import' with clear resource 'video's comments' and destination 'local comment knowledge base'. Explicitly mentions downstream purpose 'for semantic search' and target sibling 'searchComments', effectively distinguishing it from readComments.

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

Usage Guidelines4/5

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

Implies usage context by referencing 'searchComments' as the consumer of the indexed data, suggesting when to use this (when search is needed later). However, lacks explicit 'when not to use' guidance or direct comparison to readComments for immediate viewing without persistence.

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