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

ghl-mcp-server-v2

by zackscriven

ghl_location_create_recurring_task

Creates a recurring task for a location with a title, schedule rules, assigned owners or contacts, and optional start/end limits. Use it to automate repeated task creation via the GoHighLevel API.

Instructions

Create Recurring Task Endpoint: POST /locations/{locationId}/recurring-tasks (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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_location_create_recurring_task"
  }
}

Input Schema

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

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

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-idempotent write. The description adds only endpoint/version metadata and says nothing about how the recurrence schedule takes effect, whether the initial task is created, or what happens on repeated calls.

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 compact lines with the action front-loaded and the endpoint metadata second. No filler, though the version/source parenthetical has little value for an agent choosing a tool.

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?

For a mutation tool with a nested recurrence-rule body, no output schema and partial schema coverage, the description should explain required location context and how the recurrence fields combine. Instead it stops at the endpoint, leaving the hardest part of the call undocumented.

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 only 50% and the description supplies no parameter meaning at all. The schema documents most body fields, but locationId, interval and dayOfWeek are undocumented, and the rruleOptions semantics (intervalType + interval + startDate interaction) are left entirely to inference.

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 gives a specific verb+resource ('Create Recurring Task') plus the exact endpoint, POST /locations/{locationId}/recurring-tasks, so the agent knows it is a location-scoped recurring task creation. It doesn't distinguish itself from close siblings like ghl_location_update_recurring_task or ghl_project_create_recurring_task, but the verb and scope are unambiguous.

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?

Usage is only implied by the name and endpoint path: create a recurring task at a location, rather than update/delete it. There is no explicit statement of prerequisites (locationId source, task owner/contact requirements) or when to prefer a sibling such as ghl_contact_create_task for a one-off task.

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