build_setlist
Order a crate of 2-100 catalog tracks into a beat-matched DJ set that follows an energy arc, keeping each consecutive transition harmonically and tempo-smooth. arc is one of peak_time (default — builds to a peak then eases), warmup, cooldown, or flat. Returns the arc, count, an overall flow_score...
This record as markdown: /tools/com-freqblog-music-metadata/build-setlist.md
What build_setlist does on FreqBlog Music Metadata
AI agents call build_setlist to retrieve information from FreqBlog Music Metadata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
arc | string | — | Energy arc: 'peak_time' (default), 'warmup', 'cooldown', or 'flat'. |
track_ids | array | Yes | The crate to order — 2 to 100 catalog itunes_track_ids. |
start_track_id | object | — | Optional fixed opener — must be one of track_ids. |
Parameters from the server's own tool schema.
Why build_setlist is rated Low
The tool takes a list of track IDs and computes an optimized ordering with transition scores. It reads from the catalog and returns a structured result (ordered list, scores, omitted IDs). No data is created, modified, deleted, or executed — it is purely a read/query/computation operation against existing catalog data.
From the tool's definition Order a crate of 2-100 catalog tracks into a beat-matched DJ set... Returns the `arc`, `count`, an overall `flow_score`... the `tracks` in play order, the per-step `transitions`
Attacks that exploit this kind of access
The rule that runs build_setlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FreqBlog Music Metadata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_setlist, this is the rule to start with:
build_setlist is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FreqBlog Music Metadata, apply this rule, and every build_setlist call is checked against it from then on.
Questions about build_setlist
Order a crate of 2-100 catalog tracks into a beat-matched DJ set that follows an energy arc, keeping each consecutive transition harmonically and tempo-smooth. arc is one of peak_time (default — builds to a peak then eases), warmup, cooldown, or flat. Returns the arc, count, an overall flow_score (0-100), the tracks in play order, the per-step transitions ({from_index, to_index, score, reason}), and omitted (ids not found in the catalog). Feed tracks[].itunes_track_id into a Rekordbox/Serato export to drop the set straight into your DJ software. track_ids are catalog itunes_track_ids. Costs 5 quota units. It is categorised as a Read tool in the FreqBlog Music Metadata MCP Server, which means it retrieves data without modifying state.
build_setlist accepts 3 parameters: arc, track_ids, start_track_id. Required: track_ids. The full parameter table on this page comes from the server's own tool schema.
Register the FreqBlog Music Metadata MCP server in PolicyLayer and add a rule for build_setlist: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches FreqBlog Music Metadata. Nothing to install.
build_setlist is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the build_setlist rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for build_setlist. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
build_setlist is provided by the FreqBlog Music Metadata MCP server (https://mcp.freqblog.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FreqBlog Music Metadata, and thousands of servers like it.
This server
Across the catalogue