goal

Call goal.set

Set the target this brand is aiming for on one metric — 'I want 50 leads a month', 'aim for 5 posts published a week', 'change my goal to 200 visitors a week'. A target the metric already has is replaced, and the weekly briefing measures progress against it. Call it every time a change is asked for, even when you believe that value is already in force: this tool returning is the only thing that makes it done, so never report a goal as set, or as already set, without having called it or goal.read. Not for reading the targets — that is goal.read; not for how much Goosy suggests or does on its own, such as the most posts it may propose in a week — that is workspace_autonomy.set.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/goal.set

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/goal.set
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

metric_keystring required

The metric to set a target for. Use a key from goal.read, or ask the person which metric they mean — never invent one.

targetnumber required

The target value, in the metric's own unit. Must be above 0.

period'week' | 'month' required

Whether the target is per week or per month.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.