> ## 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

> A few starter prompts for ad-hoc queries against the Everflow MCP Server. For repeatable workflows, use Agent Skills.

Copy any of these into your MCP-connected AI client for quick, one-off questions — just replace the placeholders in brackets.

<Note>
  **For repeatable workflows, use [Agent Skills](/ai-automation/mcp/skills) instead.** Skills auto-activate and carry the judgment for a whole task — period reviews, tracking-link retrieval, conversion scrubbing, and more — without copy-pasting prompts. The starter prompts below are best for ad-hoc, exploratory queries; for end-to-end tool traces, see [Agentic Examples](/ai-automation/mcp/examples).
</Note>

<Accordion title="Tips for better results">
  * **Be specific about date ranges.** The agent performs better with explicit dates (`2026-04-01` to `2026-04-30`) than relative terms like "last month."
  * **Ask for one thing at a time** in complex investigations. Multi-step workflows are more reliable when each step is confirmed before the next.
  * **Use IDs when you have them.** Filtering by `offer_id` or `affiliate_id` is faster and more accurate than filtering by name.
  * **Specify currency and timezone** if your network has non-USD defaults or you're comparing across regions.
  * **Paginate explicitly** for large datasets. Ask the agent to "get the next page" or set `page_size` in your prompt when working through long lists.
</Accordion>

<Note>
  Start every new session with `get_account_info` or ask the agent to call it automatically. This confirms your default currency and timezone, which affects how reports and timestamps are interpreted.
</Note>

***

## Starter prompts

**Confirm your session context**

> "Call get\_account\_info and summarize my network name, default timezone, default currency, and whether I have limited affiliate scope."

**Performance snapshot**

> "Give me a performance summary for yesterday — total clicks, conversions, revenue, payout, and profit — in my network's default timezone."

**Top offers this month**

> "What are my top 10 offers by revenue this month? Show name, clicks, conversions, CVR, revenue, and profit, sorted by revenue descending."

**Compare this week to last week**

> "Compare this week's performance to last week across clicks, conversions, revenue, and profit. What changed significantly?"

**Biggest movers by offer**

> "Which offers had the biggest change in EPC this week vs last week? Rank by the EPC delta and show each offer's current vs prior value."

**Diagnose a click or conversion**

> "Look up transaction ID \[TRANSACTION\_ID] — offer, affiliate, timestamp, unique flag, the error code and its meaning, and whether it converted." *(or: "Look up conversion \[CONVERSION\_ID] — offer, affiliate, advertiser, payout, status, error code, click timestamp, and sub/adv parameters.")*

**Why are clicks invalid / conversions rejected**

> "Run a performance report for affiliate \[AFFILIATE\_ID] between \[FROM] and \[TO] with dimensions=click\_error\_code (or conversion\_error\_code). Show each reason and its count, sorted descending. Ignore error code 0."

**Unpaid invoices for an affiliate**

> "List all invoices for affiliate \[AFFILIATE\_ID] with status unpaid. Show billed amount, the period, and whether it's payable."

<Note>
  The invoice entity type requires an `affiliate_id` filter — a network-wide invoice list is not supported. To find affiliates with outstanding invoices, run `list_affiliates` first, then query invoices per affiliate.
</Note>

***

## Registered prompt resources (legacy)

<Warning>
  **Superseded by [Agent Skills](/ai-automation/mcp/skills).** The MCP Server historically registered a few named prompts — `troubleshoot-click`, `partner-health-check`, `revenue-analysis`, and `offer-launch-readiness` — invokable by name via the [MCP `prompts/get` method](https://modelcontextprotocol.io/docs/concepts/prompts). Skills now cover these same workflows with auto-activation and richer judgment, so the registered prompts are retained **only for backward compatibility** with clients that have a native prompt browser. They are not recommended for new integrations and may be removed in a future release — use [Skills](/ai-automation/mcp/skills) or the starter prompts above.
</Warning>