Skip to main content
Glama

get_item_properties

Retrieve media item properties including position, length, mute status, lock state, take name, playrate, and pitch from REAPER projects.

Instructions

Return properties of a media item: position, length, mute, lock, take name, playrate, and pitch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
item_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation in the adapter class that communicates with the bridge.
    def get_item_properties(
        self, track_index: int, item_index: int
    ) -> dict[str, Any]:
        return self._client.call(
            "get_item_properties",
            track_index=track_index,
            item_index=item_index,
        )
  • MCP tool registration and wrapper logic.
    @mcp.tool()
    def get_item_properties(track_index: int, item_index: int) -> dict[str, Any]:
        """
        Return properties of a media item: position, length, mute, lock, take name,
        playrate, and pitch.
        """
        try:
            return _wrap(
                adapter.get_item_properties(track_index=track_index, item_index=item_index)
            )
        except Exception as exc:
            return _err(exc)
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses what data is returned (the specific properties listed), which is helpful given no readOnlyHint exists. However, it omits error behavior (e.g., invalid indices), whether properties are returned as objects/arrays, or side effects.

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?

Single sentence, efficiently front-loaded with the action and resource. No redundant words. The colon-separated list of properties is scannable and appropriate for the context.

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?

With 2 simple integer parameters and an output schema existing, the description appropriately focuses on what properties are returned. However, the complete lack of parameter documentation (0% schema + no description coverage) leaves a gap for users unfamiliar with the indexing scheme.

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

Parameters2/5

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

Schema coverage is 0% (neither track_index nor item_index have descriptions). The description fails to compensate by explaining what these indices identify or how they relate to the 'media item' concept. The description only covers output semantics, not input parameters.

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?

Clear verb 'Return' and specific resource 'properties of a media item' with enumerated property list (position, length, mute, lock, take name, playrate, pitch). Implies distinction from sibling get_track_items by focusing on detailed properties rather than listing items, though could explicitly differentiate.

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?

No guidance on when to use this versus get_track_items or how to obtain the item_index/track_index. No mention of prerequisites or workflow context within the DAW toolset.

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

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/danielkinahan/ReaMCP'

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