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

# Availability, limits, and unsupported operations

> Build around the capabilities exposed by your connected environment. A supported request can still return unavailable data when the selected run or linked account does not contain what it needs.

Build around the capabilities exposed by your connected environment. A supported request can still return unavailable data when the selected run or linked account does not contain what it needs.

## Reading versus changing data

The 43 external MCP tools in this edition support measurement reads, discovery, and analysis planning. They do not create projects, add prompts, launch runs, change content recommendations, edit Content Playground drafts, or publish a website. Agent Q and the product interface can expose additional workflows.

`analytics_mode` returns an analysis plan for a requested report. It is not a new measurement run, a file-export endpoint, or a background report scheduler. Use it when the user explicitly requests that report workflow.

## Common result limits

| Operation | Limit or selection |
| - | - |
| Mention statement page | 1–100 rows; default 25. |
| Statement or response text | 50–2000 characters; default 500. |
| Query lookup | 1–200 rows; default 50; no cursor. |
| Placement target page | 1–200 URLs; default 20. |
| Sources per brand in source comparison | 1–200; MCP default 10. |
| Time-series selection | 1–200 series; default 6 for metric/trend, 10 for movers. |
| Movers per direction | 1–20; default 5. |
| GA4 snapshot history selection | 1–24; default 6. |

Result-size limits are not account rate limits, subscription entitlements, or a promise that that many rows exist. No verified commercial request quota or uptime promise is established by this documentation edition.

## Features that need more context

Google tools need linked and successfully synchronized data. Page-content tools need captured page content for section-level analysis. Change reports need comparable completed runs. Persona reports need an actually measured persona or query set; a requested perspective does not retroactively add it to historical data.

There is no customer webhook contract, project-write API, public service-account grant, or standalone IQRush SDK documented here. Use the supported read interfaces and your own scheduler for approved reporting needs. Recheck the runtime catalog when a later release adds capabilities.


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