Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playlists_trigger_item

Trigger a specific item in a ProPresenter playlist by specifying its playlist ID and index number to control presentation flow during live events.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
playlistIdYesThe ID of the playlist
indexYesThe item index to trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior1/5

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

With no annotations provided, the description should disclose behavioral traits like whether the trigger is destructive, idempotent, or requires permissions. It simply says 'trigger' without any detail, leaving the agent uninformed about side effects or return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (5 words) and to the point, but it lacks substantive information that would help the agent. It is not verbose, but it does not earn its place by adding value beyond restating the tool name.

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 presence of many sibling tools with similar purposes, the description is insufficient. It does not explain the tool's role in the playlist ecosystem, nor does it cover usage guidelines or behavioral aspects, leaving the agent without sufficient context to correctly invoke it.

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 description coverage is 100% and the input schema already clearly describes both parameters (playlistId and index). The description does not add any extra meaning or context beyond what the schema provides, meeting the baseline expectation.

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 clearly states the action (trigger) and the resource (a specific item in a playlist), but it does not differentiate from sibling tools like playlists_trigger_focused_item or playlists_trigger_active_presentation_item. A more specific description indicating selection by index would improve clarity.

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?

The description provides no guidance on when to use this tool versus alternatives, such as playlists_trigger or other item-specific triggers. It lacks any explanation of context or prerequisites.

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