Skip to main content
Glama
yshk-mrt

Presentation Buddy MCP Server

by yshk-mrt

SetMediaTime

Control media playback by setting specific start times in milliseconds. Jump to scenes or set replay positions for media sources during streaming presentations.

Instructions

Sets the current playback time of a media source. 用途: 特定シーンへのジャンプ、リプレイの開始位置設定

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The handler logic for the 'SetMediaTime' tool. It extracts sourceName and mediaTime from parameters, calls the OBS WebSocket method 'SetMediaInputCursor' via sendToObs, and returns success or error structured content.
    case "SetMediaTime":
        const timeParams = params as { sourceName: string; mediaTime: number };
        console.log(`Executing SetMediaTime with params:`, timeParams);
        try {
            await sendToObs("SetMediaInputCursor", { inputName: timeParams.sourceName, mediaCursor: timeParams.mediaTime }, context, action.name);
            return { structuredContent: { success: true } };
        } catch (e: any) {
            console.error(`Error in SetMediaTime for OBS:`, e.message);
            return { structuredContent: { success: false, error: e.message } };
        }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Sets'), suggesting potential side effects, but doesn't disclose behavioral traits such as required permissions, error handling (e.g., invalid time values), or effects on playback state. The examples hint at use cases but don't clarify operational limits or safety, leaving gaps in transparency.

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 brief with two sentences, but the second sentence mixes languages and adds minimal value, slightly reducing clarity. It's front-loaded with the core purpose, yet the non-English text may hinder comprehension. Overall, it's concise but could be more structured and focused.

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 annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances like whether the change is immediate or requires playback state. For a mutation tool with complex parameters, this leaves significant gaps in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'media source' and 'playback time' but doesn't add meaning beyond the schema's property names (sourceName, mediaTime). No details on valid ranges, units beyond milliseconds, or sourceName constraints are provided, failing to enhance parameter understanding.

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 verb ('Sets') and resource ('current playback time of a media source'), making the purpose evident. It distinguishes from siblings like PlayPauseMedia or StartRecording by focusing on time positioning rather than playback control or recording. However, it doesn't explicitly differentiate from tools like SwitchScene or SetSourcePosition, which might also involve media manipulation.

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 minimal usage guidance with examples ('特定シーンへのジャンプ、リプレイの開始位置設定'), but these are vague and not in English, reducing clarity. It lacks explicit when-to-use rules, prerequisites (e.g., media must be loaded), or alternatives among siblings like PlayPauseMedia for playback control, offering no structured guidance for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yshk-mrt/obs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server