Skip to content
MCP tools
Creates dataGoalsMCP tool

goals_create

Create a goal for the authenticated user.

Last updated

Create a goal for the authenticated user. Every goal needs a name (it is the heading users see), a metric, a positive target_value, and a period. The five derived metrics have their progress calculated from live CRM data; use metric="manual" for a goal whose number nobody can count for you (e.g. "get my first subscriber") — that is the only metric for which you may pass current_value. The goal is always created FOR the caller: assigning a goal to another user is a web-app action, not an MCP one. Returns the created goal.

Parameters#

ParameterTypeRequiredDescription
namestringYesName of the goal, said the way a person would say it (e.g. "Get my first user to subscribe")
metricenumYesWhat the goal counts. Use "manual" when the number is not derivable from CRM data. · One of: closings, gci, lead_conversions, appointments, listings_taken, manual
target_valuenumberYesThe number to reach (dollars for gci, a count otherwise) · Min: 0.01
period_typeenumYesHow long the goal runs · One of: weekly, monthly, quarterly, annually, custom
period_startstringYesFirst day of the goal period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD)
period_endstringYesLast day of the goal period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD)
descriptionstringNoOptional longer description (max 4000 characters)
unit_labelstringNoOptional unit shown beside the number (max 24 characters, e.g. "listings")
current_valuenumberNoStarting value. ONLY valid when metric="manual" — for every other metric the value is calculated from live data and passing it is rejected. · Min: 0
started_onstringNoThe date the goal was set (YYYY-MM-DD). Defaults to period_start. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD)

Example prompts#

  • "Set a goal of 12 closings this quarter."
  • "Make a manual goal to get my first newsletter subscriber by the end of the year."

Safety#

Creates data. Creates a new record in your CRM and may trigger notifications or webhooks. Running it twice creates a duplicate, so Claude runs it once per request.