Skip to main content
Glama

find_trending_keywords

Detect emerging keywords in any niche by analyzing recent video performance, views, and channel size, with classification as emerging, growing, or stable trends.

Instructions

Detecta keywords emergentes no nicho analisando padrões de vídeos recentes, views e tamanho dos canais. Classifica cada keyword como Emergente, Crescendo ou Estável.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nicheYesNicho a pesquisar
regionCodeNoRegião: BR, US, PT, ES, ARBR
maxKeywordsNoQuantidade máxima de keywords (5-15)
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral inputs (recent videos, views, channel size) and the output classification categories. It does not detail the return structure or edge cases, but for a read-only analysis tool it offers a reasonable level of transparency.

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 a single, efficient sentence with the action verb front-loaded. It conveys purpose, method, and output without unnecessary words.

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?

Despite having no output schema, the description implies the return value includes keywords with their classifications. With 3 documented parameters and clear analytical inputs, the description is complete enough for an agent to understand the tool's function, though it could be slightly richer on return format details.

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 100% as every parameter has a description. The tool description adds no specific parameter details beyond the schema, but the baseline is 3 when schema coverage is high, and the description does not conflict with or detract from the 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?

The description uses a specific verb 'Detecta' (detects) with a specific resource 'keywords emergentes no nicho' and explains the method (analyzing recent video patterns, views, channel size). It also mentions classification into Emergente, Crescendo, or Estável, which clearly differentiates it from sibling tools like get_keyword_stats or search_trending_topics.

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 description implies the tool is for finding emerging keywords but provides no explicit guidance on when to use it versus alternatives such as search_trending_topics or get_keyword_stats. There is no mention of exclusions or specific scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dewtech-technologies/tubemind-secure-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server