Skip to main content
Glama

PixVerse MCP Server by useapi.net (third-party)

List running jobs and free slots

pixverse_list_running_jobs
Read-onlyIdempotent

The videos, images, music and speech the API is tracking now (id, type, started, elapsed) and, per account, maxJobs with its running and free slots. The first check when a create tool answers 429 (accounts at maxJobs); jobs started on pixverse.ai or in Off-Peak mode are not tracked (pixverse_list_videos shows them). GET /scheduler/available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pixverse_list_running_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the tracking caveat: only API-scheduled jobs are listed, and off-peak/pixverse.ai jobs are invisible here. That is exactly the kind of blind spot an agent would otherwise misread. It stops short of describing response ordering or what happens when the job list is empty.

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?

Two sentences, front-loaded with what is returned, then the operational trigger and the caveat. No filler; each clause carries new information. The first sentence is telegraphic but still parses.

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

Completeness5/5

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

For a zero-parameter read tool with no output schema, the description supplies the return fields, the per-account capacity figures, the usage trigger and the scope limitation. Nothing an agent needs to call it correctly or interpret the result is missing.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter meaning to add; the baseline for a zero-param tool applies. The description instead spends its words on the response shape, which is the sensible trade.

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?

The description names the specific resource (jobs the API is currently tracking across video, image, music and speech) and states the returned fields (id, type, started, elapsed), plus the per-account maxJobs/running/free-slot data. It also explicitly demarcates itself from pixverse_list_videos, so an agent can pick the right tool without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger condition: 'The first check when a create tool answers 429 (accounts at maxJobs)'. It also states the exclusion — jobs started on pixverse.ai or in Off-Peak mode are not tracked — and redirects to pixverse_list_videos for those, which is a genuine when-not/alternative pair.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources