Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein

update_cue_list

Modify cue list names or descriptions in the LacyLights MCP Server by providing the cue list ID and optional new details to ensure accurate and updated lighting design instructions.

Instructions

Update cue list name or description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cueListIdYesCue list ID to update
descriptionNoNew description for the cue list
nameNoNew name for the cue list

Implementation Reference

  • The core handler function that executes the update_cue_list tool logic by calling the GraphQL client to update the cue list's name, description, or loop setting.
    async updateCueList(args: {
      cueListId: string;
      name?: string;
      description?: string;
      loop?: boolean;
    }) {
      const { cueListId, name, description, loop } = args;
    
      try {
        if (!name && !description && loop === undefined) {
          throw new Error(
            "At least one field (name, description, or loop) must be provided",
          );
        }
    
        const updatedCueList = await this.graphqlClient.updateCueList(cueListId, {
          name,
          description,
          loop,
        });
    
        return {
          cueListId: updatedCueList.id,
          cueList: {
            name: updatedCueList.name,
            description: updatedCueList.description,
            loop: updatedCueList.loop,
            totalCues: updatedCueList.cues.length,
          },
          success: true,
        };
      } catch (error) {
        throw new Error(`Failed to update cue list: ${error}`);
      }
    }
  • src/index.ts:1309-1333 (registration)
    MCP tool registration defining the 'update_cue_list' tool name, description, and input schema.
      name: "update_cue_list",
      description: "Update cue list name or description",
      inputSchema: {
        type: "object",
        properties: {
          cueListId: {
            type: "string",
            description: "Cue list ID to update",
          },
          name: {
            type: "string",
            description: "New name for the cue list",
          },
          description: {
            type: "string",
            description: "New description for the cue list",
          },
          loop: {
            type: "boolean",
            description: "Whether to loop the cue list (restart from first cue after last cue finishes)",
          },
        },
        required: ["cueListId"],
      },
    },
  • src/index.ts:2311-2323 (registration)
    Dispatch handler in the MCP server that routes 'update_cue_list' calls to the CueTools.updateCueList method.
    case "update_cue_list":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.cueTools.updateCueList(args as any),
              null,
              2,
            ),
          },
        ],
      };
  • GraphQL client method called by the handler, defining the backend mutation schema and execution.
    async updateCueList(id: string, input: {
      name?: string;
      description?: string;
      loop?: boolean;
    }): Promise<CueList> {
      const mutation = `
        mutation UpdateCueList($id: ID!, $input: CreateCueListInput!) {
          updateCueList(id: $id, input: $input) {
            id
            name
            description
            loop
            createdAt
            updatedAt
            cues {
              id
              name
              cueNumber
              fadeInTime
              fadeOutTime
              followTime
              notes
              scene {
                id
                name
              }
            }
          }
        }
      `;
    
      // Since the backend expects CreateCueListInput which requires projectId,
      // we need to get the current cue list first to maintain the projectId
      const cueListQuery = `
        query GetCueList($id: ID!) {
          cueList(id: $id) {
            id
            name
            loop
            project {
              id
            }
          }
        }
      `;
      
      const cueListData = await this.query(cueListQuery, { id });
      const projectId = cueListData.cueList.project.id;
    
      const updateInput = {
        name: input.name || cueListData.cueList.name,
        description: input.description,
        loop: input.loop !== undefined ? input.loop : cueListData.cueList.loop,
        projectId
      };
    
      const data = await this.query(mutation, { id, input: updateInput });
      return data.updateCueList;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Update' which implies a mutation operation, but doesn't specify required permissions, whether changes are reversible, error conditions, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action ('Update cue list') and specifies the updatable attributes ('name or description') directly. Every word earns its place, making it highly concise and well-structured.

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

Completeness2/5

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

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or error handling, nor does it explain return values. For a 3-parameter update operation in a context with multiple sibling tools, more contextual information is needed to be fully helpful.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters (cueListId, description, name) and their types. The description adds marginal value by confirming that name and description are updatable fields, but doesn't provide additional syntax, constraints, or examples beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb 'Update' and the resource 'cue list', specifying what can be updated ('name or description'). It distinguishes from siblings like 'update_cue' (which updates individual cues) and 'reorder_cues' (which changes cue order), but doesn't explicitly contrast them. The purpose is specific but lacks explicit sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing cue list), exclusions (e.g., not for creating new cue lists), or comparisons to siblings like 'create_cue_sequence' or 'update_cue'. Usage is implied from the action but not explicitly defined.

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

Related 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/bbernstein/lacylights-mcp'

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