Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official
by pedra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove object

pedra_remove_object

Remove unwanted objects from a photo using a mask image. Returns the cleaned image URL, or saves it to a Pedra property gallery when a propertyId is provided.

Instructions

Remove an object from an image using a mask. Returns the cleaned image URL. Pass propertyId to save the result into that property's gallery instead of only returning a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional name for the original photo (e.g. its file name), up to 200 characters. Only used with propertyId: if the photo isn't in that property yet, it's saved there under this name in the same call and returned as source.name. A photo already in the property keeps its name. Never shown on the image.
maskUrlYesMask image marking the region to remove: a public https:// URL, a data: URI, or a local file path.
imageUrlYesSource image: a public https:// URL, a data: URI, or an absolute path to a local image file on this computer (the file is read and inlined automatically). If the photo is on the user's device and can't be read from here (e.g. it's on their phone), get a link from pedra_create_upload_link.
propertyIdNoOptional id of the Pedra property (from pedra_list_properties) this photo belongs to. When set, the result is saved into that property's gallery — visible and editable from the app — instead of only being returned as a URL.
preserveAspectRatioNoBy default the output comes back at whatever size the AI model produces, which may not match the input's aspect ratio or resolution. Set to true to get the result at the exact width and height of the input image (center-cropped to the original aspect ratio, never stretched). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.0
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional name for the original photo (e.g. its file name), up to 200 characters. Only used with propertyId: if the photo isn't in that property yet, it's saved there under this name in the same call and returned as source.name. A photo already in the property keeps its name. Never shown on the image.",
+  "maxLength": 200,
+  "type": "string"
+}
    • addedInput schema / properties / preserveAspectRatio
      Added value: +{
+  "description": "By default the output comes back at whatever size the AI model produces, which may not match the input's aspect ratio or resolution. Set to true to get the result at the exact width and height of the input image (center-cropped to the original aspect ratio, never stretched). Defaults to false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / propertyId
      Added value: +{
+  "description": "Optional id of the Pedra property (from pedra_list_properties) this photo belongs to. When set, the result is saved into that property's gallery — visible and editable from the app — instead of only being returned as a URL.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.5.1
    • changedInput schema / properties / imageUrl / description
      Previous value: -"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file (the file is read and inlined automatically)."New value: +"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file on this computer (the file is read and inlined automatically). If the photo is on the user's device and can't be read from here (e.g. it's on their phone), get a link from pedra_create_upload_link."
  3. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / imageUrl / description
      Previous value: -"URL (or data: URL) of the source image."New value: +"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file (the file is read and inlined automatically)."
    • changedInput schema / properties / maskUrl / description
      Previous value: -"URL of the mask image marking the region to remove."New value: +"Mask image marking the region to remove: a public https:// URL, a data: URI, or a local file path."
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds meaningful context beyond them: results can either be returned as a URL or persisted into a property gallery, and gallery-saved output is "visible and editable from the app." It does not mention credit cost or whether the source image is left untouched, which keeps it short of a 5.

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?

Two sentences, zero filler, with the core action and return value front-loaded and the optional persistence behavior second. Every clause earns its place.

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?

No output schema exists, and the description covers the return value (cleaned image URL). Combined with the fully documented schema, an agent has enough to invoke it correctly; only the cost/rate-limit dimension is absent, which is minor.

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% and each parameter is already documented in the schema, so the baseline is 3. The description restates the propertyId behavior but adds no syntax or format meaning not already present in the schema fields.

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 ("Remove an object from an image") plus the required mechanism ("using a mask") and the primary outcome ("Returns the cleaned image URL"), which cleanly separates it from prompt-based siblings like pedra_edit_via_prompt or pedra_enhance.

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?

The description explains the propertyId save-vs-return choice, which is real usage guidance, but never states when to prefer this tool over alternatives such as pedra_edit_via_prompt or pedra_blur, nor any prerequisites beyond what the schema already says.

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

Deploy Server

Other Tools