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

# Prompt Library

> Ready-to-paste prompts for the Affiliate MCP: your performance, offers, clicks, conversions, invoices and payments.

Copy any of these into your MCP-connected AI client and replace the placeholders in brackets. Every prompt is answered by the [12 tools](/ai-automation/affiliate-mcp/tools) of the Affiliate MCP, which are read-only and return your own data.

<Note>
  Start a new session by asking the agent to call `get_account_info`. It returns your currency and your timezone, so the agent reads reports and timestamps correctly.
</Note>

***

## Performance

**Traffic by offer**

> "Run a performance report for \[FROM] to \[TO] grouped by offer. Show clicks, conversions, CVR and payout, sorted by payout, highest first."

Answered by `run_performance_report` with `dimensions=offer`.

**Which offers earn the most**

> "Which 10 offers paid me the most between \[FROM] and \[TO]? Show the payout, conversions and clicks for each."

Answered by `run_performance_report` with `sort_by=payout`. `payout` is what the network pays you.

**Day by day**

> "Show my clicks, conversions and payout day by day for \[FROM] to \[TO]."

Answered by `run_performance_report` with `dimensions=date`. A report window is at most 367 days.

**By country**

> "Break down my traffic for offer \[OFFER\_ID] by country between \[FROM] and \[TO]. Which countries convert best?"

Answered by `run_performance_report` with `dimensions=country` and a filter on the offer id.

**By sub id**

> "Group my traffic for \[FROM] to \[TO] by sub1 and show the conversions and payout for each value."

Answered by `run_performance_report` with `dimensions=sub1`. Sub ids go from `sub1` to `sub10`.

**Compare two equal windows**

> "Run one report for \[FROM\_1] to \[TO\_1] and a second for \[FROM\_2] to \[TO\_2], both grouped by offer. Put them side by side and tell me what changed in clicks, conversions, CVR and payout."

The comparison is two runs of `run_performance_report` read together. Use two windows of the same length, and compare rates when the volumes differ.

***

## Offers

**Offers I can run now**

> "List the offers I can run now with their category and my default payout."

Answered by `list_offers`. Only offers you can run now are listed, and the rows carry no tracking links.

**By category**

> "Show the offers in the \[CATEGORY] category."

Answered by `list_entities` with `type=category` for the exact names, then `list_offers` with `category`.

**By country or payout type**

> "Which of my offers run in \[COUNTRY] and pay per sale (CPS)?"

Answered by `list_offers` with `country` and `payout_type`. `payout_type` filters on the offer's default payout.

**Tracking link, caps and payout for one offer**

> "For offer \[OFFER\_ID], give me my tracking link, my payout for each event, and the caps."

Answered by `get_offer` with `include=tracking_url,payout,caps`. The tracking link appears when one is available to you, and `include=tracking_url` says so when it is not; caps appear when they are available to you.

**Targeting for one offer**

> "What traffic is allowed and excluded on offer \[OFFER\_ID]?"

Answered by `get_offer` with `include=targeting`.

***

## Clicks and conversions

**Find a click by id**

> "Look up the click with transaction id \[TRANSACTION\_ID] from \[FROM] to \[TO]. Show the offer, the timestamp, the payout and the error code if it is invalid."

Answered by `search_activity` with `type=click` and `transaction_id`. The click must fall inside the window you give, which is at most 14 days.

**Find a conversion by id**

> "Look up the conversion with id \[CONVERSION\_ID] from \[FROM] to \[TO] and show its offer, payout, event name and click timestamp."

Answered by `search_activity` with `type=conversion` and `conversion_id`.

**Recent invalid clicks and their error codes**

> "Show my invalid clicks from the last 3 days with the offer, the error code and the error message. Group them by error code."

Answered by `search_activity` with `type=click` and `status=invalid`. Only the newest 1,000 clicks of the window are reachable, so the grouping by error code covers that sample, and `truncated` tells you when the scan reached 1,000 clicks.

**Invalid clicks by one error code**

> "Which of my clicks on \[DATE] have error code \[CODE]? List the offer and the sub ids."

