Skip to main content
Glama

Organize with AI (OwAI)

Resolve duplicate candidates

resolve_duplicates
Destructive

Resolve candidates exactly as the OwAI duplicate view does. The owning folder and device are derived from the selected asset IDs. Mark candidates as distinct, or move explicitly reviewed originals into the source's recoverable deletion workflow. Deletion requires a plan_id from preview_media_deletion and confirm_delete_originals=true.

Input Schema

NameRequiredDescriptionDefault
plan_idNo
asset_idsYes
operationYes
idempotency_keyNo
include_favoritesNo
confirm_delete_originalsNo

Output Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / allOf
      Added value: +[
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "delete_assets"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "properties": {
      +        "confirm_delete_originals": {
      +          "const": true
      +        }
      +      },
      +      "required": [
      +        "plan_id",
      +        "confirm_delete_originals"
      +      ]
      +    }
      +  }
      +]
    • changedInput schema / required
      Previous value: -[
      -  "operation",
      -  "asset_ids"
      -]New value: +[
      +  "asset_ids",
      +  "operation"
      +]
    • addedOutput schema / properties / command / properties / attempt / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / attempt / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / attempt / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / command / properties / claimed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / claimed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / completed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / completed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / requested_at / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / requested_at / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / requested_at / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower; the description still adds meaningful context that deletion is recoverable and requires a plan_id plus confirm_delete_originals=true. It does not disclose limits such as the 100-asset batch cap, idempotency behavior, or what happens to non-reviewed candidates in the batch.

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?

Three tight sentences with the core behavior front-loaded and the deletion prerequisites placed last where the agent needs them at call time. The opening 'exactly as the OwAI duplicate view does' spends words on an unusable reference but otherwise there is no filler.

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 destructive, plan-gated tool with an output schema present, the description covers the safety-critical path: recoverable deletion, required plan_id, and the confirm flag. Remaining gaps are the two undocumented optional parameters rather than the core invocation contract.

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 0%, so the description must carry parameter meaning; it explains operation semantics, asset_ids derivation, plan_id provenance, and the confirm flag. However idempotency_key and include_favorites are entirely unaddressed in either schema or description, leaving a real gap on a 6-parameter tool.

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?

States a specific verb (resolve) plus resource (duplicate candidates) and describes the two outcomes: marking distinct or moving originals into a recoverable deletion workflow. It also clarifies that the owning folder and device are derived from asset_ids, which usefully distinguishes it from inspection siblings. The reference to 'the OwAI duplicate view' is an opaque identifier that an agent cannot act on, keeping it short of a 5.

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?

Gives clear conditional guidance: use mark_distinct to mark distinct, or delete_assets to move reviewed originals into the recoverable deletion workflow, and names the prerequisite sibling preview_media_deletion as the source of plan_id. It does not explicitly say how this differs from inspect_duplicates or when not to use it.

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