Skip to main content
Glama

Load Sequencer skill

get_sequencer_skill
Read-onlyIdempotent

Load instructions selected from list_sequencer_skills. Public workflows need no sign-in. Personal skills (my- IDs) require authentication and are read only from the current account. User-authored instructions remain subject to tool permissions and production approvals. Generates no media.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skillId": "<skillId>"
    },
    "name": "get_sequencer_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillIdYesExact skillId returned by list_sequencer_skills.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / skillId / description
      Added value: +"Exact skillId returned by list_sequencer_skills."
    • removedInput schema / properties / skillId / enum
      Removed value: -[
      -  "remotion-motion-design",
      -  "film",
      -  "url-to-video",
      -  "create-game",
      -  "restaurant-menu-to-video",
      -  "news-to-video",
      -  "architectural-walkthrough",
      -  "article-to-podcast"
      -]
    • addedInput schema / properties / skillId / maxLength
      Added value: +100
    • addedInput schema / properties / skillId / minLength
      Added value: +1
    • addedInput schema / properties / skillId / pattern
      Added value: +"^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$"
  2. Added
  3. Removed
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description adds genuinely new behavior: authentication requirements for personal skills, account-scoped reads, and that loaded user-authored instructions are still gated by tool permissions and production approvals. The 'Generates no media' line usefully preempts a wrong inference in a media-heavy sibling set, though return shape/pagination is unaddressed.

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?

Four short sentences, front-loaded with the action and its source list, then behavior, then scope caveats. No filler, though the sentence fragments ('Generates no media.') read as terse telegraphic notes rather than fully composed prose.

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

Completeness4/5

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

For a one-parameter read tool with full schema coverage and annotations, the description covers auth, account scoping, and downstream permission gating, which is what an agent needs before calling. The only real gap is that there is no output schema and the description doesn't characterize what the loaded instructions look like in the response.

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 schema already documents skillId, but the description adds meaning beyond it by explaining the 'my-' ID namespace and why those IDs behave differently at call time. That namespace semantics is real added value, not a restatement of the pattern.

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 ('Load instructions') plus the exact selector ('selected from list_sequencer_skills'), which distinguishes it from the sibling lister in the same family. An agent can tell immediately that this retrieves skill content rather than enumerating skills.

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?

It clearly implies the workflow of listing first and then loading a chosen ID, and it gives the branch condition that matters for calling it (public workflows need no sign-in vs. my- IDs require auth). It stops short of stating explicit exclusions or when not to call it, so it is strong but not complete routing guidance.

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.