> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwairy.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompt suggestion write tools

> Generate Prompt Studio suggestions for a workspace and accept the ones you want as monitored prompts through MCP. Accepting adds recurring credit use.

Prompt Studio proposes prompts to monitor. These tools start a generation and turn selected suggestions into prompts. Read [MCP write access](https://docs.qwairy.co/mcp/write/overview.md) first for plans, scopes, roles and confirmation tokens. Both tools require the `write:prompts` scope and the Manager role. Examples use synthetic data.

| Tool | Confirmation | REST equivalent |
| - | - | - |
| `generate_prompt_suggestions` | `never` | [`POST /brands/{brandId}/prompt-suggestions/runs`](https://docs.qwairy.co/developers/endpoints/prompt-suggestions/generate) |
| `accept_prompt_suggestions` | `always` | [`POST /brands/{brandId}/prompt-suggestions/accept`](https://docs.qwairy.co/developers/endpoints/prompt-suggestions/accept) |

Read the results with [`get_prompt_suggestions` and `get_prompt_suggestion_run`](https://docs.qwairy.co/mcp/tools/responses#get_prompt_suggestions).

## generate\_prompt\_suggestions

Start a Prompt Studio generation. A generation uses no customer credits. It is limited per workspace per day.

### Parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `brandId` | string | Yes | Workspace ID |
| `source` | string | No | `manual` or `topic` |
| `keywordId` | string | No | Topic ID. Required when `source` is `topic` |
| `refill` | boolean | No | Adds suggestions to the current pool instead of starting over |
| `requestId` | string | No | 1 to 200 characters. Reuse it for a retry; choose a new value for a new generation |
| `dryRun` | boolean | No | Validate without starting |
| `confirmationToken` | string | No | Token returned by the preview |

Within a rolling 24 hours, a workspace can start 3 workspace generations and 10 topic generations. At most one workspace generation and one generation per topic can run at a time. A call for the same running scope is refused.

Use a new `requestId` for each intentional generation, including a retry after a completed generation returned `FAILED`. Keep the same value when retrying a lost response. Without `requestId`, identical calls replay the previous result for 24 hours.

### Example

```text theme={null}
You: Suggest new prompts for the topic "CRM software".

Assistant: calls generate_prompt_suggestions with
  {"brandId": "brand_01", "source": "topic", "keywordId": "topic_01"}

Qwairy: starts the generation and returns its ID. The assistant polls
get_prompt_suggestion_run until the status is COMPLETED, then reads
get_prompt_suggestions.
```

***

## accept\_prompt\_suggestions

Create prompts from up to 20 suggestions of the latest generation. Monitored prompts add the recurring credit use shown in the preview, so every execution needs a confirmation token.

### Parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `brandId` | string | Yes | Workspace ID |
| `suggestionIds` | string\[] | Yes | 1 to 20 suggestion IDs from `get_prompt_suggestions` |
| `keywordId` | string | No | Topic for every accepted prompt. Defaults to the suggested topic |
| `tagIds` | string\[] | No | Up to 20 tag IDs applied to every accepted prompt |
| `monitoringEnabled` | boolean | No | Whether the new prompts are monitored. Defaults to `true` |
| `dryRun` | boolean | No | Preview the outcome of each suggestion and the recurring credit use |
| `confirmationToken` | string | No | Token returned by the preview |

Inspect the outcome of every suggestion. A suggestion can be created, already tracked, not found or invalid. Already tracked means that an equivalent prompt is active and monitored. IDs are opaque and bound to the suggestion content and taxonomy. Read them again after regeneration; an old ID cannot accept a different suggestion.

Acceptance uses the same import as Prompt Studio. A suggestion equivalent to an archived or paused prompt reactivates that prompt and reports `created`. Its text, funnel stage and topic are rewritten, its countries are cleared, and its personas and models return to the workspace defaults; its frequency, boost and last collection are kept.

Accepting starts no collection itself, but on a `LIVE` workspace it can make prompts due at the next scheduler pass: a new prompt when automatic answers are on, or a reactivated prompt whose last collection is older than its frequency. That first collection uses credits once, on top of the recurring use. The preview shows it in `credits.oneOff` and the recurring change in `credits.dailyChange`. Execution refuses the confirmation when either amount changed since the preview.

### Example

```text theme={null}
You: Accept the first three recommended suggestions, monitored.

Assistant: calls accept_prompt_suggestions with
  {"brandId": "brand_01", "suggestionIds": ["suggestion_01", "suggestion_02", "suggestion_03"], "monitoringEnabled": true}

Qwairy: returns a preview of the three prompts and their recurring credit use,
with a confirmationToken.

You: Confirm.

Assistant: repeats the call with the token.
```

## Related

* [Get prompt suggestions with MCP](https://docs.qwairy.co/developers/guides/prompt-suggestions-mcp.md) for the complete sequence.
* [Prompt, topic and tag write tools](https://docs.qwairy.co/mcp/write/prompts-topics-tags.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.