Skip to main content
Glama

suggest_ideas

Read-only

Generate specific video ideas for the signed-in user's own YouTube channel to make next, grounded in what already earns them subscribers there (their winners), what their audience keeps asking for (their comments), and what each suggested subject is actually worth: roughly what videos on it earn for channels YouTube places next to theirs, so the ideas can be ranked by real headroom rather than by hunch. Call this when the user asks what to make, film, or post next; for video ideas, content ideas, or topic suggestions; what their next video should be; to brainstorm ideas; or says they are out of ideas or stuck on what to make. This GENERATES ideas from scratch. To judge or package a specific idea the user already has in mind, use evaluate_idea instead. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

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": "suggest_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectsNoWhat this channel is actually about, comma separated, when the user names them (for example 'quantconnect, interactive brokers, trading'). Only pass what the USER said; never guess on their behalf. Klyf derives these from their search report otherwise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / properties / subjects
      Added value: +{
      +  "description": "What this channel is actually about, comma separated, when the user names them (for example 'quantconnect, interactive brokers, trading'). Only pass what the USER said; never guess on their behalf. Klyf derives these from their search report otherwise",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context beyond that — the tool reads the user's real connected channel, requires no clarification, and ranks ideas by actual earning headroom for neighboring channels. It stops short of describing the return payload's structure or idea count, which is a minor gap given there is no output schema.

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?

Purpose is front-loaded and the generate-vs-evaluate contrast is well placed. Some redundancy creeps in — parallel trigger lists ('video ideas, content ideas, or topic suggestions') and the emphatic 'not for context, not for a link, not for a title' could be tightened without losing meaning.

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?

For a zero-required-parameter generative tool with no output schema, the description covers input sourcing, expected grounding data, and the value/ranking axis of results. Only the shape of the returned ideas (count, fields) is left unstated, which is acceptable but not exhaustive.

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 single optional 'subjects' parameter is fully documented in the schema (100% coverage), so baseline is 3. The description adds useful framing that the tool needs no input and derives subjects from the search report otherwise, but it does not add syntax or formatting meaning beyond 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?

States a specific verb and product: 'Generate specific video ideas for the signed-in user's own YouTube channel', and names the grounding signals (winners, comments, headroom). It explicitly contrasts with the sibling evaluate_idea ('This GENERATES ideas from scratch'), so the agent can distinguish it without opening schemas.

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?

Provides explicit trigger phrasings ('what to make, film, or post next', 'out of ideas or stuck') plus a clear exclusion routing to evaluate_idea for judging a specific idea the user already has. Also gives a strong procedural rule: call immediately, never ask the creator anything first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources