funnel

Call funnel.plan

Write the plan for a funnel — 'plan a funnel for our webinar', 'what would a lead funnel for this offer need?' — what it needs, in what order, where the operator decides, and how each part will be proven. Ask the few questions that matter first (the offer, who it is for, where the traffic comes from, what counts as a conversion, how long the follow-up runs), state a default rather than asking a fifth time, and stop when you have enough. It creates NOTHING: the plan is text they read and change before anything is built. Not for creating the funnel's project once they agree — that is funnel.scaffold.

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/funnel.plan

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/funnel.plan
  • 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

partsstring[] required

Which parts this funnel needs. Choose from the closed list — you cannot invent one. A funnel with a page and a sequence is a real funnel; do not add parts nobody asked for.

defaultedstring[]

Which of the five answers YOU supplied rather than the operator. The plan marks each one so they can see what they never actually decided. Leave it out when they answered everything.

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 4 revisions of this API.