Skip to main content
Glama

Zapmatte Green Screen Remover MCP

get_removal_status

Idempotent

Check your own job. Poll no faster than every 5 seconds. On success returns outputs (URLs of the ProRes MOV, WebM, matte, preview and, for colour backgrounds, MP4) and the result page; failed jobs are refunded automatically. Requires a key.

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": {
      "taskId": "<taskId>"
    },
    "name": "get_removal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations it discloses a rate limit, an auth requirement ("Requires a key"), a refund-on-failure guarantee, and the exact set of outputs returned on success. That is substantial behavioral context an agent cannot get from the structured fields. It does not explain the in-progress/pending response shape, and "Check" sits a little awkwardly against readOnlyHint=false without explanation, but nothing is contradicted.

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?

Five short clauses, front-loaded with the action and the polling constraint, with no filler. "Check your own job" is slightly elliptical, but every sentence contributes a constraint, guarantee, or return detail.

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?

For a single-parameter status tool with no output schema, the description covers safety-adjacent facts (rate limit, refunds, auth) and enumerates return values. The remaining gap is mostly the intermediate/pending state and taskId provenance, which is minor relative to complexity.

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

Parameters2/5

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

With only one required parameter at 0% schema description coverage, the description carries the full burden, and it only implies ownership scoping via "your own job". It never says what taskId is, its format, or where it comes from (presumably the removal submission), so an agent must infer the linkage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Check your own job" states a verb (check) and a resource (job status), and the later sentence clarifies that the job is a green-screen/removal job producing MOV/WebM/matte outputs. It is distinguishable from siblings like remove_green_screen or estimate_removal_cost, though the noun "job" is only made concrete by the output list rather than stated up front.

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

Usage Guidelines3/5

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

It gives a concrete polling cadence ("Poll no faster than every 5 seconds") and a scoping rule ("your own job"), which is real operational guidance. However, it never states when to call this versus waiting, nor how to obtain the taskId used to call it, and names no alternative tool.

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