---
title: "Find the right Adako tool for a job"
method: POST
path: "/api/v1/tools/search_tools/execute"
tags: ["Adako"]
---

# Find the right Adako tool for a job

`POST /api/v1/tools/search_tools/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/search_tools/execute`
- Auth: HTTP bearer

Finds the tools that do a job, ranked, from the user's own wording. Free and instant.
Use when: you are not sure which tool to call, the user asked for something you have not seen a tool for, or a tool name you guessed came back unknown. Searching costs nothing — guessing costs a failed call.
When not to use: you already know the tool name (call it, or call get_tool_schema for its arguments).
Returns: up to top_k rows with the tool name, what it does, its risk and cost, its arguments (required ones marked) and the exact "How to call" line — most tools are reached through their platform router, so follow that line as written. For flat arguments that is enough to make the call; get_tool_schema adds descriptions and nested fields. A request to delete campaigns, ad groups, ad sets or ads also gets a note first: no tool does that, and what to offer instead.
Searches every platform unless you pass platform. If nothing matches, say so and ask the user what they want to achieve; do not invent a tool name.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `query` string, required: What the user wants to do, in their own words ("stop wasting money on bad search terms").
    - `platform` 'google_ads' | 'meta_ads' | 'chatgpt_ads' | 'tiktok_ads' | 'linkedin_ads' | 'system': Restrict to one platform. Leave empty to search all of them.
    - `top_k` integer: How many tools to return. Default 5.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)
