# Nimbata MCP

> Nimbata lets you track which marketing campaigns generate phone calls. It provides call attribution analytics, monitoring inbound leads via dynamic number insertion. You can manage call tracking sources, retrieve granular metadata for specific calls, and list all active numbers directly through your AI client.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** call-tracking, marketing-attribution, lead-generation, dynamic-number-insertion, call-analytics, roi-tracking

## Description

Nimbata lets you manage full call tracking and attribution right through your agent. You don't wanna leave your workflow just to check leads, so we built this server for that.

### Diving Into Call Records

You can list all managed inbound calls using `list_calls`, which gives you basic metadata on everything that came in. If you need to narrow the focus, use `search_calls` to filter records based on specific criteria like date ranges or a source name. For deep background on any single conversation, call `get_call_details`. That tool pulls comprehensive info like how long the call lasted and who called it (the caller ID). If you need the actual chat recording, use `get_call_recording` to grab the URL or access key for that specific phone conversation.

### Analyzing Sources and Performance

Want to know where your money's coming from? You can check which marketing sources are running by calling `list_sources`. To get the specifics on one channel, use `get_source` to pull all the detailed info about a particular source or channel. For performance tracking, you can generate reports using `get_source_report`, which shows exactly how well a configured source performed over time. You'll also find that `get_call_report` generates a full summary report covering multiple tracked calls when you need to look at the big picture.

### Managing Assets and Numbers

You gotta keep track of your gear, right? Start by checking the connection status with `check_nimbata_status` to make sure all the data's available. To see every number currently active, run `list_numbers`. If you need details on just one specific tracking phone number—its current status and everything else—call `get_number`. 

### Creating and Tracking Sources

If your marketing needs change, you can set up a new campaign tracker using `create_source` to establish a brand-new source for proper attribution. You can also get detailed information on any existing tracking source through `get_source`, making sure all the details are right before running a campaign.

## Tools

### search_calls
Filters and searches through call records using specific criteria like date range or source name.

### check_nimbata_status
Verifies the server's current connection status to ensure data is available.

### create_source
Sets up a new marketing tracking source for campaign attribution.

### get_call_details
Pulls comprehensive metadata—like duration and caller ID—for one specific call record.

### get_call_recording
Retrieves the URL or access key for a recorded phone conversation.

### get_call_report
Generates a detailed summary report covering multiple tracked calls.

### get_number
Retrieves specific details about an active tracking phone number, including its status.

### get_source_report
Generates a performance report showing how well a configured tracking source performed over time.

### get_source
Gets detailed information for a specific marketing source or channel.

### list_calls
Lists all managed inbound calls, providing basic metadata for an overview.

### list_numbers
Provides a complete list of all currently active tracking phone numbers.

### list_sources
Lists every marketing source configured in the system.

## Prompt Examples

**Prompt:** 
```
List all tracked calls in Nimbata from today.
```

**Response:** 
```
I've retrieved your calls. You have 5 tracked activities today, including 3 from 'Google PPC' and 2 from 'Organic'. Would you like to see the duration for any of them?
```

**Prompt:** 
```
Show me the call tracking sources I have configured and their performance.
```

**Response:** 
```
You have 4 active tracking sources. "Google Ads" generated 89 calls this month (32% conversion rate), "Facebook Campaigns" had 45 calls (28% conversion), "Website Organic" tracked 67 calls (41% conversion), and "Direct Mail" logged 12 calls (50% conversion).
```

**Prompt:** 
```
Get the recording and full details for call ID call_7823.
```

**Response:** 
```
Call call_7823 details: Incoming call from +1 (555) 234-5678 on May 10th at 3:42 PM, duration 4m 32s. Source: "Google Ads Brand Campaign". The recording URL has been retrieved and is ready for playback. The caller was matched to tracking number +1 (800) 555-0199.
```

## Capabilities

### List, search, and deep dive into call records
Retrieves comprehensive lists of calls (`list_calls`), searches filtered results (`search_calls`), and pulls granular details for single calls (`get_call_details`).

### Analyze source performance and reports
Gets detailed reports on marketing sources (`get_source_report`) and lists all configured tracking channels (`list_sources`).

### Manage call assets and numbers
Lists active phone numbers (`list_numbers`), gets details for specific numbers (`get_number`), and checks the server connection status (`check_nimbata_status`).

