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

ghl-mcp-server-v2

by zackscriven

ghl_contact_update_task_completed

Idempotent

Marks a contact task as completed or incomplete by updating its completion status using a specific contact ID and task ID.

Instructions

Update Task Completed Endpoint: PUT /contacts/{contactId}/tasks/{taskId}/completed (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_completed"
  }
}

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: +"UpdateTaskStatusParams"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds useful non-annotation context—the OAuth scope contacts.write and API version header—but says nothing about side effects (notifications, timestamps) or what happens when a task is already completed.

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?

Three compact lines with no filler; the endpoint and auth metadata are front-loaded. The only redundancy is the opening line duplicating the tool name.

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?

For a mutation endpoint with a nested body, the description provides endpoint, version, and auth scope, and annotations cover safety/idempotency. It still omits expected side effects and return behavior (there is no output schema), leaving the agent to guess what completing a task triggers.

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 contactId, taskId, and the body.completed boolean are fully documented in the schema itself. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 heading 'Update Task Completed' largely restates the tool name, but the endpoint line (PUT /contacts/{contactId}/tasks/{taskId}/completed) makes the specific operation—marking a contact's task as completed—unambiguous. It does not explicitly contrast with the sibling ghl_contact_update_task, so it is clear but not differentiated.

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 tool versus ghl_contact_update_task or ghl_contact_create_task. The agent must infer from the endpoint path that this is the dedicated completion-status toggle; no exclusions or prerequisites are given.

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