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

# Call ads.suggest_competitors

`POST /api/v1/tools/ads.suggest_competitors`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/ads.suggest_competitors`
- Auth: HTTP bearer

Suggest a few competitors worth tracking — 'who are our competitors', 'suggest some competitors to watch'. Offer TWO OR THREE competitors — never six — for the operator to confirm, guessed from what you know of their brand and site. This does NOT start tracking them and does NOT look anything up: each one is recorded as a candidate waiting for the operator's yes. Give a short honest reason per name; they read it before confirming. Once they confirm, use ads.research_pull to see what that competitor is running. Not for looking up what a named competitor is running — that is `ads.research_pull`.

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
  - `candidates` object[], required: Two or three names, never more. Guess from what you know of this brand and its site.
    - `name` string, required: The competitor's brand name, as a person would say it.
    - `platform` 'meta' | 'google' | 'linkedin' | 'tiktok', required: Where you would look them up first.
    - `reason` string, required: One short line on why you think they are a competitor. The operator reads this before confirming.
  - `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
    - `candidates` object[], required
      - `id` string, required
      - `name` string, required
      - `platform` 'meta' | 'google' | 'linkedin' | 'tiktok', required
      - `reason` string, required
      - `confirmed` false, required
    - `already_tracked` object[], required
      - `name` string, required
      - `platform` 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`.

## Changes

- **2026-10-19** `d59cf9dfc713`: 2 warning, 2 info
  - added the new `linkedin` enum value to the `oneOf[subschema #1]/candidates/items/platform` response property for the response status `200`
  - added the new `tiktok` enum value to the `oneOf[subschema #1]/candidates/items/platform` response property for the response status `200`
  - added the new `linkedin` enum value to the request property `candidates/items/platform`
  - added the new `tiktok` enum value to the request property `candidates/items/platform`

[Operation history](https://skmtc.dev/goosybear/apis/goosy-bear-api/changes/api/v1/tools/ads.suggest_competitors/post.md)

---

[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)