Skip to main content
Glama

List releases to plan

list_releases
Read-onlyIdempotent

Upcoming catalog releases with your saved tier and suggest-v1 suggestion. Needs a connected account with the plan: the token from start_planner or one made at /agents (401 connection-required without it). Filter by from/to (releaseDate), query (case-insensitive title search), format and untieredOnly; limit defaults to 50 (max 200) and total counts every match. Releases opening today or later come first, then those at the most theatres. releaseDate is AMC's release date or, when AMC has none, the earliest local showing date (the film's own, or its special screenings' when it has none); dateSource says which (amc or first-showing). Special screenings (Early Access, Fan Event, Q&A, anniversary, Insider, Opening Night and similar) appear under their base film as screenings [{id, label}]; one whose base film isn't in the catalog is its own release. Suggestions are advice, never intent. filmId is the AMC movie id and stays the same when the film joins your plan: pass it, or a screening's id, to set_tier, set_format_preference, get_plan, get_best_showings and request_booking. Planner responses name each film's filmId (the planner's own) and amcMovieId (this id).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest releaseDate (YYYY-MM-DD).
fromNoEarliest releaseDate (YYYY-MM-DD).
limitNo
queryNoCase-insensitive title search; also matches special screenings' titles.
formatNoOnly releases with upcoming listed showings in this format.
untieredOnlyNoOnly releases without a tier on your plan.

Output Schema

NameRequiredDescriptionDefault
totalYes
releasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / releases / items / properties / filmId / description
      Added value: +"The AMC movie id, the same before and after the film joins your plan. Every planner tool accepts it."
    • addedOutput schema / properties / releases / items / properties / screenings / items / properties / id / description
      Added value: +"The special screening's AMC movie id."
  2. Changed17 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Only releases with upcoming listed showings in this format.",
      +  "enum": [
      +    "dolby",
      +    "imax",
      +    "prime",
      +    "3d",
      +    "laser",
      +    "digital",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Earliest releaseDate (YYYY-MM-DD).",
      +  "format": "date",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Case-insensitive title search; also matches special screenings' titles.",
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Latest releaseDate (YYYY-MM-DD).",
      +  "format": "date",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / untieredOnly
      Added value: +{
      +  "description": "Only releases without a tier on your plan.",
      +  "type": [
      +    "boolean",
      +    "string"
      +  ]
      +}
    • changedOutput schema / properties / releases / items / additionalProperties
      Previous value: -{
      -  "$ref": "#/definitions/__schema0"
      -}New value: +false
    • addedOutput schema / properties / releases / items / properties / dateSource
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "amc",
      +        "first-showing"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / releases / items / properties / filmId
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / releases / items / properties / releaseDate
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / releases / items / properties / screenings
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / releases / items / properties / suggestion
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "$ref": "#/definitions/__schema0"
      +      },
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / releases / items / properties / tier
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "top",
      +        "want",
      +        "maybe",
      +        "skip",
      +        "seen",
      +        "declined"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / releases / items / properties / title
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / releases / items / required
      Added value: +[
      +  "filmId",
      +  "title",
      +  "releaseDate",
      +  "dateSource",
      +  "tier",
      +  "suggestion",
      +  "screenings"
      +]
    • addedOutput schema / properties / total
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "releases"
      -]New value: +[
      +  "releases",
      +  "total"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description is free to add the genuinely new behavior, which it does: required auth and the 401 failure mode, limit default 50 / max 200, that total counts every match rather than the page, and non-obvious sort ordering (today-or-later first, then most theatres). It also discloses data-shape quirks — dateSource tagged amc vs first-showing, and special screenings nested under their base film unless the base is absent from the catalog.

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

Conciseness4/5

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

Purpose, auth, filters, ordering, date semantics, screenings, and the filmId handoff are ordered sensibly with the most decision-relevant facts first. It is dense and runs long in places (the AMC/local date and base-film screening clauses require a re-read), but nearly every sentence carries operational information an agent would otherwise get wrong.

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?

For a six-parameter read with an output schema, the description covers everything that would cause misuse: auth failure mode, pagination semantics, sort order, date-source ambiguity, nested screening shape, and the filmId vs amcMovieId identifier mapping. Return values are left to the output schema as appropriate.

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?

Schema coverage is already 83%, so the baseline is 3; the description earns more by clarifying that format means releases with upcoming listed showings, that untieredOnly is relative to 'your plan', and that total reflects all matches while limit caps the page. Minor overlap remains (from/to as releaseDate, query as case-insensitive title search are restated from the 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 opening clause states a specific verb and resource — upcoming catalog releases enriched with the saved tier and suggest-v1 suggestion — which is clearly distinct from siblings like search_showtimes, get_best_showings, and get_movie. The agent can tell what it gets back without opening the schema.

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?

Prerequisites are explicit (connected account with a plan; token from start_planner or /agents, otherwise 401 connection-required), and the filmId paragraph implicitly maps the downstream workflow (set_tier, set_format_preference, get_plan, get_best_showings, request_booking). It stops short of an explicit 'use this instead of search_showtimes when...' exclusion, so a 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources