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

# Your first MCP workflow

> Verify access and ask your agent for a read-only performance check.

[Connect your client](/mcp/connect), then ask your assistant to check campaign performance. This exercise reads reports without changing ads.

## 1. Choose an account

> Use Superlaunch to list the ad accounts I can access. Include their names, currencies, and time zones.

Choose an account from the result. If two accounts have the same name, ask for their IDs to identify the right one.

## 2. Ask for a report

> For this account, show daily campaign spend, impressions, and clicks for the last seven complete days. Check which metrics Superlaunch supports first. State the dates, currency, and time zone, and tell me if any results are missing.

The assistant uses `insights_capabilities` to check supported reports, then `insights_query` to read the data. If the result spans several pages, it needs to read each page before presenting a complete report.

## 3. Check the answer

Confirm that the report uses the account and dates you selected. Ask the assistant to explain any missing data or warnings before drawing conclusions.

You can follow up with:

> Which campaigns had the highest spend? Show their clicks and impressions alongside spend.

For conversion analysis, specify the event and attribution window. See [Analyze performance](/guides/insights).

## Next steps

Try a [rule, launch, or memory workflow](/mcp/workflows). Developers can use the [JSON argument examples](/mcp/examples) and [tool reference](/mcp/tools).


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