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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_add_message_attachments

Idempotent

Sets or replaces up to five attachment URLs on an existing conversation message, separate from file upload, for custom call messages.

Instructions

Replaces/adds attachments (URLs) on an existing message — separate from POST /conversations/messages/upload, which is the file-binary upload step that produces those URLs. Add message attachments Set attachments on an existing message (replaces existing). Maximum 5 URLs. Supported for Custom Call message type. Endpoint: PUT /conversations/messages/{messageId}/attachments (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.write

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses key behavior: existing attachments are replaced, at most 5 URLs are accepted, only Custom Call messages are supported, and the conversations/message.write scope is required. It does not explain return behavior or failure cases, but the annotations and schema already cover much of the safety profile.

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?

The description is compact and front-loads the important distinction from the upload endpoint. It has some redundancy in the repeated 'Add message attachments' and 'Set attachments...' phrasing, but the endpoint, version, and scope details earn their place.

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?

Given the rich annotations, complete parameter schema, and absence of an output schema, the description supplies the key missing context: replacement semantics, the 5-URL limit, the Custom Call restriction, and the required OAuth scope. It could say more about invalid message IDs or unsupported message types, but it is sufficient for correct invocation.

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 messageId and attachments are already documented with examples. The description repeats the URL array and maximum-5 constraint already present in the schema and adds little about messageId format or body structure beyond the endpoint path.

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 verb and resource: it sets or replaces attachment URLs on an existing message. It explicitly distinguishes this from the binary upload endpoint that produces those URLs, and it names the endpoint and OAuth scope.

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 clearly separates this operation from POST /conversations/messages/upload and explains that upload is the file-binary step. It also states the maximum of 5 URLs and that this is supported only for the Custom Call message type, though it does not name the sibling tool directly.

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