---
title: "Call funnel.plan"
method: POST
path: "/api/v1/tools/funnel.plan"
tags: ["funnel"]
---

# Call funnel.plan

`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

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.

## Headers

- `x-request-id` string

## Request body

- object
  - `answers` object, required
    - `offer` string, required: What they are selling, in their own words. Ask for this first — everything else follows from it.
    - `audience` string, required: Who the offer is for.
    - `entry_point` string, required: Where the traffic comes from — ads, organic, cold email, referral. If they have not said, state the default and move on.
    - `conversion_event` string, required: The one thing that counts as a conversion — a booked call, a purchase, a form fill.
    - `follow_up_window` string, required: How long the follow-up runs, e.g. 14 days. Default it and say so rather than asking a fifth question they do not care about.
  - `parts` string[], 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.
  - `defaulted` string[]: 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.
  - `workspace` string: 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 `200`

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.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `plan_markdown` string, required
    - `project_name` string, required
    - `ordered_parts` object[], required
      - `key` string, required
      - `label` string, required
      - `depends_on` string[], required
    - `missing_dependencies` string[], required
    - `answer_note` string, required
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)