Skip to main content
Glama

job_youtube_search

YouTube search results for one query

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "job_youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYespattern [^\r\n]{1,200}
max_resultsNodefault 20, at most 200

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and delivers almost nothing beyond the title. It does not say whether results are capped, ordered, paginated, or whether the call is expensive/network-bound, nor what a result item contains.

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?

A single short sentence with no filler and the key scope (one query) front-loaded. Its brevity is efficient rather than padded, though it errs toward under-specification.

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

Completeness2/5

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

The tool has no annotations and no output schema, so the description must explain the return shape and result limits, and it does neither. For a search tool whose output format is entirely undocumented elsewhere, this leaves the agent unable to predict what it will receive.

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%, with the schema already documenting query as a string with a pattern and max_results with a default of 20 and a cap of 200. The description adds only the "one query" framing, which is marginal but consistent with the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "YouTube search results for one query" names the resource and implies the search verb, so an agent can guess it retrieves search results. However, it never states the verb explicitly and gives no basis for distinguishing it from siblings such as job_youtube_channel or job_youtube_transcript beyond the word "search".

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the channel, comments, or transcript tools, and no stated prerequisites or exclusions. The only implied constraint is that it handles a single query, which the agent gets from the name anyway.

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