Skip to main content
Glama

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

List effect templates

pixverse_list_effects
Read-onlyIdempotent

PixVerse's effect templates (more than 900) for pixverse_create_video's template_id: template_id, display_name, effect_type (how many input images), template_type (1 video, 2 image), the template's model, qualities, duration and example_text. search filters by name or prompt; a page at a time (offset, limit). GET /videos/effects.

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_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.
limitNoItems per page (default 50).
offsetNoWhere the page starts (default 0): the next_offset of the previous page.
searchNoWords to find in the template's name or prompt (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive operation, so the safety profile is covered. The description adds real context beyond that: the corpus size (900+ templates), page-at-a-time retrieval via offset/limit, and semantics of the returned fields such as effect_type meaning the number of input images and template_type encoding 1=video / 2=image. It does not mention total result counts or ordering, a minor omission.

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

Conciseness4/5

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

Front-loaded with the resource and its purpose, followed by return-field semantics and then pagination. The middle field enumeration is dense but every item earns its place by describing an undocumented return value. No filler sentences.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the returned fields (template_id, display_name, effect_type, template_type, model, qualities, duration, example_text) and the pagination model. The multi-account email requirement is left entirely to the schema, and result totals are unaddressed, but for a read-only list tool this is close to complete.

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%, so search, offset and limit are already fully documented in the schema, including the next_offset pagination idiom and the email requirement. The description restates search-by-name-or-prompt and pagination without adding syntax, format, or constraint detail beyond that. Baseline 3 applies where the schema does the heavy lifting.

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?

States a specific verb and resource (listing PixVerse effect templates, 900+ of them) and ties the resource to a concrete consumer: the template_id of pixverse_create_video. An agent can tell immediately what it gets and why, and distinguish it from the other list_* siblings.

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

Usage Guidelines4/5

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

The phrase "for pixverse_create_video's template_id" gives a clear usage trigger: call this before creating a template-driven video. It also explains that search narrows by name or prompt and that results come a page at a time. There is no explicit when-not or named alternative, which keeps it just short of a 5.

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