Skip to main content
Glama
SavageCore
by SavageCore

seerr_list_discover_movies

Read-only

Search and discover movies using filters like genre, keywords, certifications, ratings, release dates, and streaming providers.

Instructions

Discover movies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
genreNo
studioNo
sort_byNo
keywordsNo
languageNo
watch_regionNo
certificationNo
vote_count_gteNo
vote_count_lteNo
watch_providersNo
exclude_keywordsNo
vote_average_gteNo
vote_average_lteNo
with_runtime_gteNo
with_runtime_lteNo
certification_gteNo
certification_lteNo
certification_modeNo
certification_countryNo
primary_release_date_gteNo
primary_release_date_lteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description adds no behavioral context beyond the readOnlyHint annotation. It does not describe the returned data, pagination behavior, or any side effects. The annotation already covers safety, but the tool's actual output/behavior remains undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. The phrase adds no information beyond what is already in the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (22 optional parameters, output schema, many siblings), this minimal description is grossly inadequate. It does not explain what the tool does, how to use it, or what results to expect.

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

Parameters1/5

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

With 22 parameters and 0% schema description coverage, the description should clarify parameter semantics, but it does not mention any parameters or their intended use.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Discover movies' is essentially a restatement of the tool name, omitting the 'list' aspect. It does not distinguish from sibling tools like seerr_list_discover_tv or seerr_list_discover_movies_upcoming, providing only a vague verb+resource with no specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus other discovery tools. The description offers no mention of filters, pagination, or alternatives.

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/SavageCore/seerr-mcp'

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