PyScrappy

Overview Schema Source Related Servers Discussions Admin

Search Youtube

search_youtube

Finds YouTube videos matching a query and returns their titles, channels, URLs, durations, view counts, and upload dates.

Instructions

Search YouTube for videos matching a query and return a list of matching videos with their metadata.

Performs a live YouTube search over the network, so results reflect current YouTube data and may vary between calls; it is read-only and has no side effects. Returns a list of video objects, each typically containing: title (str), channel (str), url/link (str) to the video, video_id (str), duration (str), view_count (int), and published/upload date (str). Returns an empty list when the query matches no videos.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The search text, as a string. Example: "model context protocol tutorial". No default (required).
`max_results`	No	Maximum number of videos to return, as an integer. Example: 10. Default 20.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 31, 2026

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of videos to return (default 20)."New value: +"Maximum number of videos to return, as an integer. Example: 10. Default 20."

changedInput schema / properties / query / description

Previous value: -"Search query, e.g. \"model context protocol tutorial\"."New value: +"The search text, as a string. Example: \"model context protocol tutorial\". No default (required)."

Changed18 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / max_results / description

Added value: +"Maximum number of videos to return (default 20)."

removedInput schema / properties / max_results / title
```
Removed value: -"Max Results"
```

addedInput schema / properties / query / description

Added value: +"Search query, e.g. \"model context protocol tutorial\"."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

removedInput schema / title

Removed value: -"search_youtubeArguments"

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

Addedv1.2.0Jul 26, 2026
Removedv1.1.7Jul 26, 2026
First observedv1.1.6Jul 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses live network search, variability between calls, read-only nature with no side effects, and empty-list behavior on no matches. This is strong behavioral context, though it omits potential rate limits or auth requirements.

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?

Two sentences with the main purpose front-loaded. The second sentence packs useful behavioral and return details without filler. The enumeration of return fields is slightly verbose but valuable, keeping the overall structure efficient.

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 two-parameter search tool, the description covers purpose, network behavior, read-only status, return shape, and empty-case handling. With an output schema present, the return-field listing is redundant but not problematic. Missing edge cases like errors or pagination are minor.

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 already documents query and max_results with types, examples, and defaults. The description adds no parameter-specific meaning beyond what the schema provides, so baseline 3 applies.

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 verb and resource: 'Search YouTube for videos matching a query and return a list of matching videos with their metadata.' This clearly distinguishes it from sibling tools like search_images or search_hackernews by naming YouTube directly.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance, and no mention of alternative tools. The purpose is implied by the name and description, but an agent must infer when to select this over other search tools. The live-network and read-only context hints at behavior, not usage selection.

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