---
title: "General and monitoring"
url: "https://docs.teleflows.io/guides/mcp/reference/tools/general-and-monitoring.md"
canonical_url: "https://docs.teleflows.io/guides/mcp/reference/tools/general-and-monitoring/"
last_updated: 2026-10-01
type: reference
summary: "Reference for the 4 general and monitoring tools of the Teleflows MCP server."
---

# General and monitoring

Each tool lists the inputs your assistant can send. You do not type these yourself: ask in plain language and the assistant fills them in.

## Get record by ID

Tool name: `teleflows_get_record`

Gets one record by type and ID, when you already have the ID (for example `buyer_id` or `target_id` from a call, or an ID from a list).

Ring trees and target groups include their members (ID, name, position). Campaigns, publishers, routing plans and ring tree targets have their own tools with more detail: `teleflows_get_campaign`, `teleflows_get_publisher`, `teleflows_get_routing_plan`, `teleflows_get_ring_tree_target`. A call's `target_id` can point to a target or to a ring tree target: if target returns not found, try `teleflows_get_ring_tree_target`. Ring tree members are ring tree targets; what target group members point to is not documented.

**Inputs**

| Input | Details | Description |
|---|---|---|
| `record_type` | string; required; `buyer`, `target`, `ring_tree`, `target_group`, `tracking_number`, `workflow`, `variable`, `audio_file`, `blocked_number`, `pixel`, `postback_config`, `predictive_config` | What kind of record. |
| `id` | string; required; 36 characters | A Teleflows ID (UUID). |

## Find where a record is used

Tool name: `teleflows_find_usages`

Shows where a workflow, routing plan, target, target group, ring tree or ring tree target is used: the records that reference it (for example the campaigns using a routing plan, or the routes pointing at a target).

Use it for "what breaks if I change or disable X". Route references are resolved to their routing plans by this server, because Teleflows does not return the plan. Only records your API key can access are included. Buyers, publishers, campaigns, numbers, pixels, postbacks, variables, audio files and predictive configs have no usage lookup: for a publisher's campaigns use `teleflows_list_campaigns` with `publisher_id`; for a campaign's numbers or postbacks use `teleflows_list_tracking_numbers` or `teleflows_list_postback_configs` with `campaign_id`.

**Inputs**

| Input | Details | Description |
|---|---|---|
| `record_type` | string; required; `workflow`, `routing_plan`, `target`, `target_group`, `ring_tree`, `ring_tree_target` | What kind of record. |
| `id` | string; required; 36 characters | A Teleflows ID (UUID). |
| `page` | integer; 1 to 100000; default `1` | Page number, from 1. |

## List conversion receipts

Tool name: `teleflows_list_conversion_receipts`

Lists conversion processing receipts in a time window: when each was received, its processing status, latency and test flag.

Use it to monitor whether conversions are being processed and how fast. Receipts cannot be linked to a specific call or campaign in the API. There is no status filter: count statuses in the results. The window end is sent as given; whether Teleflows includes a record at exactly that moment is not documented.

**Inputs**

| Input | Details | Description |
|---|---|---|
| `since` | string; up to 40 characters | Start of the window (inclusive): date-time with timezone, or YYYY-MM-DD meaning 00:00 UTC that day. Default: 24 hours before until. |
| `until` | string; up to 40 characters | End of the window (exclusive): date-time with timezone, or YYYY-MM-DD meaning 00:00 UTC that day, not included. Example: yesterday on 2026-10-01 is since 2026-09-30, until 2026-10-01. Default: now. At most 31 days after since; longer windows are rejected. |
| `page` | integer; 1 to 100000; default `1` | Page number, from 1. |
| `page_size` | integer; 1 to 100; default `20` | Records per page, 1-100. |

## List pixel fires

Tool name: `teleflows_list_pixel_fires`

Lists one pixel's delivery results in a time window: trigger event, status, the response code and latency from the receiving side, test flag and attempt number.

Reads saved results only: it never fires a pixel, and request contents are not available. Pixel fires cannot be linked to a specific call in the API. For all pixels, list them with `teleflows_list_pixels` and check each.

**Inputs**

| Input | Details | Description |
|---|---|---|
| `pixel_id` | string; required; 36 characters | The pixel ID (UUID). |
| `since` | string; up to 40 characters | Start of the window (inclusive): date-time with timezone, or YYYY-MM-DD meaning 00:00 UTC that day. Default: 24 hours before until. |
| `until` | string; up to 40 characters | End of the window (exclusive): date-time with timezone, or YYYY-MM-DD meaning 00:00 UTC that day, not included. Example: yesterday on 2026-10-01 is since 2026-09-30, until 2026-10-01. Default: now. At most 31 days after since; longer windows are rejected. |
| `page` | integer; 1 to 100000; default `1` | Page number, from 1. |
| `page_size` | integer; 1 to 100; default `20` | Records per page, 1-100. |
