Skip to main content
Glama
deenesjakoruzh
trendsmcp-ai

youtube-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

youtube-trends-mcp

YouTube-Trends MCP Funktioniert mit Claude Funktioniert mit Cursor

YouTube-Trenddaten für KI-Assistenten Finden Sie heraus, wonach Menschen auf YouTube suchen. Aktuelle Themen, wachsende Video-Keywords und historische Suchnachfrage – alles per KI in natürlicher Sprache abfragbar.

Vollständige Dokumentation und Live-Demo: https://trendsmcp.ai/youtube-trends

Teil von Trends MCP – dem MCP-Server für Live-Trenddaten aus über 12 Quellen. Siehe das Haupt-Repository: https://github.com/trendsmcp/trends-mcp

In 2 Schritten loslegen

Schritt 1: Holen Sie sich Ihren kostenlosen API-Key auf trendsmcp.ai 100 Anfragen/Tag, keine Kreditkarte erforderlich.

Schritt 2: Fügen Sie ihn zu Ihrem KI-Client hinzu (ersetzen Sie YOUR_API_KEY):

+ Zu Cursor hinzufügen (ein Klick)

Cursor / Windsurf / Cline   (~/.cursor/mcp.json oder entsprechend)

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

VS Code / GitHub Copilot   (.vscode/mcp.json)

