Skip to main content
Glama

list_track_items

Read-only

List timeline items across all tracks, a track type, or a specific track; enable detail to inspect types, source ranges, offsets, colors, and flags.

Instructions

Items on a timeline (all tracks, one track type, or one track) with ref, name, record range, track, enabled, source clip. detail=true adds type, source range, offsets, color and flags.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
detailNo
timelineNo
track_typeNo
track_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that by naming the returned fields and explaining exactly what detail=true expands (type, source range, offsets, color, flags) — valuable since there is no output schema. It stops short of disclosing the limit default of 1000 or any truncation/pagination behavior, which matters for a list 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?

Two dense sentences with the resource and scope front-loaded and the detail behavior last; nothing is redundant. The telegraphic field list ('ref, name, record range, track, enabled, source clip') is terse but readable and earns its space by standing in for a missing output schema.

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

Completeness3/5

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

For a 5-parameter tool with zero schema coverage and no output schema, the description covers return fields and the detail flag well. It leaves the default limit and its implications, the polymorphic timeline argument, and the track_index/track_type relationship undocumented, which are real gaps for a list endpoint.

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 0%, so the description must carry the burden. It meaningfully explains detail=true and the three scope modes that map to timeline/track_type/track_index, but says nothing about limit (default 1000), does not reveal that timeline accepts either a string name or an integer id, and does not clarify whether track_index is dependent on track_type.

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?

Names the resource (items on a timeline) and enumerates the three scoping modes — all tracks, one track type, or one track — plus the fields returned. The listing verb is implicit rather than stated, but an agent can tell this apart from mutating siblings like delete_items or add_track 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 Guidelines3/5

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

The parenthetical 'all tracks, one track type, or one track' implies when each scoping mode applies, but there is no explicit when-to-use vs when-not guidance. No mention of how this relates to alternatives such as get_selected_items or list_clips, so the agent must infer the routing.

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