Skip to main content
Glama
Sign In
Partle

Partle

by rubenayla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_product_image

DestructiveIdempotent

Remove a specific image from a product without affecting the product itself. Use when an image was uploaded by mistake or a listing is updated.

Instructions

Remove a specific image from a product. Destructive, idempotent.

Use when an image was uploaded by mistake or the merchant updated their listing. The product itself is preserved — only the image record and its file are removed. To remove the product entirely use delete_product.

Args: api_key: Partle API key (prefix pk_). product_id: ID of the product the image belongs to. image_id: ID of the image to delete. Visible in the images array of get_product responses.

Returns: {"deleted_image": image_id} on success.

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": {
      "api_key": "<api_key>",
      "product_id": "<product_id>",
      "image_id": "<image_id>"
    },
    "name": "delete_product_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes
product_idYes
image_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent; description adds that only image record/file are removed and product is preserved, providing useful context beyond annotations.

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?

Concise and well-organized: first sentence for essence, then usage context, then structured Args/Returns sections. No superfluous text.

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?

Covers effect, use cases, parameters, and return value. For a simple destructive tool with annotations and no output schema, this is fully adequate.

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

Parameters5/5

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

With 0% schema coverage, description fully documents each parameter: api_key format, product_id role, image_id with hint to get_product response. Also specifies return format.

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?

Clearly states 'Remove a specific image from a product' and explicitly distinguishes from delete_product which removes the entire product.

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?

Provides explicit use cases: 'when an image was uploaded by mistake or the merchant updated their listing' and suggests alternative sibling tool delete_product.

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