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

ghl-mcp-server-v2

by zackscriven

ghl_media_update_file

Rename a GoHighLevel file or folder by ID using a sub-account location token. Update media metadata without full re-upload.

Instructions

Update File/Folder Updates a single file or folder by ID Endpoint: POST /medias/{id} (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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_media_update_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the file or folder to update
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateObject"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent, open-world behavior, so the safety bar is partly covered. The description adds the concrete endpoint (POST /medias/{id}) and API version plus the token scope requirement, but never says what actually changes on the record or that repeated calls are non-idempotent in practice.

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?

Front-loaded with the action and resource, followed by endpoint metadata. The endpoint/spec-source parenthetical is somewhat operational noise but short enough to earn its place for debugging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the nested request body carries real complexity, yet the description never indicates what the update returns or that the body effectively only renames the item. Auth and endpoint are covered, but the mutation contract is thin for a nested-object write tool.

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%, so both the path id and the nested body fields (name, altType, altId) are already documented in structured form. The description only restates 'by ID' and adds no format, constraint, or mutation-scope detail beyond 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 resource ('Updates a single file or folder by ID'), and the word 'single' implicitly contrasts with ghl_media_bulk_update_files. It doesn't name that sibling explicitly, but the operation 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 by 'single file or folder' versus the bulk sibling; there is no explicit when-to-use or when-not-to-use statement. The one useful prerequisite it does give is that a Sub-Account (location) token is required.

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