Skip to main content
Glama
Sign In
tubemind-secure-mcp

tubemind-secure-mcp

by dewtech-technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_competitor_videos

Fetch competitor channel videos with title, views, likes, duration, and publish date. Analyze content strategy by providing a channel ID.

Instructions

Lista os vídeos de um canal concorrente com título, views, likes, duração e data. Útil para analisar estratégia de conteúdo de competidores. Requer o Channel ID (começa com UC).

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": {
      "channelId": "<channelId>"
    },
    "name": "get_competitor_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoOrdenação: viewCount (mais vistos), date (mais recentes), rating (mais curtidos)viewCount
channelIdYesChannel ID do concorrente (começa com UC, 24 chars). Ex: UCVjlpEjEY9GpksqbEesJnNA
maxResultsNoNúmero de vídeos (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the required channel ID format and the fields returned, but it does not explicitly state that the operation is read-only or mention any side effects. The verb 'Lista' implies a safe read, but additional behavioral details are absent.

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 three concise sentences: the first states the action, the second provides the use case, and the third states a requirement. No unnecessary detail or repetition.

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?

Without an output schema, the description usefully lists the returned fields (title, views, likes, duration, date). It also gives a use case. It could mention ordering or result limits, but those are covered in the input schema, so the description is reasonably complete.

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 the baseline is 3. The description restates the channel ID requirement ('começa com UC'), which is already in the schema, without adding new parameter-specific semantics.

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 clearly states the tool 'lists videos of a competitor channel' with specific fields (title, views, likes, duration, date). The word 'concorrente' distinguishes it from sibling tools that likely target the user's own channel, such as list_channel_videos.

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?

The description says it's 'useful for analyzing competitor content strategy,' providing clear context for when to use it. However, it does not explicitly exclude alternatives or name sibling tools for comparison, so it lacks full when-not guidance.

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