Skip to main content
Glama

Zapmatte Green Screen Remover

remove_green_screen

Destructive

Start a paid green screen removal with user approval and an exact expectedCredits quote. Needs uploadKey from create_upload (after the PUT). Required requestId deduplicates identical retries for 24h; never use a new id to retry an uncertain submission. Returns taskId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>",
      "durationSeconds": "<durationSeconds>",
      "requestId": "<requestId>",
      "uploadKey": "<uploadKey>",
      "expectedCredits": "<expectedCredits>"
    },
    "name": "remove_green_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesQuality id from list_removal_options: "standard" or "fine".
requestIdYesUnique submission id, e.g. a UUID. Reuse for identical retries within 24 hours; never change after an uncertain outcome.
uploadKeyYeskey returned by create_upload, after the video file was PUT to its putUrl.
backgroundNoTransparent (ProRes, WebM, matte) or a solid colour (adds an MP4).
durationSecondsYesLength of the video in seconds (decimals allowed).
expectedCreditsYesExact cost from estimate_removal_cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the operation is paid, requires user approval, requires an exact cost quote, and that requestId deduplicates identical retries for 24 hours. That retry/dedup contract is the critical behavioral fact for a destructive, non-idempotent submission and it is not derivable from destructiveHint/openWorldHint.

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?

Four tight sentences with zero filler. The paid/approval constraint is front-loaded, prerequisites follow, and the retry rule and return value close it out in the order an agent needs them.

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 destructive, paid, multi-step operation with a nested background object and no output schema, the description covers cost, approval, key provenance, dedup window, and the returned taskId. Nothing essential for a correct first call 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% and the parameter descriptions already spell out uploadKey provenance and requestId reuse rules, so the description largely restates them. It adds only the framing that expectedCredits must be an exact quote and that approval is required before calling; useful, but marginal against a fully documented schema.

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?

Uses a specific verb ('Start') and resource ('green screen removal') and immediately qualifies the operation as paid and approval-gated, which separates it from estimate_removal_cost and get_removal_status. The closing 'Returns taskId' tells the agent what it gets back.

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?

Clearly states prerequisites: uploadKey comes from create_upload after the PUT, and expectedCredits must be an exact quote (schema names estimate_removal_cost as the source). The retry rule ('never use a new id to retry an uncertain submission') is explicit. It stops short of naming when to prefer a sibling instead, but the sequencing constraints effectively route the agent.

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