Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get YouTube search terms (OAuth)

get_search_terms
Read-onlyIdempotent

Retrieve the search terms viewers typed before watching your videos, with views and watch time per term, to inform titles, descriptions and tags. Filter by date range or specific video.

Instructions

The YouTube search terms viewers typed before watching your videos, with views and watch time per term.

Useful for titles, descriptions and tags. Requires OAuth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWhen no dates are given: the last N days ending today.
limitNoHow many terms, 1-25 (the API's maximum).
end_dateNoEnd date YYYY-MM-DD, inclusive.
video_idNoOnly searches that led to this video. Omit for the whole channel.
start_dateNoStart date YYYY-MM-DD, inclusive. Omit both dates to use `days`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds context beyond that: an explicit OAuth requirement (relevant given the auth_status sibling) and a statement of what comes back (views and watch time per term). It stops short of noting quota cost or that results are capped at 25 terms.

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?

Two short sentences, front-loaded with the resource and its returned metrics before the usage and auth notes. Nothing is filler, though the second sentence is a loose grab-bag of use hint plus prerequisite rather than a structured note.

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?

With annotations, full schema descriptions, and an output schema, the remaining burden is light and largely met: what the tool returns, what it is good for, and that OAuth is required. The only meaningful gap is that the 25-term cap and 28-day default behavior live in the schema, not the description.

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% and each parameter (days, limit, start_date/end_date, video_id) is self-documented in the schema, so the baseline of 3 applies. The description adds no meaning about date precedence or the channel-wide default that the schema already explains.

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?

The description names a specific resource (the search terms viewers typed before watching) and the payload returned (views and watch time per term), which lets an agent distinguish this from analytics tools that report on traffic sources or revenue. It does not compare itself to any sibling by name, so it stops short of a 5.

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?

It gives a downstream-use hint ('Useful for titles, descriptions and tags') and an auth prerequisite, which implies investigative/metadata work, but offers no explicit when-to-use vs. when-not guidance or alternative tool for traffic-source questions. Usage is inferred rather than stated.

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