funnel

Call funnel.status

How far along a funnel is — 'how far along is our funnel?', 'has the funnel been tested?' — which parts have passed a test lead, which have not, and whether the whole funnel has been proven end to end. A part that has not passed reads unverified; never call one done on its behalf. Not for running a test lead through it — that is funnel.test_part or funnel.test_end_to_end.

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.status

Request

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

project_board_idstring uuid

The funnel's project id, if you have one from something you were shown. If you do not, use funnel_name instead — do not guess a uuid.

funnel_namestring

What the member calls the funnel, when you do not have its id. It is matched against their own projects only.

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.