VidLens

Overview Schema Source Related Servers Discussions Admin

setActiveCollection

Set the default video collection for transcript searches to streamline queries without specifying collection IDs repeatedly.

Instructions

Set the default collection that transcript search should focus on when collectionId is omitted. [~instant]

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": {
      "collectionId": "<collectionId>"
    },
    "name": "setActiveCollection"
  }
}

Input Schema

Name	Required	Description	Default
`collectionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.8Apr 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Adds '[~instant]' timing hint and clarifies this affects transcript search specifically, but omits crucial state-mutation details like persistence duration, error behavior for invalid IDs, and relationship to clearActiveCollection given zero annotation coverage.

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?

Single front-loaded sentence with minimal verbosity; '[~instant]' is compact though slightly cryptic, and the sentence efficiently conveys both action and primary scope constraint.

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?

Adequate for a simple state-setting tool with one parameter and no output schema, but insufficient given the 0% schema coverage—missing parameter documentation and operational details like state persistence or conflict resolution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Fails to compensate for 0% schema description coverage; mentions 'collectionId' only in the context of search omission rather than documenting the required parameter's format, valid values, or source (e.g., from listCollections).

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?

Description uses specific verb 'Set' with clear resource 'default collection' and explicitly scopes the effect to 'transcript search', effectively distinguishing it from sibling tool setActiveCommentCollection.

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?

Implies usage context by mentioning 'when collectionId is omitted' in search operations, but lacks explicit guidance on when to use versus clearActiveCollection or prerequisites like obtaining valid IDs from listCollections.

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