{
  "servers": {
    "trends-mcp": {
      "type": "http",
      "url": "https://api.trendsmcp.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Claude Desktop   (claude_desktop_config.json) Benutzer → Einstellungen → Entwickler → Konfiguration bearbeiten – in mcpServers einfügen

{
  "mcpServers": {
    "trends-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.trendsmcp.ai/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude.ai (Browser)   Einstellungen -> Connectors -> Benutzerdefinierten Connector hinzufügen:

https://api.trendsmcp.ai/mcp

Related MCP server: Google Trends MCP Server

Beispielabfrage

Nach dem Verbinden fragen Sie Ihre KI:

get_trends(keyword='morning routine', source='youtube', data_mode='weekly')

Verfügbare Tools

Tool

Was es macht

get_trends

Zeitreihe für ein Keyword in dieser Quelle

get_growth

Wachstums-% über 1W, 1M, 3M, 6M, 1Y-Zeiträume

get_top_trends

Was gerade in dieser Quelle angesagt ist

get_ranked_trends

Top-Themen nach Volumen geordnet

FAQ

Welche YouTube-Daten liefert Trends MCP?

YouTube-Videosuchvolumen-Trends – normalisiertes Interesse im Zeitverlauf, Wachstumskennzahlen und historische Reihen. Dies spiegelt die Nachfrage nach Videoinhalten zu bestimmten Themen wider, nicht die Aufrufzahlen einzelner Videos.

Wie unterscheiden sich YouTube-Suchdaten von Google-Suchdaten?

YouTube zeigt videospezifische Absichten an. Ein Keyword wie 'Handstand lernen' kann auf YouTube eine hohe Nachfrage haben, aber auf Google ein geringeres Suchvolumen. Der Vergleich beider offenbart Präferenzen für das Inhaltsformat.

Kann ich das nutzen, um trendige YouTube-Inhaltsideen zu finden?

Ja. Fragen Sie eine Reihe von Themen-Keywords ab, sortieren Sie nach Wachstumsrate der letzten 30 Tage, und Ihre KI zeigt, welche Videothemen derzeit an Suchmomentum gewinnen.

Deckt es auch die YouTube-Short-Suche ab?

Das Signal umfasst das gesamte YouTube-Suchvolumen einschließlich der Shorts-Entdeckung. YouTube trennt die Shorts-Suchdaten nicht, daher spiegeln die Ergebnisse das gesamte Suchinteresse auf der Plattform wider.

Alle Datenquellen

Trends MCP deckt über 12 Quellen in einer Verbindung ab: Google Search, YouTube, TikTok, Reddit, Amazon, Wikipedia, News Sentiment, Web Traffic, App Downloads, Steam, npm und mehr.

Alle durchsuchen: https://trendsmcp.ai/data-sources

Funktioniert auch als Python-Client

Derselbe API-Key funktioniert direkt in Python – kein MCP-Host erforderlich.

pip install youtube-trends-mcp
import os
from youtube_trends_mcp import TrendsMcpClient, SOURCE

client = TrendsMcpClient(api_key=os.environ["TRENDSMCP_API_KEY"])

series  = client.get_trends(source=SOURCE, keyword="your keyword")
growth  = client.get_growth(source=SOURCE, keyword="your keyword", percent_growth=["1M", "3M", "12M"])
top     = client.get_top_trends(type="Youtube", limit=10)

Vollständige Python-Dokumentation: trendsmcp.ai/docs

Lizenz

MIT © Trends MCP

Available Tools

3 tools
get_growthA
Read-onlyIdempotent
Inspect

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Prefer this over get_time_series for growth questions. app downloads and app rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesOne source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID.
percent_growthNoGrowth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y', '60M', '5Y', 'MTD', 'QTD', 'YTD'. Every preset is a two-date comparison.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description adds useful behavioral context: values are on a 0-100 scale with absolute volume when available, and the agent should tell the user their plan limit is reached on rate limiting or quota exhaustion. These details are not present in the structured fields and do not contradict the annotations.

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 compact and every sentence earns its place: core operation, output scale, sibling preference, app-source caveat, and rate-limit handling. It front-loads the primary purpose and avoids redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a detailed input schema, an output schema, and safety annotations, the description fills the remaining gaps: tool selection, output scale, source disambiguation, and error behavior. It is complete enough for an agent to invoke the tool correctly without further inference.

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?

The input schema already documents all parameters thoroughly, including valid sources, keyword formatting rules per source, and every preset growth window. The description references preset windows and Android bundle IDs but does not add meaning beyond the schema, so a baseline of 3 is appropriate.

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 opens with a specific action and resource: 'Point-to-point growth for a keyword on one or more sources.' It also names sibling tools to disambiguate itself, stating it is preferred over get_time_series for growth questions and clarifying that app sources are not the live boards on get_top_trends.

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

Usage Guidelines5/5

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

It gives an explicit selection rule: 'Prefer this over get_time_series for growth questions.' It also warns against confusing app downloads/app rankings with get_top_trends live boards, and specifies how to handle rate limits or quota exhaustion. This gives the agent clear when-to-use and when-not-to-use guidance.

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

get_time_seriesA
Read-onlyIdempotent
Inspect

Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesExactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'tesla'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint. The description adds behavioral context beyond those hints: the 0-100 value range, volume availability, and rate-limit/quota handling instructions. This provides useful operational detail that annotations do not convey, though the core safety profile is already covered by hints.

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?

Three sentences, each earning its place: purpose and scope, usage routing, and error handling. Front-loaded with the core purpose; no repetition or fluff. The alternative tool routing is included efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a two-parameter tool with a full output schema, the description covers purpose, usage scenarios, alternatives, and error handling. An agent has all necessary information to decide when to call it and what to expect, with no critical gaps.

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% and both parameters have detailed, source-specific descriptions (e.g., keyword format per source, valid source list). The tool description adds no additional parameter meaning beyond restating 'one keyword and one source', so the baseline for full schema coverage applies.

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 explicitly states it returns 'Full historical series for one keyword and one source' with a value range and volume detail. It distinguishes itself from siblings get_top_trends and get_growth by stating what it is not for (live trending, growth questions), making the tool's purpose unambiguous.

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

Usage Guidelines5/5

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

Directly states when to use it: 'Use for charting or custom math' and when not to: 'Not for live trending (use get_top_trends)' and 'For most growth questions, use get_growth'. Also provides explicit handling for rate-limited or quota-exhausted requests, which is actionable guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv0.1.0
    • First observedget_growth
    • First observedget_time_series
    • First observedget_top_trends
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation4/5

get_growth and get_time_series both handle keyword-based queries and could be confused, but their descriptions clearly distinguish growth snapshots from full historical series. get_top_trends is clearly separate as a live, keyword-free board.

Naming Consistency5/5

All tool names follow the same get_ pattern with clear object suffixes: get_growth, get_time_series, get_top_trends. The naming is consistent and predictable.

Tool Count5/5

Three tools is a compact but well-scoped set covering the three core modes: growth comparison, historical series, and live top trends. Each tool earns its place without redundancy.

Completeness4/5

The set covers the primary trend-data workflows: growth lookups, full time series, and live rankings. Minor gaps exist around discovering available feeds, periods, or sources, but descriptions embed enough detail for agents to proceed.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers