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

ghl-mcp-server-v2

by zackscriven

ghl_association_update

Idempotent

Updates the labels of an existing association by ID, letting you correct or rename its first and second object labels when relationship terms change.

Instructions

Update Association By Id Update Association , Allows you to update labels of an associations. Documentation Link - https://doc.clickup.com/8631005/d/h/87cpx-293776/cd0f4122abc04d3 Endpoint: PUT /associations/{associationId} (Version header: v3; source: v3/associations-v3.json) OAuth scopes: associations.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": {
      "associationId": "<associationId>",
      "body": "<body>"
    },
    "name": "ghl_association_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / firstObjectLabel / description
      Added value: +"First Object's Association Label, e.g. 'student'. (Spec bug override 2026-08-27: empty object schema in upstream spec despite being required — the tool was uncallable.)"
    • removedInput schema / properties / body / properties / firstObjectLabel / example
      Removed value: -"student"
    • changedInput schema / properties / body / properties / firstObjectLabel / type
      Previous value: -"object"New value: +"string"
    • addedInput schema / properties / body / properties / secondObjectLabel / description
      Added value: +"Second Object's Association Label, e.g. 'tutor'. (Spec bug override 2026-08-27: empty object schema in upstream spec.)"
    • removedInput schema / properties / body / properties / secondObjectLabel / example
      Removed value: -"tutor"
    • changedInput schema / properties / body / properties / secondObjectLabel / type
      Previous value: -"object"New value: +"string"
    • addedInput schema / properties / body / title
      Added value: +"UpdateAssociationReqDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description's burden is lower. It still adds real value: the write is limited to labels (other association properties are untouched), it requires the associations.write OAuth scope, and it pins the v3 API version via a required header. It does not say what happens on a nonexistent ID or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two lines are near-duplicates ('Update Association By Id' then 'Update Association, Allows you to update labels'), which is wasted space, and the wording is slightly ungrammatical. The metadata lines (doc link, endpoint, scope) are dense and useful, and the key scope constraint appears early.

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 two-parameter mutation with no output schema and no annotations gap to fill, the description covers the endpoint, version header, auth scope, and the fact that only labels change. The notable omission is any explanation of associationId or error/return behavior, plus a missing prerequisite that the association must already exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the two nested body labels have descriptions, but associationId is a bare string with no description anywhere. The description mentions 'By Id' without saying where that ID comes from (e.g., from ghl_association_list or ghl_association_get_by_key_name) or its format. It fails to compensate for the coverage gap.

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 (update an association by ID) and narrows the scope to labels, which meaningfully distinguishes it from sibling operations like ghl_association_create, ghl_association_delete, and ghl_association_get_by_id. It never names those siblings explicitly, so it falls short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus ghl_association_create, ghl_association_delete_relation, or the several association getters. The only directional content is the endpoint and OAuth scope, which explain the mechanics but not the selection criteria. The agent must infer that an existing association ID is a precondition.

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