youtube.search
Search public YouTube content by keyword or phrase. Returns matching result cards, estimated result count, and spelling suggestions. Use filter parameters to apply multiple YouTube search filters: - upload_date: Last hour, Today, This week, This month, This year - content_type: Video, Channel, Pl...
This record as markdown: /tools/io-github-vee3io-vee3/youtube.search.md
What youtube.search does on Vee3
AI agents call youtube.search to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search keywords or phrase. |
cursor | object | — | Pagination cursor from cursorNext. |
sort_by | object | — | Sort order. One of: Relevance, Upload date, View count, Rating. |
duration | object | — | Duration filter. One of: Under 4 minutes, 4 - 20 minutes, Over 20 minutes. |
features | object | — | Feature filters. Multiple allowed. Each value must be one of: Live, 4K, HD, Subtitles/CC, Creative Commons, 360°, VR180, 3D, HDR, Location, Purchased. |
language | string | — | Language code for localized results (for example en). |
location | string | — | Country code for localized results (for example US). |
upload_date | object | — | Upload date filter. One of: Last hour, Today, This week, This month, This year. |
content_type | object | — | Content type filter. One of: Video, Channel, Playlist, Movie. |
Parameters from the server's own tool schema.
Why youtube.search is rated Low
This tool purely retrieves publicly available YouTube search results. It has no side effects, does not modify or delete any data, and does not execute code or trigger external operations. It is a straightforward read/query operation.
From the tool's definition Search public YouTube content by keyword or phrase. Returns matching result cards, estimated result count, and spelling suggestions.
Attacks that exploit this kind of access
The rule that runs youtube.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube.search, this is the rule to start with:
youtube.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every youtube.search call is checked against it from then on.
Questions about youtube.search
Search public YouTube content by keyword or phrase. Returns matching result cards, estimated result count, and spelling suggestions. Use filter parameters to apply multiple YouTube search filters: - upload_date: Last hour, Today, This week, This month, This year - content_type: Video, Channel, Playlist, Movie - duration: Under 4 minutes, 4 - 20 minutes, Over 20 minutes - features: Live, 4K, HD, Subtitles/CC, Creative Commons, 360°, VR180, 3D, HDR, Location, Purchased (multiple allowed) - sort_by: Relevance, Upload date, View count, Rating Filter values are matched case-insensitively. Only one option per group applies except features, which accepts multiple labels. When a requested filter cannot be applied, the API returns the best-effort results available so far and includes unappliedFilters with the labels that were skipped. Use cursor with the same query to paginate: pass cursorNext from a prior response. Filter parameters and cursor cannot be combined. Check didYouMean when the query may be misspelled. Cost = 20 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
youtube.search accepts 9 parameters: query, cursor, sort_by, duration, features, language, location, upload_date, content_type. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for youtube.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Vee3. Nothing to install.
youtube.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the youtube.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for youtube.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
youtube.search is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue