Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

youtube_suggest

Read-only

Returns YouTube search-box autocomplete completions for a query prefix in YouTube's own ranking order. Use for video-topic keyword research (the list differs from google_suggest); accepts optional hl language and gl region codes.

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": {
      "q": "<q>"
    },
    "name": "youtube_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query prefix to autocomplete. Required, e.g. openai.
CountNoSuggestions to return, default 10, clamped to 1..20.
RegionNoTwo-letter YouTube region code, default US.
LanguageNoYouTube interface language, default en.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the notable behavioral trait that results come in YouTube's own ranking order, which is useful, but it doesn't cover return format details like ordering stability or rate limits. With annotations doing the heavy lifting, a 3 is appropriate.

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?

Two compact sentences, zero waste. The scoping purpose is front-loaded before the differentiating note about google_suggest.

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?

An output schema exists, so return values needn't be explained. The description covers purpose, use case, and the key differentiator from a close sibling. It is nearly complete for a four-parameter research 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 each parameter is already documented with examples and defaults. The description mentions the hl/gl language and region options but adds no format or constraint detail beyond what the schema provides. Baseline 3 is correct when the schema carries the burden.

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?

Specific verb and resource: returns YouTube search-box autocomplete completions for a query prefix. It also distinguishes itself from the sibling set by contrasting the output with google_suggest, so an agent can tell the two apart without inspecting schemas.

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?

Explicitly states the use case ('Use for video-topic keyword research') and notes the distinction from google_suggest. It does not spell out when not to use it or name other autocomplete siblings (e.g. youtube_search vs youtube_suggest), but the intended context is clear.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources