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

# Call ads.research_pull

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

## Request

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

See what one competitor is running as ads, longest-running first — 'what ads is our competitor running?', 'what ads is HubSpot running', 'pull up their Facebook ads', 'what are they running on Google?', 'show me their LinkedIn ads', 'what ads are they running on TikTok?'. It looks the competitor up by name in the Meta, Google, LinkedIn or TikTok ad library (the platform the member names; Meta when they name none) and returns their three longest runners: the hook, the format, how long each has run (or the date it was first seen; LinkedIn's library states neither) and a link to it in the library — the ads they keep paying for are the ones working. Each run's ad_id is what `ads.pick_reference` takes when the member wants one as a reference. This charges the workspace one lookup; a competitor pulled in the last 30 days answers from what we already have and costs nothing unless refresh is set. The ads' pictures are never stored: send the member to each run's link to see one. Not for suggesting which competitors to watch — that is `ads.suggest_competitors`. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

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
  - `competitor` string, required: The competitor, in the operator's own words — a brand name. A platform-native page id or advertiser id also works when they have one.
  - `platform` 'meta' | 'google' | 'linkedin' | 'tiktok', required: Which ad library to look in.
  - `limit` integer: How many of their longest-running ads to keep. Defaults to three, which is what the card shows.
  - `refresh` boolean: Look them up again even though we already have a recent pull saved. This SPENDS a lookup; leave it off unless the operator asked for fresh numbers.
  - `confirmation_id` string, uuid: Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.
  - `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
    - `state` 'confirmation_required'
    - `confirmation_id` string, uuid
    - `expires_in_seconds` integer
    - `request_summary` string: What will happen, in one sentence, for a person to approve before confirming.
    - `advertiser_name` string
    - `platform` 'meta' | 'google' | 'linkedin' | 'tiktok'
    - `runs` object[]
      - `ad_id` string, required
      - `advertiser_name` string, required
      - `hook` string, required
      - `format` 'image' | 'video', required
      - `ran_days` integer, nullable, required
      - `first_seen_at` string, nullable, required
      - `details_url` string, nullable, required
    - `from_memory` boolean
    - `pulled_at` string
    - `read` string
    - `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]/platform` response property for the response status `200`
  - added the new `tiktok` enum value to the `oneOf[subschema #1]/platform` response property for the response status `200`
  - added the new `linkedin` enum value to the request property `platform`
  - added the new `tiktok` enum value to the request property `platform`

[Operation history](https://skmtc.dev/goosybear/apis/goosy-bear-api/changes/api/v1/tools/ads.research_pull/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)