Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search YouTube

search_youtube
Read-only

Search YouTube videos by keyword to mine hooks, angles, and long-form structure. Returns ranked compact video data including title, author, plays, link, and cover.

Instructions

Organic YouTube keyword search (/v1/youtube/search) — videos to mine for hooks/angles/long-form structure. Returns compact JSON {desc (title), author, handle, plays, link, cover} per video, ranked by views. Spends about a credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax videos returned (1–25, default 8)
queryYeskeyword to search videos for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "found": {
-      "description": "total videos found",
-      "type": "number"
-    },
-    "videos": {
-      "description": "the compact video objects ({desc, author, handle, plays, link, cover}), ranked by views",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, so the description adds valuable context the annotations do not: the endpoint, the exact compact JSON fields returned, ranking by views, and approximate credit cost. This exceeds what the structured annotations alone provide.

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

Conciseness5/5

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

The description is tight and front-loaded: first the core operation, then return shape, then ranking, then cost. Every sentence earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only search tool with no output schema, the description is complete: it covers the purpose, the output structure, ordering, and resource cost. Nothing essential is missing for selecting or invoking the tool.

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 description coverage is 100%, so the schema fully documents the 'query' and 'limit' parameters. The description adds nothing about parameter behavior beyond the schema, which meets the baseline but does not exceed it.

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 action ('keyword search') and resource (YouTube), plus the intended downstream use ('mine for hooks/angles/long-form structure'). This clearly differentiates it from sibling search tools targeting other platforms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is given: use it for organic YouTube keyword research to find videos to mine. It does not explicitly name alternatives or state when not to use it, but the use case is specific enough that an agent can select it appropriately among the search_* siblings.

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

Deploy Server

Other Tools