yzturkey-mcp

get_series_details

Retrieve comprehensive details for a specific series, including all themes/videos and their current statuses by providing the series ID.

Instructions

Get details of a specific series, including all themes/videos inside it and their statuses.

Args: series_id: Series/Batch UUID.

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": {
      "series_id": "<series_id>"
    },
    "name": "get_series_details"
  }
}

Input Schema

Name	Required	Description	Default
`series_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. The word 'Get' implies a read-only operation, and the description discloses the returned content. However, it does not explicitly confirm non-mutating behavior, mention auth requirements, error cases, or any operational limits, leaving room for clearer behavioral disclosure.

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?

The description is highly concise: one purpose sentence and a short Args block. The main function is front-loaded, every word earns its place, and there is no redundant detail.

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?

Given a single parameter and the presence of an output schema, the description covers the essential return aspects (themes/videos and their statuses). It doesn't need to fully describe the output structure because the schema exists. It omits edge cases or error handling, but that is acceptable for a straightforward read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description's Args block adds meaningful context: series_id is a 'Series/Batch UUID', going beyond the schema's bare string type. This is sufficient for the single-parameter interface, though it could have been slightly more detailed about the expected UUID format.

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?

The description states a specific verb ('Get'), resource ('details of a specific series'), and enumerates what is included (all themes/videos and their statuses). This clearly distinguishes it from list_series (which likely lists series) and update_series_settings (which modifies).

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?

The description implies when to use it: when you have a specific series_id and need composed details including themes/videos. However, it does not explicitly state when to prefer this over sibling tools like list_series, nor does it offer any exclusions or alternative routing.

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

Deploy Server