post_dataforseo_serp_youtube_video_comments_liveLive YouTube Comments provides real-time data on comments on the video you specify in the request. You will get the top 20 comments on the video as well as information about the author, and key comment metrics.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / body / items / properties / language_code / descriptionPrevious value: -"YouTube interface language code, for example en. Provide this or language_name."New value: +"search engine language code required field if you don't specify language_name if you use this field, you don't need to specify language_name you can receive the list of available languages of the search engine with their language_code_by making a separate request to the https://api.dataforseo.com/v3/serp/youtube/languages example: enn"Input schema / properties / body / items / properties / language_name / descriptionPrevious value: -"YouTube interface language name, for example English. Provide this or language_code."New value: +"full name of search engine language required field if you don't specify language_code if you use this field, you don't need to specify language_code you can receive the list of available languages of the search engine with their language_name by making a separate request to the https://api.dataforseo.com/v3/serp/youtube/languages example: English"Input schema / properties / body / items / properties / location_code / descriptionPrevious value: -"YouTube location code, for example 2840. Provide this or location_name."New value: +"search engine location code required field if you don't specify location_name_ if you use this field, you don't need to specify location_name you can receive the list of available locations of the search engines with their location_code by making a separate request to the https://api.dataforseo.com/v3/serp/youtube/locations example: 2840n"Input schema / properties / body / items / properties / location_name / descriptionPrevious value: -"YouTube location name, for example United States. Provide this or location_code."New value: +"full name of search engine location required field if you don't specify location_code if you use this field, you don't need to specify location_code you can receive the list of available locations of the search engine with their location_name by making a separate request to the https://api.dataforseo.com/v3/serp/youtube/locations example: United States"Input schema / properties / body / items / properties / video_id / descriptionPrevious value: -"ID of the video"New value: +"ID of the video required field you can find video ID in the URL or 'youtube_video' item of YouTube Organic result example: vQXvyV0zIP4"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds no behavioral context beyond output content, such as API credit consumption, authentication needs, or side effects. It merely says the tool provides data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with what the tool returns. No filler or redundant restatement of the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a complex nested body with required field combinations, yet the description does not mention input structure, usage routing, or behavioral warnings. Output schema exists so return values need not be explained, but the description is still insufficient given the complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% per context signals. The description only says 'the video you specify in the request', which hints at video_id but does not explain the body array structure, required fields, or the location/language alternatives. It fails to compensate for the low schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States it provides real-time comments on a specified video and details the return content (top 20 comments, author info, comment metrics). The resource is clear, but it does not explicitly differentiate itself from siblings like youtube_video_info_live or youtube_video_subtitles_live.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is given. It does not mention alternatives, prerequisites, or conditions that would select this tool over related siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.