Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playlists_create_under

Create a new playlist within an existing playlist structure in ProPresenter. Specify parent playlist ID, name, and type to organize content hierarchically.

Instructions

Create a new playlist under an existing playlist

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlistId": "<playlistId>",
      "name": "<name>",
      "type": "<type>"
    },
    "name": "playlists_create_under"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYesThe parent playlist ID
nameYesThe name of the new playlist
typeYesThe type of playlist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided; description only states basic purpose without disclosing side effects (e.g., whether it affects the active playlist, permissions needed, or return behavior), which is insufficient for a create operation.

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?

Extremely concise (one sentence), no redundant words, but lacks structural elements like bullet points or sections that could improve readability. However, for its brevity, it earns a 4.

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

Completeness2/5

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

Given no output schema, extensive sibling tools, and three required parameters, the description is too brief. It does not clarify the result (e.g., returns new playlist details) or constraints, leaving the agent with insufficient contextual information.

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 has 100% coverage with descriptions for each parameter. The description adds minimal semantic value ('under an existing playlist') that contextualizes playlistId but does not enhance understanding of other parameters beyond the schema. Baseline 3 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?

Clearly states the specific action (create) and resource (playlist), and distinguishes from sibling tools like playlists_create by specifying 'under an existing playlist', indicating it creates a sub-playlist.

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 tool versus alternatives (e.g., playlists_create for top-level playlists), no prerequisites or context, leaving the agent to infer usage.

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