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

ghl-mcp-server-v2

by zackscriven

ghl_media_bulk_update_files

Idempotent

Update metadata or status for multiple GoHighLevel media files and folders in one request, including renaming items by ID.

Instructions

Bulk Update Files/Folders Updates metadata or status of multiple files and folders Endpoint: PUT /medias/update-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_update_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 / filesToBeUpdated / items / title
      Added value: +"UpdateMediaObject"
    • addedInput schema / properties / body / title
      Added value: +"UpdateMediaObjects"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real value beyond that: the exact endpoint (PUT /medias/update-files), API version v3, the OpenAPI source file, and the required Sub-Account token. It stops short of describing partial-failure behavior or max items per call.

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?

Four short lines, front-loaded with the action and scope, followed by the endpoint and the auth caveat. No filler; the only minor inefficiency is the redundant title-style heading repeating the tool name.

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 single-parameter, nested-body mutation with no output schema, the description supplies the auth model and endpoint context an agent needs to call it. The one gap is the 'status' claim, which is not representable in the schema (only id and name are updatable), and no return-value expectation is set.

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%, with altId, altType, filesToBeUpdated and nested id/name all documented inline, so the baseline of 3 applies. The description adds no syntax or constraint detail beyond the schema, and its mention of 'status' is not a settable field in the schema.

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 and scope ('Bulk Update Files/Folders', 'Updates metadata or status of multiple files and folders'), which distinguishes it from the single-file ghl_media_update_file sibling by the word 'bulk'. It does not name the sibling explicitly, but the plural/bulk framing is unambiguous.

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?

Usage is only implied: 'bulk' signals use when updating many objects rather than calling ghl_media_update_file repeatedly, and the description notes the Sub-Account (location) token prerequisite. There is no explicit when-not guidance, no mention of batch-size limits, and no stated alternative for single-file updates.

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