Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-12USmethodology registry-public-v1
Searchable tools
113,018
Authless tools
7,424
Auth required
100,766
Described tools
61,167
113,018 tools
- List operating systemslist · Retrieves operating systems.VoluumVoluum
PluginrequiredMarketing - List regionslist · Retrieves regions.VoluumVoluumPluginrequiredMarketing
- List report columnslist · Lists all available columns and their metadata.
Returns metadata for all available report columns including their key (API name),
human-readable label, data type, and capabilities.
## Purpose
This is the **runtime discovery mechanism** for building valid report queries.
Call this endpoint at startup to discover:
- All valid **groupBy** dimensions — filter the response for canGroupBy: true.
- All valid **column** (metric) values — filter for canGroupBy: false.
- Human-readable **display labels** for column headers.
- Column **data types** for correct formatting.
## Bootstrap sequence
For AI/programmatic consumers, the recommended startup sequence is:
1. Authenticate (POST /auth/access/session)
2. Call `list_columns` — discover valid groupBy values and built-in columns
3. Call `list_custom_conversions` — discover account-specific conversion types
4. Call `list_custom_columns` — discover user-defined derived metrics
5. Call `list_traffic_sources` — discover custom variable name mappings per source
6. Now you can build valid report queries with complete column sets.
## Response fields per column
- **key**: the column name to use in the 'column' and 'groupBy' query parameters.
- **label**: human-readable display name.
- **type**: data type (string, number, decimal, monetary, percentage, date_time, boolean).
- **canGroupBy**: if true, this column can be used as a groupBy dimension.
- **canBeRestricted**: if true, this column can be used in filter conditions.VoluumVoluumPluginrequiredMarketing
- List scheduled reportslist · Lists scheduled reportsVoluumVoluumPluginrequiredMarketing
- List shared reportslist · List shared reportsVoluumVoluumPluginrequiredMarketing
- List tagslist · Retrieves all tags for a given clientId and entityType starting with tagPrefix.VoluumVoluumPluginrequiredMarketing
- List time zoneslist · Retrieves timezones.VoluumVoluumPluginrequiredMarketing
- List traffic source integrationslist · List all configured traffic source integrations for the account, including their type, transfer status, account name, and settingsVoluumVoluumPluginrequiredMarketing
- List traffic source templateslist · Retrieves traffic source templates, optionally filtered and paged.
Filter and page **server-side** rather than fetching the whole collection and filtering locally.
Filters combine with AND, and each filter parameter's own description states whether it matches
exactly or as a case-insensitive substring. Filters are applied before paging, so a page contains
only entities matching the filters.
Send *limit* to page; without it this endpoint returns the whole matching collection - but the MCP
list_ tools default *limit* to 100, so through them a bare call is one page, not the complete
collection.
Paging is by cursor, not by position: a response that has more to give carries *nextId*, and you get
the following page by sending it back as the *nextId* parameter with the **same filters**. When
*nextId* is absent the collection is exhausted - there is no need for a further request to discover
that, and no total count to compare against. Do not construct a cursor yourself; ids are opaque here.
Freshness (*If-Modified-Since*) is judged over every entity of this type, not over the filtered page:
a change that moves an entity out of your filter, or onto a page you are not reading, still answers 200.
So the header combines with both filtering and paging, at the cost of the occasional 200 for a view that
did not itself change.VoluumVoluumPluginrequiredMarketing
- List traffic sourceslist · Returns all traffic sources with their configuration.
Returns the list of traffic sources configured in the account, including their
custom variable name mappings, postback URLs, and cost tracking settings.
Filter and page **server-side** rather than fetching the whole collection and filtering locally.
Filters combine with AND, and each filter parameter's own description states whether it matches
exactly or as a case-insensitive substring. Filters are applied before paging, so a page contains
only entities matching the filters.
Send *limit* to page; without it this endpoint returns the whole matching collection - but the MCP
list_ tools default *limit* to 100, so through them a bare call is one page, not the complete
collection.
Paging is by cursor, not by position: a response that has more to give carries *nextId*, and you get
the following page by sending it back as the *nextId* parameter with the **same filters**. When
*nextId* is absent the collection is exhausted - there is no need for a further request to discover
that, and no total count to compare against. Do not construct a cursor yourself; ids are opaque here.
Freshness (*If-Modified-Since*) is judged over every entity of this type, not over the filtered page:
a change that moves an entity out of your filter, or onto a page you are not reading, still answers 200.
So the header combines with both filtering and paging, at the cost of the occasional 200 for a view that
did not itself change.
## Custom variable names
Each traffic source defines customVariable1Name through customVariable10Name,
which give meaning to the customVariable1-10 dimensions in reports.
The same index can mean completely different things on different traffic sources
(e.g. customVariable1 might be "Site ID" on one source and "Keyword" on another).
Read the variable name mappings from this endpoint before interpreting
groupBy=customVariable{N} report data. Cache the result — it rarely changes.
## Other fields relevant to report analysis
- postbackUrl — the URL used to fire conversions back to the traffic source
- costVariable — if present, the source passes cost data automaticallyVoluumVoluumPluginrequiredMarketing
- Mark notification as readmark · Mark a notification as read. Updates the read timestamp, indicating the user explicitly opened the notificationVoluumVoluumPluginrequiredMarketing
- Mark notification as seenmark · Mark a notification as seen. Updates the seen timestamp, indicating the user's client displayed the notificationVoluumVoluumPluginrequiredMarketing
- Mark notification as unreadmark · Mark a notification as unread, clearing its read timestampVoluumVoluumPluginrequiredMarketing
- Mark notifications as readmark · Mark all notifications as read, or a specific set if request body with UUID list is providedVoluumVoluumPluginrequiredMarketing
- Mark notifications as seenmark · Mark all notifications as seen by setting the seen timestamp on items that have not been seen yetVoluumVoluumPluginrequiredMarketing
- Mark notifications as unreadmark · Bulk mark multiple notifications as unread by providing their ids This tool takes a request body: you MUST call get_schema("mark_notifications_unread") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move affiliate networks to workspacemove · Changes workspace for affiliate networks. This tool takes a request body: you MUST call get_schema("move_affiliate_networks_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move campaigns to workspacemove · Changes workspace for campaigns. This tool takes a request body: you MUST call get_schema("move_campaigns_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move flows to workspacemove · Changes workspace for flows. This tool takes a request body: you MUST call get_schema("move_flows_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move landers to workspacemove · Changes workspace for landers. This tool takes a request body: you MUST call get_schema("move_landers_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move offers to workspacemove · Changes workspace for offers. This tool takes a request body: you MUST call get_schema("move_offers_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Move traffic sources to workspacemove · Changes workspace for traffic sources. This tool takes a request body: you MUST call get_schema("move_traffic_sources_to_workspace") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Pause campaign dimension valuepause · Pause a specific dimension value (keyword, zone, target, etc.) within a campaign in the traffic sourceVoluumVoluumPluginrequiredMarketing
- Pause campaign dimension valuespause · Pause multiple dimension values (keywords, zones, targets) at once within a campaign This tool takes a request body: you MUST call get_schema("pause_campaign_dimensions") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Pause campaign in traffic sourcepause · Pause a campaign in the traffic source via the Automizer integration. The campaign will stop receiving trafficVoluumVoluumPluginrequiredMarketing
- Pause traffic source integrationpause · Pause an integration by setting all its data transfers to PAUSED statusVoluumVoluumPluginrequiredMarketing
- Prepare a test conversion postbackprepare · Composes the postback URL that fires a test conversion for a click id obtained with prepare_test_visit. The server performs no external request: fetch the URL yourself, or hand it to the user. Verify with run_dryrun_report.VoluumVoluumPluginrequiredMarketing
- Prepare a test visitprepare · Opens a campaign test session and returns the URL to visit to register a test visit, with step-by-step instructions for reading the click id out of the redirect and, on a lander funnel, for clicking through the lander. The server performs no external request: visit the URL yourself, or hand it to the user — a browser runs this test best. Follow up with prepare_test_conversion.VoluumVoluumPluginrequiredMarketing
- Read knowledge base articleread · Returns the body of one knowledge-base article (JSON: id, modified, truncated, content) for an id obtained from search_docs. Content is HTML with images/scripts/styles removed. Long articles are capped by default: truncated=true means the content field holds only the beginning of the article. The cap is generous and usually contains the answer — only re-call with full=true when what you needed was not in the returned portion; do not refetch reflexively.VoluumVoluumPluginrequiredMarketing
- Register device push tokenregister · Register a device for push notifications by storing its FCM token and setting up default notification preferencesVoluumVoluumPluginrequiredMarketing
- Register notification deviceregister · Register a device with extended info (OS, browser, device type) and store its FCM token for push notifications This tool takes a request body: you MUST call get_schema("register_notification_device") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Replace custom conversionsreplace · Replaces the entire custom conversion configuration list This tool takes a request body: you MUST call get_schema("replace_custom_conversions") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Request traffic log exportcreate · Emails a traffic-log report for the specified campaign and date range to one or more recipients.
Submits an asynchronous Traffic Log request: Voluum generates a log of the campaign's raw traffic over the given period and emails it to the addresses in 'emails'. Sends mail to caller-supplied addresses, so confirm the recipients with the user before calling. Returns the request id immediately — the report is not ready yet; poll `get_traffic_log` for its status and download link.VoluumVoluumPluginrequiredMarketing
- Reset campaign budget in traffic sourcereset · Send a reset campaign budget command to the traffic sourceVoluumVoluumPluginrequiredMarketing
- Reset campaign daily budget in traffic sourcereset · Send a reset daily budget command to the traffic source for a campaignVoluumVoluumPluginrequiredMarketing
- Restore affiliate networksrestore · Restores affiliate network(s). This tool takes a request body: you MUST call get_schema("restore_affiliate_networks") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Restore campaign in traffic sourcerestore · Restore a previously deleted campaign in the traffic source via the Automizer integrationVoluumVoluumPluginrequiredMarketing
- Restore campaignsrestore · Restores campaign(s). This tool takes a request body: you MUST call get_schema("restore_campaigns") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Restore flowsrestore · Restores flow(s). This tool takes a request body: you MUST call get_schema("restore_flows") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Restore landersrestore · Restores lander(s). This tool takes a request body: you MUST call get_schema("restore_landers") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Restore offersrestore · Restores offer(s). This tool takes a request body: you MUST call get_schema("restore_offers") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Restore traffic sourcesrestore · Restores traffic source(s). This tool takes a request body: you MUST call get_schema("restore_traffic_sources") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Resume campaign dimension valueresume · Resume a paused dimension value (keyword, zone, target, etc.) within a campaign in the traffic sourceVoluumVoluumPluginrequiredMarketing
- Resume campaign dimension valuesresume · Resume multiple paused dimension values (keywords, zones, targets) at once within a campaign This tool takes a request body: you MUST call get_schema("resume_campaign_dimensions") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
- Resume campaign in traffic sourceresume · Resume a paused campaign in the traffic source via the Automizer integration, restarting traffic deliveryVoluumVoluumPluginrequiredMarketing
- Resume traffic source integrationresume · Resume a paused integration by setting all its data transfers back to ACTIVE statusVoluumVoluumPluginrequiredMarketing
- Run dry-run reportrun · Returns dry run report for testing campaign configuration. Examples available — call get_examples("run_dryrun_report") for sample request + response.VoluumVoluumPluginrequiredMarketing
- Run reportrun · Returns aggregated report grouped by the specified dimension(s).
Returns aggregated performance data grouped by the specified dimension(s).
This is the primary reporting endpoint for campaign analytics.
## Prerequisites
Before building report queries, call these endpoints to discover account-specific configuration:
- **`list_columns`** — returns all valid groupBy dimensions (canGroupBy: true) and metric
columns with their display labels and types.
- **`list_custom_conversions`** — returns custom conversion type definitions
(index 1-20 mapping to customConversions{N} and customRevenue{N} columns).
- **`list_custom_columns`** — returns user-defined derived metric names that can be passed as
column values alongside built-in metrics.
- **`list_traffic_sources`** — returns each source's *customVariables[]* array, where every entry
carries *index*, *name* (user-facing label) and *parameter* (the URL parameter the source sends
on the click). Variable meanings are defined per traffic source — the same slot index can mean
different things on different sources.
## Key behaviors
- **Date range is half-open [from, to)**: the 'to' date is exclusive.
To query March 5 in full, set from=2026-03-05T00:00:00Z and to=2026-03-06T00:00:00Z.
- **Name columns must be requested explicitly**: groupBy=campaignId only returns campaignId.
Add campaignName to the column list to get human-readable names.
- **Column is a repeated parameter**: use column=visits&column=clicks, not column=visits,clicks.
- **Drilldown filters**: use filter1=campaignId&filter1Value=<id> to filter results.
Multiple filters: filter1/filter1Value, filter2/filter2Value, etc.
## Metric formulas
- **CTR** = clicks / visits (lander effectiveness)
- **CR** = conversions / clicks (offer quality)
- **CV** = conversions / visits (end-to-end funnel efficiency)
- **ROI** = (revenue - cost) / cost (expressed as percentage, e.g. 125.0 = 125%)
- **CPA** = cost / conversions
- **EPV** = revenue / visits
- **EPC** = revenue / clicks
- **CPV** = cost / visits
## Direct-linking campaigns
Campaigns without a lander (direct-linking) never record click events.
CTR, CR, clicks, and EPC are always zero — this is expected, not a tracking error.
Use CV (conversions/visits) and EPV (revenue/visits) instead.
Detection: inspect the campaign's flow for lander presence (`get_campaign` or run
groupBy=landerId filtered to the campaign — if no landers appear, it is direct-linking.
## This endpoint vs /report/conversions
This endpoint returns aggregated data grouped by dimensions.
For individual conversion events (no grouping), use `list_conversions` instead —
that endpoint does not accept groupBy, conversionTimeMode, or include parameters.
## Rate limits and response size
Throttling applies at three levels:
**Per Bearer token (per user)** — three independent buckets:
| Bucket | Base allocation | Notes |
|---|---|---|
| Per-second (burst) | **~4 req/s** | Hit first by most clients |
| Concurrent in-flight | **~30** | Counted while a request is on the wire |
| Per-minute (sustained) | Higher; rarely the binding cap | Only hit if you sustain perfectly even pacing |
Base allocation only — many accounts have higher negotiated limits.
Contact support for your values.
**Per IP** — anti-abuse cap; authenticated clients from a single host
should not normally hit it.
**Per-user utilization budget (reports only)** — independent of request
count. Heavier queries (longer date ranges, wider *groupBy*, more *column*
values) cost more; light queries cost little. Often the binding cap on
heavy analytics workloads — prefer many narrow queries over a few enormous
ones if you see 429s without exceeding the per-second cap.
Exceeding any of these returns **429 Too Many Requests** with an empty
body and no *Retry-After* header. Back off and retry.
Per-request row cap: see the *limit* query parameter.
Per-account caps and throttling thresholds are configurable; contact support to raise them.
Examples available — call get_examples("run_report") for sample request + response. Guide available — call get_guide("run_report") for usage guidance.VoluumVoluumPluginrequiredMarketing
- Run time-aggregated reportrun · Returns report data aggregated by time unit.
Returns performance metrics aggregated by the specified time unit (day, hour, month, etc.).
The response is a map of timestamps to metric values, useful for time-series analysis
and trend visualization.
## Date range
Same half-open [from, to) semantics as `run_report` — the 'to' date is exclusive.
## Use cases
- Daily performance trends (unit=DAY)
- Hourly granularity for dayparting analysis (unit=HOUR)
- Day-of-week patterns for bid scheduling (unit=DAY_OF_WEEK)
- Hour-of-day patterns for dayparting (unit=HOUR_OF_DAY)VoluumVoluumPluginrequiredMarketing
- Schedule recurring conversions report emailschedule · Submits a scheduled conversion report request and returns empty response. Reports will arrive via emailVoluumVoluumPluginrequiredMarketing
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.