List blacklisted episode subtitles with pagination support, enabling review and management of blocked subtitle entries.
List blacklisted episodes subtitles.
GET /api/episodes/blacklist
Args: start: Paging start integer length: Paging length integer
| Name | Required | Description | Default |
|---|---|---|---|
| start | No | ||
| length | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the GET endpoint and paging args, which is useful context, but it does not disclose any behavioral traits beyond what the annotations and schema already convey.
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?
The description is compact and front-loaded, with a clear one-line purpose, the HTTP endpoint, and a minimal argument list. There is no filler or redundant prose.
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?
Given the tool's low complexity, rich annotations, and existing output schema, the description covers the essential invocation details: endpoint and paging parameters. It falls slightly short by not explaining what 'blacklisted' means in this context or how this tool relates to nearby list_episodes endpoints.
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%, so the description must compensate. It does clarify that 'start' is a paging start and 'length' is a paging length, adding meaning beyond the bare schema titles. However, it does not explain default behavior, offset semantics, or how optional values are handled.
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?
The description states a specific verb ('List') and a specific resource ('blacklisted episodes subtitles'), making the tool's scope clear. The 'blacklist' qualifier distinguishes it from related siblings like list_episodes and list_movies_blacklist.
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 guidance is given about when to use this tool versus alternatives such as list_episodes or list_episodes_wanted. The description simply restates the tool's purpose and provides no exclusions, prerequisites, or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.