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

ghl-mcp-server-v2

by zackscriven

ghl_location_update_recurring_task

Idempotent

Update an existing recurring task for a GoHighLevel location by changing its schedule, title, description, assignees, contacts, or overdue-task behavior.

Instructions

Update Recurring Task Endpoint: PUT /locations/{locationId}/recurring-tasks/{id} (Version header: v3; source: v3/locations-v3.json)

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>",
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_location_update_recurring_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecurring Task Id
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / rruleOptions / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "count": {
      -        "description": "Max number of task executions",
      -        "example": 10,
      -        "type": "number"
      -      },
      -      "createTaskIfOverDue": {
      -        "description": "Create Task If Over Due",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "dayOfMonth": {
      -        "description": "1, 2, 3, ..., 27, 31",
      -        "example": 15,
      -        "type": "number"
      -      },
      -      "dayOfWeek": {
      -        "enum": [
      -          "MO",
      -          "TU",
      -          "WE",
      -          "TH",
      -          "FR",
      -          "SA",
      -          "SU"
      -        ],
      -        "example": "MO",
      -        "type": "string"
      -      },
      -      "dueAfterSeconds": {
      -        "description": "Due after seconds",
      -        "example": 23404000,
      -        "type": "number"
      -      },
      -      "endDate": {
      -        "description": "End Date",
      -        "example": "2021-09-30T00:00:00.000Z",
      -        "type": "string"
      -      },
      -      "interval": {
      -        "example": 2,
      -        "type": "number"
      -      },
      -      "intervalType": {
      -        "enum": [
      -          "yearly",
      -          "monthly",
      -          "weekly",
      -          "daily",
      -          "hourly"
      -        ],
      -        "example": "monthly",
      -        "type": "string"
      -      },
      -      "monthOfYear": {
      -        "description": "1, 2, ....., 11, 12",
      -        "example": 1,
      -        "type": "number"
      -      },
      -      "startDate": {
      -        "description": "Start Date",
      -        "example": "2021-09-30T00:00:00.000Z",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "intervalType",
      -      "interval",
      -      "startDate",
      -      "dueAfterSeconds"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "count": {
      +        "description": "Max number of task executions",
      +        "example": 10,
      +        "type": "number"
      +      },
      +      "createTaskIfOverDue": {
      +        "description": "Create Task If Over Due",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "dayOfMonth": {
      +        "description": "1, 2, 3, ..., 27, 31",
      +        "example": 15,
      +        "type": "number"
      +      },
      +      "dayOfWeek": {
      +        "enum": [
      +          "MO",
      +          "TU",
      +          "WE",
      +          "TH",
      +          "FR",
      +          "SA",
      +          "SU"
      +        ],
      +        "example": "MO",
      +        "type": "string"
      +      },
      +      "dueAfterSeconds": {
      +        "description": "Due after seconds",
      +        "example": 23404000,
      +        "type": "number"
      +      },
      +      "endDate": {
      +        "description": "End Date",
      +        "example": "2021-09-30T00:00:00.000Z",
      +        "type": "string"
      +      },
      +      "interval": {
      +        "example": 2,
      +        "type": "number"
      +      },
      +      "intervalType": {
      +        "enum": [
      +          "yearly",
      +          "monthly",
      +          "weekly",
      +          "daily",
      +          "hourly"
      +        ],
      +        "example": "monthly",
      +        "type": "string"
      +      },
      +      "monthOfYear": {
      +        "description": "1, 2, ....., 11, 12",
      +        "example": 1,
      +        "type": "number"
      +      },
      +      "startDate": {
      +        "description": "Start Date",
      +        "example": "2021-09-30T00:00:00.000Z",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "intervalType",
      +      "interval",
      +      "startDate",
      +      "dueAfterSeconds"
      +    ],
      +    "title": "CustomRRulesOptions",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"RecurringTaskUpdateDTO"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=true), so the description only needs to add operational context. It contributes the HTTP verb (PUT) and the required v3 version header, which hints at replacement semantics, but it never explains whether omitted fields are cleared, how rruleOptions interact with existing schedules, or what permissions are needed.

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?

Two short lines, front-loaded with the action and resource, with no filler. The second line is raw OpenAPI provenance metadata ('source: v3/locations-v3.json') that adds little for an agent, keeping it just short of a 5.

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

Completeness2/5

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

This is a mutation tool with a deeply nested recurrence configuration object (rruleOptions with intervalType, count, endDate, dayOfMonth, etc.) and no output schema. The description says nothing about how recurrence updates affect existing generated task instances or about partial-update behavior, leaving significant gaps for a tool of this complexity.

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 id, locationId, and every nested body field are already documented in the schema. The description adds nothing about parameter meaning, formats, or the required nested rruleOptions fields, which is the baseline-3 outcome when the schema carries the load.

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 description states a specific verb+resource ('Update Recurring Task') and the endpoint path confirms it operates on a location-scoped recurring task, which separates it from the project-scoped ghl_project_update_recurring_task. It never explicitly names the create/delete/get siblings, so differentiation is implicit rather than stated.

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 guidance on when to use this versus ghl_location_create_recurring_task, ghl_location_get_recurring_task_by_id, ghl_location_delete_recurring_task, or the project-level equivalents. The only context is the raw endpoint string, which an agent must interpret on its own.

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