PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

playlist_get_selection

Read-onlyIdempotent

Read the Playlist's current time selection and project PPQ in FL Studio as raw endpoints, with validity and consistency evidence, so you can verify them before use.

Instructions

Read the Playlist's current time selection and the project PPQ.

Read-only. Returns the raw selection endpoints with validity and
consistency evidence. PPQ is ticks per quarter note; the endpoints are not
converted to bars and are not guaranteed render limits, so check the
evidence before relying on them. Use project_get_summary for the playback
position.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`warnings`	No
`end_ticks`	No
`observed_at`	Yes
`range_order`	No
`start_ticks`	No
`raw_end_time`	Yes
`timebase_ppq`	No
`raw_time_unit`	No	unknown
`duration_ticks`	No
`raw_start_time`	Yes
`schema_version`	No	1.0
`semantic_scope`	No
`selection_state`	No	unknown
`observation_atomic`	No
`project_dirty_flag`	No
`safe_for_rendering`	No
`selection_presence`	No	unknown
`raw_end_display_hint`	No
`interpretation_status`	No	unvalidated
`raw_start_display_hint`	No
`inactive_start_semantics`	No	unknown
`repeated_read_consistent`	No
`render_endpoint_inclusivity`	No	unknown

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description goes further: it warns that endpoints are raw ticks, not converted to bars, not guaranteed to be render limits, and that validity/consistency evidence should be checked before relying on them. That is substantive interpretation guidance beyond structured data.

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?

Front-loaded with the purpose, then caveats, with no wasted clauses. The standalone 'Read-only.' sentence is slightly redundant against the readOnlyHint annotation, keeping it just short of a 5.

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

Completeness5/5

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

For a zero-parameter read tool with an output schema and rich annotations, the description supplies the one thing structured fields cannot: how to interpret the returned selection endpoints. Nothing needed to call it correctly is missing.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description adds no parameter information (there is none to add) and instead explains output semantics, which is appropriate.

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?

The first sentence states a specific verb and two specific resources: the Playlist's current time selection and the project PPQ. It also implicitly separates itself from project_get_summary by reserving that tool for the playback position, so an agent can tell the two apart without opening schemas.

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 names the alternative for an adjacent need ('Use project_get_summary for the playback position'), which is real routing guidance. However, it gives no explicit when-not conditions for this tool itself, nor does it cover other selection-adjacent siblings like playlist_list_tracks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server