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

ghl-mcp-server-v2

by zackscriven

ghl_contact_update_task

Idempotent

Update an existing contact task by modifying optional fields such as title, body, due date, completion status, or assignee.

Instructions

REGRESSION-VERIFIED: assignedTo is present in UpdateTaskBody. Unlike create, no fields are marked required on update — all of title/body/dueDate/completed/assignedTo are optional partial updates. Update Task Endpoint: PUT /contacts/{contactId}/tasks/{taskId} (Version header: v3; source: v3/contacts-v3.json) OAuth scopes: contacts.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": {
      "contactId": "<contactId>",
      "taskId": "<taskId>",
      "body": "<body>"
    },
    "name": "ghl_contact_update_task"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateTaskBody"
  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 cover readOnly=false, idempotent=true, destructive=false, and the description adds the OAuth scope (contacts.write), the API version header, and the partial-update merge behavior — real context beyond structured fields. It stops short of describing what the response returns or what happens to unmentioned fields, but with annotations this is solid.

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?

Four lines with no filler, but the front-loaded line is internal meta-commentary ('REGRESSION-VERIFIED: assignedTo is present in UpdateTaskBody'), which is verification noise rather than the most useful fact for an agent. The actual purpose lands second, and the endpoint/scope lines are well-formatted.

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 3-param mutation with no output schema, the definition supplies method, path, version header, auth scope, and update semantics. Gaps are minor: no statement about return payload or error conditions when the task/contact pair does not exist.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description goes further by enumerating the mutable fields (title/body/dueDate/completed/assignedTo) and stating they are all optional partial updates rather than a full replacement — semantics the schema alone does not convey.

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?

The definition names the verb and resource ('Update Task') and pins the exact endpoint PUT /contacts/{contactId}/tasks/{taskId}, so the operation is unambiguous. It also explicitly contrasts itself with the create counterpart ('Unlike create...'), though it never names the sibling tool ghl_contact_create_task directly.

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?

It implies the right context — a partial update where every field is optional — and distinguishes that from create semantics. But there is no explicit when-not guidance, no mention of the adjacent ghl_contact_update_task_completed for the common 'mark done' case, and no prerequisites beyond the OAuth scope.

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