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' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. It discloses quota limits and scoring against keywords/voice, but does not state if tool is read-only, whether it modifies data, or how scoring works. Adequate but not detailed.
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: purpose, scoring detail, return fields and quotas. Front-loaded with key information, no unnecessary 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?
Given no output schema, description lists return fields but not their types. For a tool returning scores, types (number) are implicitly clear. Quota info adds context. Slightly incomplete but sufficient.
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%, so baseline is 3. Description adds no extra meaning beyond what schema already provides for 'count' and 'locale' (e.g., count range already in schema). No added value.
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?
Description clearly states the verb 'Find' and resource 'next N best video topic opportunities', and distinguishes itself from sibling tools like youtube_get_recommendations by focusing on opportunity scoring.
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?
Description implies usage for finding video topics but does not explicitly state when to use this tool vs alternatives like youtube_get_recommendations or youtube_generate_video. Quota info provided but no usage context.
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.
Most tools have distinct purposes and clear descriptions, but there is some potential confusion among the four Polymarket-related tools (categorize, edge, signals, top_traders) and among the multiple 'alya_' prefixed tools that query different data sources.
Naming patterns are mixed: some tools use 'alya_' prefix, others use action-based names like 'batch_calibrate' or 'image_gen', and YouTube tools all start with 'youtube_'. The inconsistency in prefixes and verb styles makes the set less predictable.
32 tools is high for an MCP server, and they span a wide, unrelated set of domains (Polymarket, YouTube, gemology, weather, earthquakes, health, celebrity, etc.), making the surface feel bloated and unfocused.
Each domain has incomplete coverage: Polymarket lacks trade execution, YouTube automation depends on external OAuth, health tools only offer diagnosis and drug interactions without follow-up, and other domains have minimal tooling. The server feels like a collection of one-off features rather than a coherent surface.