Find the next N best video topic opportunities for your channel. Scores each topic against your locked niche keywords and brand voice. Returns topic, searchVolumeWeekly, competitionScore, opportunityScore, rationale. Quota: 25/mo Free, 500/mo Pro, 2000/mo Studio.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | How many opportunities (1–10) | |
| locale | No | BCP-47 locale, e.g. 'en', 'tr', 'es' |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description discloses scoring against niche keywords and brand voice, and lists returned fields. It includes quota limits but does not explain how keywords are set or any prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each adding value: purpose, scoring method, return fields, and quota. Front-loaded with actionable info, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Describes return fields and scoring criteria adequately for a tool with 2 params and no output schema. However, lacks context about prerequisite 'locked niche keywords,' which may affect completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters described. The description adds context (e.g., 'N' in 'Find the next N best') but does not significantly expand beyond schema defaults.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Find the next N best video topic opportunities for your channel' with specific verb and resource. It distinguishes itself from siblings like youtube_generate_video by focusing on opportunity discovery.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when seeking video topics but does not explicitly state when to use versus alternatives or provide exclusions. The quota mention provides some context but no direct guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.