Skip to main content
Glama

YouTube Transcript + YouTube Search MCP

Get Video Dislikes

get_video_dislikes
Read-only

Use this when the user asks how many dislikes a YouTube video has, or how well liked it is. YouTube no longer publishes dislikes, so this returns estimates from Return YouTube Dislike: likes, dislikes, a star rating and the view count. Say that the numbers are estimates.

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": {
      "video_url": "<video_url>"
    },
    "name": "get_video_dislikes"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_urlYesYouTube URL (full or short) or an 11-character video ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the safe read-only profile. The description goes well beyond them by disclosing that YouTube no longer publishes dislikes, that values come from a third-party estimator, that they are estimates, and that the agent should surface that caveat to the user — exactly the reliability context needed here.

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?

Three short sentences with no waste: trigger first, data-source caveat second, user-facing behavior last. The most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description enumerates the return payload (likes, dislikes, star rating, view count) and explains the provenance of those numbers. For a one-parameter read tool, nothing an agent needs is missing.

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% and the single video_url parameter is already documented as accepting a full URL, short URL, or 11-character ID. The description adds nothing about input format, 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 concrete verb and resource (returns dislike estimates for a YouTube video) plus the data source, Return YouTube Dislike. It lists the exact returned figures, so it is distinguishable from every sibling, none of which touch engagement metrics.

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?

Gives an explicit trigger: 'Use this when the user asks how many dislikes a YouTube video has, or how well liked it is.' It does not name a when-not case or an alternative tool, but no sibling overlaps this capability, so the routing risk is low.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.