Skip to main content
Glama
Sign In
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_cue_list_details

Retrieve details of a cue list and its cues with pagination to avoid context overflow, plus filtering and sorting for large lists.

Instructions

Get cue list with its cues, optionally paginated.

Parameters:

  • cueListId: Cue list to retrieve

  • page: Page number (default: 1)

  • perPage: Items per page (default: 50, max: 100)

  • includeLookDetails: Include full look data for each cue (default: false)

  • sortBy: Sort cues by cueNumber, name, or lookName

  • filterBy: Optional filters (cueNumberRange, nameContains, etc.)

By default, each cue includes lookId and lookName but NOT full look fixture values. Set includeLookDetails=true only if you need full look data for every cue (this can be very large).

For large cue lists (50+ cues), use pagination to avoid context overflow.

Returns:

  • Cue list metadata

  • Paginated cues array

  • Pagination info (total, page, perPage, hasMore)

  • Statistics (averages, counts, ranges)

  • Lookup tables for quick reference

Example workflow:

  1. list_cue_lists(projectId) - Find available cue lists

  2. get_cue_list_details(cueListId, page=1) - Get first page of cues

  3. If pagination.hasMore, call with page=2, etc.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (min 1)
sortByNoSort cues by cue number, name, or look namecueNumber
perPageNoItems per page (min 1, max 100)
filterByNoOptional filters to apply to the cue list
cueListIdYesCue list ID to query
includeLookDetailsNoInclude full look data for each cue (default: false for performance)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.7.0
    • addedInput schema / properties / filterBy / properties / lookNameContains
      Added value: +{
+  "description": "Filter cues where look name contains this text (case-insensitive)",
+  "type": "string"
+}
    • removedInput schema / properties / filterBy / properties / sceneNameContains
      Removed value: -{
-  "description": "Filter cues where scene name contains this text (case-insensitive)",
-  "type": "string"
-}
    • addedInput schema / properties / includeLookDetails
      Added value: +{
+  "default": false,
+  "description": "Include full look data for each cue (default: false for performance)",
+  "type": "boolean"
+}
    • removedInput schema / properties / includeSceneDetails
      Removed value: -{
-  "default": true,
-  "description": "Include detailed scene information for each cue",
-  "type": "boolean"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number for pagination (min 1)",
+  "type": "number"
+}
    • addedInput schema / properties / perPage
      Added value: +{
+  "default": 50,
+  "description": "Items per page (min 1, max 100)",
+  "type": "number"
+}
    • changedInput schema / properties / sortBy / description
      Previous value: -"Sort cues by cue number, name, or scene name"New value: +"Sort cues by cue number, name, or look name"
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
-  "cueNumber",
-  "name",
-  "sceneName"
-]New value: +[
+  "cueNumber",
+  "name",
+  "lookName"
+]
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: includeLookDetails can produce very large payloads, pagination prevents context overflow, and defaults for page/perPage. It does not mention any auth/permission requirements or error behavior, which is a modest gap for a no-annotation tool.

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?

Front-loaded with the core purpose, then organized into Parameters, Returns, and Example workflow sections that are easy to scan. The parameter list largely duplicates the schema descriptions, which is minor waste given the useful additions around payload size and pagination.

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 tool with no output schema, the description compensates by enumerating the return shape (metadata, cues array, pagination info, statistics, lookup tables). Combined with defaults, sorting, and filtering hints, an agent has everything needed to call it correctly.

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 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: the warning that includeLookDetails may be 'very large' and the default/max guidance on pagination that frames when to use it. The filterBy examples are listed only sketchily ('etc.'), so it does not fully enrich every parameter.

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?

States a specific verb and resource ('Get cue list with its cues, optionally paginated') and distinguishes itself from the sibling list_cue_lists by casting that tool as the discovery step in the worked example. An agent can tell immediately that this retrieves the contents of one known cue list rather than enumerating lists.

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

Usage Guidelines5/5

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

The example workflow explicitly names list_cue_lists as the alternative for finding lists, then routes to this tool with page=1 and subsequent pages when hasMore is true. It also gives a conditional rule for includeLookDetails ('only if you need full look data') and a concrete threshold for pagination (50+ cues).

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

Deploy Server

Other Tools