Skip to main content
Glama
ptbsare

overseerr-mcp-server

by ptbsare

overseerr_tv_requests

Retrieve TV show requests with filtering by availability status, creation date, and pagination controls for efficient request management.

Instructions

Get a paginated list of TV show requests that satisfy the filter arguments.

Args:
    status (Optional[str]): Filter by media availability status (e.g., "pending", "available", "approved"). Valid values: "all", "approved", "available", "pending", "processing", "unavailable", "failed". Defaults to all if omitted or invalid.
    start_date (Optional[str]): Filter for requests created on or after this date, formatted as 'YYYY-MM-DDTHH:MM:SS.mmmZ'.
    take (Optional[int]): The number of results to return (page size). Defaults to 7.
    skip (Optional[int]): The number of results to skip (for pagination). Defaults to 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo
takeNo
statusNo
start_dateNo
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explains pagination via take/skip, default values, status filter valid values, and date format. It does not mention authentication or response structure, but for a read-only list operation, it provides substantial transparency.

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 succinct, front-loaded with the main purpose, and uses a clear Args list. Every sentence adds value; no wasted words.

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?

Given no output schema, the description still provides a complete picture: what the tool returns (paginated list), all filter parameters, and defaults. It is fully adequate for selecting and invoking the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates. It explains each parameter's purpose, valid values for status, the expected date format, and defaults for take and skip, adding significant meaning beyond the raw schema.

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 clearly states the verb 'Get' and the resource 'paginated list of TV show requests,' with filter arguments. It distinguishes itself from the sibling tool overseerr_movie_requests by specifying TV show requests.

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?

The description implies this tool is for reading/filtering TV requests, contrasting with sibling tools like overseerr_request_tv_to_library (creating) and overseerr_movie_requests (movies). It does not explicitly name alternatives or exclusions, but the context is clear from the resource type.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ptbsare/overseerr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server