Skip to main content
Glama

sponsor_segments

Fetch SponsorBlock skip segments for any YouTube URL to identify sponsor, intro, and other non-content sections; returns category, timestamps, and action type, or an empty list when none exist.

Instructions

Fetch SponsorBlock skip segments for a YouTube URL. Returns the configured categories plus a list of {start, end, category, action_type, uuid} segments. Empty list when none exist (404). Errors only on network/parse failure or non-YouTube URLs.

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": {
      "url": "<url>"
    },
    "name": "sponsor_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube URL (watch / shorts / youtu.be / embed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden: it discloses the return shape ({start, end, category, action_type, uuid}), that the configured categories are included, that a 404 maps to an empty list rather than an error, and the two failure conditions. Unstated are auth requirements, caching, and rate limits, which keeps it from a 5.

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 sentences, front-loaded with purpose, then return contract, then error semantics. No filler and each sentence adds distinct information.

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?

With no annotations and no output schema, the description does the necessary work by specifying the returned fields and 404-as-empty behavior. It leaves open how 'configured categories' is determined, but for a single-parameter read tool it is close to complete.

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 coverage is 100% and the URL format variants (watch / shorts / youtu.be / embed) are already documented in the schema itself. The description only adds the constraint that non-YouTube URLs are an error, which is a marginal gain beyond structured data.

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: 'Fetch SponsorBlock skip segments for a YouTube URL.' It names the upstream data source and the entity being retrieved, which no sibling tool does, so an agent can identify it immediately.

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?

Implies usage for any YouTube URL and gives an explicit boundary: errors occur only on network/parse failure or non-YouTube URLs. It does not name an alternative tool, but no comparable sibling is present in the provided list, so the missing 'instead of X' clause is minor.

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

Deploy Server

Other Tools