Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_search_hashtag

Search YouTube by hashtag and retrieve matching videos, channels, and playlists; use continuation tokens to page through results.

Instructions

youtube: Search by Hashtag. GET /v1/youtube/search/hashtag. Provide one of: hashtag, continuationToken. Search YouTube and get matching videos, channels, and playlists Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "hashtag": "<hashtag>"
    },
    "name": "youtube_search_hashtag"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoSearch for all types of content or only shorts
hashtagYesHashtag to search for
continuationTokenNoUse continuationToken from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by disclosing the credit model: 1 credit on success, zero cost for errors, blocked or timed-out requests, invalid requests, and cache hits. It says nothing about rate limits, auth requirements, or result-set caps, and the closing sentence about not-found charging is circular and adds no usable information.

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?

The purpose and endpoint come first and the response contents follow, which is good front-loading. The cost sentences are boilerplate-heavy and the final caveat about not-found charging is wordy and near-meaningless, but the total length stays manageable.

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?

For a three-parameter search tool with no output schema and no annotations, the description covers purpose, response surface, pagination, and cost. The remaining gap is that it never explains how `type` (shorts vs all) changes results, which is the one thing an agent could get wrong here.

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 baseline is 3. The description echoes the continuationToken paging intent ('get the next page') but says nothing about the `type` parameter's role in restricting to shorts, leaving that entirely to the schema.

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

Purpose4/5

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

States a specific verb+resource ('Search by Hashtag' on YouTube) and names the return surface (videos, channels, playlists), which separates it from narrow lookups like youtube_video or youtube_channel. It stops short of naming the sibling it competes with, youtube_search, so an agent must infer that hashtag-scoped search is the distinguishing factor.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is referenced despite youtube_search and youtube_search_typeahead being nearby. The line 'Provide one of: hashtag, continuationToken' actively muddies things, since the schema marks hashtag as required, leaving the agent unsure whether a token-only call is legal.

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