Skip to main content
Glama

List the kit

list_kit
Read-onlyIdempotent

Outfits, places and props a music video brief can mention The kit is what a music video is made from besides the artist’s character: outfits, places and props. Each is in one artist’s kit (owner_artist_id, a project in a Creator workspace; an outfit’s is its artist_id) and serves their songs; shared true offers it to every other artist’s songs too (owner_name says whose it is). Each has a name and an @handle unique in the workspace; a music video brief (direction) that mentions @handle uses that piece exactly as it is, and the director designs the rest. With artist_id: what a brief for their song can mention, their own pieces first, then those other artists shared; with owner_artist_id: only their own (their kit page); without either, every piece. url is the piece cropped, up to 1536 px (what the AI receives; width and height describe it), thumbnail_url a 320 px copy, source_url the image the crop is a rectangle of. Every piece by default; pass q to search by name, @handle or description, and limit/offset to page. total is how many pieces match.

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_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPart of the name, @handle or description
kindNooutfit, place or prop
limitNoPieces per page, 1-100 (default: every piece)
offsetNoHow many pieces to skip
artist_idNoWhat a brief for this artist’s song can mention: theirs and those shared
owner_artist_idNoOnly the pieces in this artist’s kit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / artist_id / description
      Previous value: -"Only the workspace’s pieces and this artist’s outfits"New value: +"What a brief for this artist’s song can mention: theirs and those shared"
    • addedInput schema / properties / owner_artist_id
      Added value: +{
      +  "description": "Only the pieces in this artist’s kit",
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Pieces per page, 1-100 (default: every piece)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "How many pieces to skip",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Part of the name, @handle or description",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, so the bar is lower, but the description adds real payload context: the default returns every piece with no paging, url is a crop up to 1536 px, thumbnail_url is a 320 px copy, source_url is the uncropped original, and total is the match count. It also explains the shared-visibility model (shared true exposes a piece to every other artist's songs). What it omits is any indication of result ordering when no artist filter is supplied or of payload size risk when paging is skipped.

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

Conciseness3/5

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

Most sentences carry useful domain information, but the opening is a fragment that runs straight into the next sentence without punctuation ('...can mention The kit is what...'), and the first half is domain exposition rather than an action statement. A reader must reach the second half before learning the filtering and paging behaviour, so it is not well front-loaded.

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?

With no output schema and six optional parameters, the description carries the return-value burden and does it well, naming name, @handle, shared, owner_name, url, thumbnail_url, source_url, width/height and total. It is missing only fields the agent might also receive (identifiers, kind) and the default sort order when listing everything.

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 coverage is 100%, so the schema already documents all six parameters, establishing a baseline of 3. The description does add genuine meaning on top — q searches name, @handle or description; artist_id results are ordered 'their own pieces first, then those other artists shared'; limit defaults to everything — but these are refinements of already-documented fields rather than filling a documentation gap.

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 defines the resource precisely — outfits, places and props making up an artist's kit — and the closing line 'Every piece by default' plus the filter behaviour makes clear this returns a collection rather than a single piece. It never states an explicit verb like 'list' (that lives only in the title) and never names the neighbouring get_kit_piece/list_looks, but the resource boundary is unambiguous.

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 gives explicit routing between the two artist parameters: artist_id for 'what a brief for their song can mention' (own plus shared), owner_artist_id for 'only their own (their kit page)', and neither for everything. That is strong when-to-use guidance for the filter combinations, though it never points to sibling tools such as get_kit_piece for a single piece or add_kit_piece for mutations.

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