### Create and manage tracking sources
Allows you to create new marketing tracking sources (`create_source`) or retrieve details on existing ones (`get_source`).

## Use Cases

### Auditing a poor-performing campaign source
The Marketing Manager notices Facebook leads are dipping. They prompt their agent: 'What's the performance report for Facebook Campaigns?' The agent runs `get_source_report`, showing that while call volume is high, the conversion rate dropped 15% this month.

### Investigating a mysterious inbound lead
A Sales Rep gets a hot lead but doesn't know where it came from. They ask their agent to 'Get details for call ID 9021'. The agent uses `get_call_details`, revealing the source was an obscure Direct Mail campaign, allowing the rep to adjust follow-up strategy.

### Onboarding a new ad channel
The Developer needs to track calls from a new LinkedIn Ad campaign. They use `create_source` first, giving it the unique tracking ID, then they can monitor its performance using `get_source_report` as soon as leads start rolling in.

### Quickly checking all active lines
The Ops Engineer needs to ensure no call numbers are out of service. They run `list_numbers`, verifying every assigned tracking number is marked 'active' before a major campaign launch.

## Benefits

- See exactly where leads are coming from. Instead of guessing, use `get_source_report` to quantify performance by channel (e.g., Google Ads vs. Facebook).
- Stop manual data exports. You can pull full reports using `get_call_report` directly in the chat interface—no CSV needed.
- Know your comms infrastructure instantly. Use `list_numbers` and `get_number` to check availability or details for any tracking line.
- Drill down fast on single calls. If you have a call ID, use `get_call_details` to get the source, duration, and caller ID in one command.
- Manage your setup without logging into multiple dashboards. Use `list_sources` or `create_source` directly through your AI agent.

## How It Works

The bottom line is: your AI client acts as a dedicated analyst, pulling call metadata and performance reports without you opening a single dashboard tab.

1. First, subscribe to the Nimbata server and enter your API Key into your AI client.
2. Next, prompt your agent with a specific request—like 'List all calls from Google Ads last week' or 'Get details for call ID X'.
3. The agent executes the necessary tool (e.g., `list_calls`, `search_calls`) and returns structured data directly in the chat.

## Frequently Asked Questions

**How do I check a call's source using get_call_details?**
The `get_call_details` tool provides the full metadata for any specific call ID. This includes the attributed Source field, telling you exactly which campaign or channel generated the inbound call.

**Can I list all available tracking numbers with list_numbers?**
Yes, `list_numbers` gives you a complete inventory of every active number managed by Nimbata. This is useful for audits or planning new campaigns.

**What's the difference between get_source and get_source_report?**
`get_source` pulls static details about a channel (like its name or setup date). `get_source_report`, however, gives you performance metrics—call count and conversion rates over time.

**Do I need to use search_calls for everything?**
No. Use `search_calls` when you know the criteria (like a date range or specific source). If you just want a general overview of all recent activity, `list_calls` is faster.

**How do I verify if my Nimbata connection is active using check_nimbata_status?**
It confirms your API key is valid and the server is accessible. This tool runs a simple ping test, confirming connectivity without needing any specific data parameters.

**What information does the create_source tool need to set up a new tracking source?**
It requires defining the source name, platform type (e.g., Google Ads), and associated ruleset. This function handles the backend setup for you through your natural conversation.

**Does get_call_report provide different data than just calling list_calls?**
Yes, `get_call_report` provides summarized metrics across a specified date range. It aggregates key performance indicators (KPIs) rather than simply listing individual call records.

**How do I retrieve or access the actual media files using get_call_recording?**
This tool returns a secure, temporary URL for the audio file. Your agent uses that link to download the recording data directly into your local environment for review.

**Can my AI automatically find the details for a specific call by its ID?**
Yes! Use the `get_call_details` tool with the Call ID. Your agent will respond with complete metadata for the record, including duration, caller city, and marketing source in seconds.

**How do I find my Nimbata API Key?**
Log in to your Nimbata account, navigate to **Settings** > **API**, and you will find your unique secret token there.

**Does it support tracking sources?**
Yes, use the `list_tracking_sources` tool to retrieve all your configured channels and understand where your inbound calls are coming from via the AI.