media-jobs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MJM_SERVICE_TOKEN | Yes | Service token used by the MCP server; must match the value configured in .env. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_job_statusB | Current status and retry round of a job, e.g. job_code="MJ-0001". |
| list_job_errorsB | Most recent pipeline errors of a job, newest first. Sensitive values are redacted. |
| search_runbooksB | Search operational runbooks. Cite results by their |
| submit_jobB | Register a job. Idempotent per source_id: repeating the call never creates duplicates. |
| retry_jobA | Move a failed job back to pending. Pass a unique idempotency_key per intended retry. |
| probe_mediaA | Technical specs (codec, resolution, fps, duration, bitrate, audio) of a media file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_job | Guided triage of one job. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: job status, error listing, submission, retry, runbook search, and media probing. There is no meaningful overlap between job lifecycle tools, diagnostics, documentation search, and media inspection.
All names are snake_case and follow a verb-first convention (get_, search_, list_, submit_, retry_, probe_). The pattern is predictable throughout the set.
Six tools are well-scoped for a media job management server, covering submission, retry, status, errors, docs, and media probing without bloat. Each tool appears to earn its place.
The core lifecycle is covered: submit, check status, inspect errors, retry, search runbooks, and probe media specs. Minor gaps such as cancellation or job listing exist but are not fatal for the apparent purpose.