Answered by `search_activity` with `type=click` and `error_code`.

**Conversions in a window**

> "List my conversions from \[FROM] to \[TO] for offer \[OFFER\_ID], with the payout and the sub ids."

Answered by `search_activity` with `type=conversion`. Approved conversions are listed, newest first. Use whole days for the window.

***

## Invoices and payments

**Unpaid invoices**

> "List my unpaid invoices with the billed amount, the balance and the period of each."

Answered by `list_invoices` with `status=unpaid`. The `summary` on the first page totals billed, paid and balance for every match.

**An invoice's lines**

> "Show the line items of invoice \[INVOICE\_ID]: offers, adjustments and VAT."

Answered by `get_invoice`. Lines are paged, and items that are not itemised are summed in `other_items_total`.

**Payments for an invoice**

> "List every payment recorded against invoice \[INVOICE\_ID] with its status, type and amount."

Answered by `list_payments` with `invoice_id`. Without dates it covers all the payments of that invoice.

**Payments in a period**

> "Show the payments made to me between \[FROM] and \[TO], and add up the ones with status success."

Answered by `list_payments` with `from`, `to` and `status`. The tool returns no total, so the agent adds `amount_received` per currency across all pages. An explicit window is at most 366 days, and the default is the last 90 days.

***

## Documentation

**How to use the Affiliate API**

> "How do I get my conversions with the Affiliate API? Search the documentation and give me the endpoint and its parameters."

Answered by `search_documentation`, with `source=api_docs` for the Affiliate API and Affiliate MCP documentation only.

***

## Registered prompts

Four registered prompts carry the core steps of the four partner skills (`partner-performance-review`, `partner-offer-finder`, `partner-click-and-conversion-check` and `partner-invoice-and-payment-check`), for clients that discover prompts through the protocol but not skills. Arguments marked `*` are required; dates are `YYYY-MM-DD`.

<Note>
  The Affiliate MCP is in private beta, and so are these prompts.
</Note>

| Prompt | Arguments | What it runs |
| - | - | - |
| `partner-performance-review` | `from`*, `to`*, `dimension` (offer by default; offer, date, week, month, hour, sub1 to sub10, country, platform, device\_type, browser or source\_id) | Your traffic for the window: the dimensions from `get_report_schema`, then `run_performance_report` with the totals, the applied query and the timezone quoted |
| `partner-offer-finder` | `country`, `category`, `payout_type` (cpa, cpc, cpm, cps, cpa\_cps or prv), `offer_id` (numeric) | `list_offers` with those filters, with the exact category names from `list_entities`. With `offer_id` it adds `get_offer` for your tracking link, caps and payout |
| `partner-click-and-conversion-check` | `transaction_id` or `conversion_id` (exactly one, 32 alphanumeric characters), `from`*, `to`* | `search_activity` for that click or conversion in the window, with the click's error code and message as returned |
| `partner-invoice-and-payment-check` | `invoice_id` (numeric), `status` (paid or unpaid); give at most one | `list_invoices`, then `get_invoice` and `list_payments` for one invoice, with amounts per currency and only `success` payments counted as received |

***

## Tips

<Accordion title="Tips for better results">
  * **Read `get_account_info` first.** It gives your currency and timezone. `get_report_schema` tells you which dimensions, filters and metrics are available to you.
  * **Use `get_report_schema` before building a report.** It lists the dimensions, filters and metrics you can use, and anything else is refused.
  * **Give explicit dates** such as `2026-04-01` to `2026-04-30` rather than "last month".
  * **Mind the windows.** Reports cover at most 367 days. Click search covers at most 14 days and reaches the newest 1,000 clicks. Conversion search covers the last 365 days.
  * **Page through long lists.** While `has_more` is true, ask for the next page and the agent passes `next_cursor` back.
  * **Use ids when you have them.** An `offer_id` or an invoice id is faster and more exact than a name.
  * **Any MCP client works.** A prompt is plain language, so it runs the same in Claude, Cursor or VS Code once the server is [connected](/ai-automation/affiliate-mcp/overview).
</Accordion>


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