Skip to main content
Glama
Sign In

Popcraft

by io.github.popcraft-ai
OverviewDiscussionsAdmin

Popcraft Effects Gallery

popcraft_effects_show
Read-only

Browse Popcraft's curated video effects (特效) — cinematic camera moves, VFX, and viral looks, each defined by a reference video + recipe prompt — plus the user's own saved effects. Returns effect ids, names, categories, preview videos, and the full recipe. TO APPLY AN EFFECT: call popcraft_generate_video with model = the effect's default_model_id, a medias entry {value: reference_video_url, role: "video"}, and a prompt that combines the effect's prompt with the user's subject (add the user's start image as role "start_image" or "image" if they provided one). Optionally filter by category or a query substring match on the name.

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": "popcraft_effects_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive substring match against effect names (English + Chinese)
categoryNoFilter to one category, e.g. "action", "fpv", "vfx"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable context beyond that — the exact return fields and the downstream apply workflow — but says nothing about pagination, result limits, or rate behavior.

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-loads purpose, then the apply workflow, then optional filters. Slightly long but each sentence (purpose, returns, application mapping, filters) earns its place with no redundancy.

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?

With no output schema, the description compensates by enumerating return fields and fully explaining the downstream application path. Nothing an agent needs to browse and then apply an effect is missing.

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 coverage is 100%, so both parameters (query, category) are already documented in the schema. The description restates the filtering behavior without adding syntax or format detail beyond what the schema provides, so the baseline 3 is appropriate.

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 (Browse) and resource (Popcraft's curated video effects), enumerates what the effects contain (reference video + recipe prompt) and what the tool returns (ids, names, categories, previews, recipe). Clearly distinguishable from siblings like popcraft_show_elements or popcraft_models_explore.

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?

Explicitly routes the agent: to apply an effect it names the sibling popcraft_generate_video and spells out the exact model/medias/prompt mapping. It also states the optional filtering conditions (category or query substring), leaving little to inference.

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

All Popcraft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources