Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_media_bulk_delete_files

Idempotent

Bulk soft-delete or trash multiple media files and folders in a single request by specifying location details and a deleted or trashed status.

Instructions

Bulk Delete / Trash Files/Folders Soft-deletes or trashes multiple files and folders in a single request Endpoint: PUT /medias/delete-files (Version header: v3; source: v3/medias-v3.json) Requires a Sub-Account (location) token.

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": {
      "body": "<body>"
    },
    "name": "ghl_media_bulk_delete_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / filesToBeDeleted / items / title
      Added value: +"DeleteMediaObjectItem"
    • addedInput schema / properties / body / title
      Added value: +"DeleteMediaObjectsBodyParams"
  2. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare mutation, idempotency, and non-destructive behavior, while the description adds the important nuance that this is a soft-delete or trash operation and requires a Sub-Account token. It does not describe the response or restoration behavior, but it adds meaningful context beyond the 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?

The description is front-loaded and compact: title, core behavior, endpoint/version, and auth requirement are all stated in four short lines. Every line contributes useful information without unnecessary prose.

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 nested-body mutation tool with complete schema documentation and existing annotations, the description provides sufficient operational context: soft-delete/trash semantics, bulk scope, endpoint, and token requirement. The main minor gap is that the return/response behavior is not described.

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 the nested body fields are fully documented in the schema. The description reinforces that multiple files/folders are affected and mentions the location token requirement, but does not add parameter-level syntax or constraints beyond the schema.

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?

The description states a specific bulk operation: soft-delete or trash multiple files and folders in one request. The word 'Bulk' and phrase 'multiple files and folders' clearly distinguish it from the single-file sibling ghl_media_delete_file.

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?

It gives clear usage context by specifying that this is for multiple files and folders in a single request. It does not explicitly name the single-file alternative or state exclusions, but the bulk scope makes the intended use clear.

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