Skip to main content
Glama

evaluate_idea

Read-only

Judge whether a specific YouTube video idea, topic, or title the user is weighing up is worth making, grounded BOTH in what already converts on their own YouTube channel and in how that topic actually performs for other channels YouTube places next to theirs: roughly what a decent video on it gets, what the best get, and whether the demand is still current. Call this whenever the user proposes an idea and asks whether it (or a title) is worth making, will work, or is a good idea, and also when they ask what a topic or subject normally gets, how big a topic is, whether a topic is worth their time, or how their channel compares to others covering it. For deeper packaging help (several title options, thumbnail text, or reviewing/scoring a title or thumbnail), use package_video instead.

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

Input Schema

NameRequiredDescriptionDefault
ideaNoThe video idea, topic, or title to evaluate
titleNo
topicNo

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description goes beyond that by disclosing what the judgment is grounded in (own-channel conversion data plus how the topic performs for neighboring channels) and roughly what the answer contains — typical performance, best-case performance, and whether demand is current. It does not discuss data staleness or what happens when no comparable channels exist, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded in the first sentence, but the trigger sentence is padded with near-synonymous phrasings ("is worth making, will work, or is a good idea" and a long chain of topic-size questions). The useful content is all there, yet it reads as an undifferentiated block rather than a structured guide.

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 no output schema, the description compensates by describing the shape of the answer in prose, and annotations cover the read-only/open-world profile. It is nearly complete for a three-parameter analysis tool, missing only edge-case behavior such as insufficient comparison data or whether the idea must relate to the user's own channel.

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 only 33%: only `idea` carries a description, while `title` and `topic` are bare strings. The prose mentions idea/topic/title as the things being judged, which hints they are alternative representations of the same input, but it never says whether to pass one or all three, or what happens if two conflict. That is the key ambiguity an agent would hit, and it is left unresolved.

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 concrete verb-and-resource pair ("Judge whether a specific YouTube video idea, topic, or title ... is worth making") and immediately states the evidence basis (the user's own channel plus neighboring channels' performance). It is clearly distinguishable from package_video, which the description explicitly routes packaging work to.

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?

The when-to-use conditions are enumerated concretely: the user proposes an idea and asks if it is worth making, or asks what a topic normally gets, how big it is, or how their channel compares. The final sentence names the alternative (package_video) and the exact condition that selects it (multiple title options, thumbnail text, title/thumbnail scoring).

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