Retrieve Plex library items grouped by decade for a specific section ID, enabling decade-based browsing and filtering of your media collection.
Get By Decade.
GET /library/sections/{sectionId}/byDecade
Args: section_id: The unique identifier of the library section
| Name | Required | Description | Default |
|---|---|---|---|
| section_id | Yes |
| 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. The description adds little behavioral context beyond repeating the GET path; it does not disclose grouping behavior, result size, pagination, or any other trait that would help the agent reason about side effects or response handling.
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 short, structured, and front-loaded with the endpoint. The Args block is clean, though the opening phrase 'Get By Decade' is somewhat redundant with the tool name and endpoint.
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?
For a read-only lookup with one well-defined integer parameter and an output schema, the essential call information (endpoint and parameter) is present. However, the description is not self-sufficient as a purpose statement and gives no context about what grouping by decade means, making it weaker in tool-selection contexts.
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?
The only parameter, section_id, is described as 'The unique identifier of the library section.' Even though schema description coverage is 0%, the description meaningfully explains the sole required argument. It lacks examples or constraints, but for a simple integer identifier this is adequate.
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 is essentially a fragment: 'Get By Decade.' It includes the HTTP path (GET /library/sections/{sectionId}/byDecade), which supplies the resource and action, so it is more than a pure tautology. However, it does not explain what 'byDecade' returns or how it differs from sibling endpoints like by_year or by_resolution.
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 provided about when to use this tool versus alternatives. The path implies it is a filtered library-section query, but there is no explicit when/when-not or mention of sibling tools that may be more appropriate for year or resolution-based queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.