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

# All tools

> The complete list of tools the Cello MCP server exposes

The Cello MCP server exposes the tools below. Which ones are available depends on your Cello role. See the [Developers](/mcp/developers/use-cases) and [Growth Managers](/mcp/growth/use-cases) sections for use cases and example prompts.

<Note>
  All Cello MCP tools are currently read-only. To make changes, the assistant points you to the relevant page in the [Cello Portal](https://portal.cello.so).
</Note>

## Overview

| Tool                                                            | Purpose                                              | Typically used by |
| --------------------------------------------------------------- | ---------------------------------------------------- | ----------------- |
| [`cello_get_program_metrics`](#cello_get_program_metrics)       | Program metrics, trends, and benchmarks in one call  | Growth            |
| [`cello_get_referrers`](#cello_get_referrers)                   | Find and sort referrers by engagement or performance | Growth            |
| [`cello_get_top_referrers`](#cello_get_top_referrers)           | Top referrers by net new ARR                         | Growth            |
| [`cello_get_integration_status`](#cello_get_integration_status) | Health of the four integration components            | Developer         |
| [`cello_get_events`](#cello_get_events)                         | Latest events feed with per-field validation         | Developer         |
| [`cello_get_recommendations`](#cello_get_recommendations)       | Prioritized best-practice recommendations            | Both              |
| [`search_cello`](#search_cello)                                 | Search the Cello knowledge base                      | Both              |
| [`query_docs_filesystem_cello`](#query_docs_filesystem_cello)   | Read full doc pages and OpenAPI specs                | Both              |

## Program & analytics

### cello\_get\_program\_metrics

Complete referral program metrics in a single call.

* **Returns**: lifetime cumulative totals (referrer funnel and new-user funnel, plus ARR) with pre-calculated monthly and weekly trends; weekly and monthly history time series; and industry benchmarks segmented by GTM motion (Free Trial, Freemium, Demo Only, or Overall). Benchmarks cover Active Rate, Sharing Rate, Signup Rate, and Unique Views per Share, each with a median (50th pct) and best-in-class (75th pct) line. Sharing rate uses a banded benchmark adjusted for your active rate so you're compared against true peers.
* **Use for**: questions about program performance, stats, trends, revenue, funnel metrics, or industry comparisons.

See also: [Program Performance](/guides/attribution/program-performance), [Benchmarks](/guides/attribution/benchmarks)

### cello\_get\_referrers

Find referrers, optionally filtered and sorted by engagement or performance metrics.

* **Parameters**: `filter` (matches ucc, email, product user id, or referrer id), `page` (1-indexed, 10 per page), `sort` (defaults to net new ARR; also revenue, signups, purchases, unique views, and recent activity).
* **Returns**: up to 10 referrers per page with their metrics, plus the total match count. Best presented as a table.

### cello\_get\_top\_referrers

The top-performing referrers, sorted by net new ARR (descending).

* **Parameters**: `page` (1-indexed, 10 per page).
* **Returns**: up to 10 referrers per page with their metrics, plus the total count.

## Integration health

### cello\_get\_integration\_status

Checks whether all four integration components are working: the referral widget, the attribution widget, signup tracking, and purchase tracking.

* **Returns**: per-component `connectionStatus` (`connected`, `connectedWithWarnings`, or `notConnected`), an optional `warningType`, and a `lastEventReceived` timestamp. Includes signup source, purchase source, and any widget errors.

See also: [Integration Status](/guides/support/portal/integration-status)

### cello\_get\_events

Recent webhook and API events Cello received from your payment provider or direct API integration.

* **Returns**: recent events (newest first) with source, overall validation status, timestamp, and a payload breakdown of key fields (ucc, productUserId, email, customerId), each with its own validation status.
* **Use for**: verifying events are received and diagnosing missing or malformed fields that block attribution.

See also: [Event Feed](/guides/support/portal/event-feed)

## Optimization & documentation

### cello\_get\_recommendations

A prioritized list of best-practice recommendations for improving your referral program, grouped by activation, sharing, and conversion.

* **Returns**: recommendations with completed/pending status, effort and impact labels, actionable links, and a top-priority callout.

See also: [Performance Recommendations](/guides/attribution/recommendations)

### search\_cello

Search the Cello knowledge base for documentation, code examples, API references, and guides.

* **Returns**: contextual content with titles and direct links to the relevant documentation pages.

### query\_docs\_filesystem\_cello

A read-only query interface over an in-memory filesystem containing the Cello documentation pages and OpenAPI specs.

* **Use for**: reading the full content of a specific doc page by path, exact keyword or regex search, and exploring the docs structure. Complements `search_cello`, which is better for broad or conceptual queries.