Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

audio_trigger_playlist_item

Trigger a specific audio item from a ProPresenter playlist using playlist and item IDs to control playback during presentations.

Instructions

Trigger a specific item in a specific 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>",
      "itemId": "<itemId>"
    },
    "name": "audio_trigger_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYesThe ID of the playlist
itemIdYesThe ID of the item to trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. The term 'Trigger' implies an action but does not state whether it is destructive, if it interrupts current playback, or what the return value is. This lack of transparency could lead to misuse.

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?

The description is a single sentence with no extraneous words. It is appropriately sized and front-loaded.

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 the tool's simplicity (2 params, no output schema) and absence of annotations, the description should at least mention that the playlist and item must exist. It lacks completeness for safe invocation without additional context.

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 coverage is 100% with clear descriptions for playlistId and itemId. The tool description adds no additional meaning beyond the schema. Baseline score applies.

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?

The description 'Trigger a specific item in a specific playlist' clearly states the verb 'Trigger' and the resource 'specific item in a specific playlist'. It distinguishes from sibling tools like audio_trigger_playlist (which likely triggers the entire playlist) by specifying 'item'. However, it could be more explicit about the action of 'trigger' (e.g., play, activate).

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 is provided on when to use this tool versus alternatives like audio_trigger_playlist, audio_trigger_active_playlist_item, or other 'trigger' siblings. The description does not specify any prerequisites or context.

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