Multimodal AI
Object Eraser & Image Object Removal API MCP
Remove selected objects or regions using a mask image. Built for product listings, ads and storefronts. Available via REST API or MCP.
Object Eraser & Image Object Removal API AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Remove A Selected Object
Prompt: Remove the object marked by [mask image] from [base image], keeping the surrounding scene coherent.
What You Need to Provide
Provide assets you may use and that meet this tool’s documented file, dimension and count limits.
A pending task is not a completed image, video or text result. Retrieve the existing task rather than submitting a duplicate.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_object_eraser_image_object_removalhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "object-eraser-image-object-removal-1",
"method": "tools/call",
"params": {
"name": "nexscope_object_eraser_image_object_removal",
"arguments": {
"imageUrl": "https://example.com/product.jpg",
"maskImageUrl": "https://example.com/mask.png"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Asynchronous task workflow
- 1. Create once
Keep the returned taskId.
- 2. Query with backoff
Use nexscope_media_task_result after 5 seconds, then 10, 20, and 30 seconds.
- 3. Use final result
Stop at success, failure, or timeout.
{
"jsonrpc": "2.0",
"id": "object-eraser-image-object-removal-result-1",
"method": "tools/call",
"params": {
"name": "nexscope_media_task_result",
"arguments": {
"skillSlug": "object-eraser-image-object-removal",
"taskId": "TASK_ID_FROM_THE_GENERATION_RESULT"
}
}
}Arguments
| Name | Type | Required | Description |
|---|---|---|---|
imageUrl | string | required | Public URL of the base image. The image must be between 300 and 4096 pixels in both width and height, and its width-to-height ratio must be between 0.4 and 2.5. Example: https://example.com/product.jpg |
maskImageUrl | string | required | Public URL of the mask image for the area to erase. Example: https://example.com/mask.png |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | required | Data value used by this API operation. |
msg | string | null | required | Msg value used by this API operation. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | required | Trace id value used by this API operation. |
ts | string | required | Epoch milliseconds. |
Any of option 1 — requires taskId, status, result
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.result | any | required | Completed generation output retained from the task result. Fields vary by capability; generated resources use Nexscope-hosted URLs and any count represents charged Nexscope credits. This is the business output, not a task creation receipt. |
data.status | string | required | Status value used by this API operation. Allowed: PENDING, RUNNING, SUCCEEDED, FAILED, TIMEOUT |
data.taskId | string | required | Task id value used by this API operation. |
Any of option 1
| Name | Type | Required | Description |
|---|---|---|---|
data.result | object | required | Completed generation output retained from the task result. Fields vary by capability; generated resources use Nexscope-hosted URLs and any count represents charged Nexscope credits. This is the business output, not a task creation receipt. |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data.result | null | required | Completed generation output retained from the task result. Fields vary by capability; generated resources use Nexscope-hosted URLs and any count represents charged Nexscope credits. This is the business output, not a task creation receipt. |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Remove the object marked by [mask image] from [base image], keeping the surrounding scene coherent.
Illustrative Response Explanation
The illustrative request has been accepted as task example-task and is PENDING. No completed output is available yet. Keep this task ID and check its result; do not submit the same request again just because processing has not finished.
About this sample: Illustrative format example with fictional values, not a live tool call. Replace example inputs with your own permitted assets or public identifiers.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Illustrative example with fictional data, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "object-eraser-image-object-removal-example",
"method": "tools/call",
"params": {
"name": "nexscope_object_eraser_image_object_removal",
"arguments": {
"imageUrl": "https://example.com/product.jpg",
"maskImageUrl": "https://example.com/mask.png"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "object-eraser-image-object-removal-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"cost\":\"-1\",\"data\":{\"taskId\":\"example-task\",\"status\":\"PENDING\",\"result\":null},\"msg\":null,\"time\":\"2026-01-01 00:00:00\",\"traceId\":null,\"ts\":\"0\"}"
}
],
"structuredContent": {
"code": 0,
"cost": "-1",
"data": {
"taskId": "example-task",
"status": "PENDING",
"result": null
},
"msg": null,
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "0"
},
"isError": false
}
}