Skip to main content
Glama
Sign In
VidLens

VidLens

by thatsrajan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recommendUploadWindows

Identify optimal YouTube upload windows by analyzing channel publishing history and timezone data to improve content scheduling strategy.

Instructions

Recommend upload windows from recent publishing history for a given timezone. [~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": {
      "channelIdOrHandleOrUrl": "<channelIdOrHandleOrUrl>",
      "timezone": "<timezone>"
    },
    "name": "recommendUploadWindows"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdOrHandleOrUrlYes
timezoneYesIANA timezone, e.g. Australia/Sydney
lookbackDaysNo
dryRunNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.8

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. The '[~3-10s]' timing disclosure adds valuable latency context not inferable from schema. However, fails to explain the presence of 'dryRun' parameter—leaving ambiguous whether this tool has side effects, creates persistent recommendations, or is purely read-only.

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?

Extremely concise two-part structure: functional description followed by latency annotation. Every element earns its place; no redundancy. Front-loaded with action and resource.

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?

Lacks output schema, yet description provides no hint about return format (time ranges? specific timestamps? scores?). With no annotations and mysterious 'dryRun' parameter, the description should clarify state changes or persistence. Core function is covered but operational context is incomplete.

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 low (25%), requiring description compensation. Mentions 'timezone' explicitly and 'recent publishing history' implicitly maps to lookbackDays, adding semantic context. However, fails to explain 'channelIdOrHandleOrUrl' format expectations or the behavioral implications of 'dryRun', leaving half the parameters undocumented.

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?

Clear specific verb ('recommend') + resource ('upload windows') + data source ('recent publishing history')._implicitly distinguishes from siblings like analyzePlaylist or inspectChannel by focusing narrowly on upload timing optimization, though lacks explicit contrast.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this versus other analysis tools (e.g., inspectChannel or analyzePlaylist). The '[~3-10s]' indicates performance latency but not functional prerequisites or when to avoid.

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

Deploy Server

Other Tools