Metadata MCP Connector

Get Performance Metrics

performance_metrics

Read-only

Read paginated performance metrics for ads, audiences, creatives, offers, target groups, or keywords. The endpoint argument selects the report and dates use ISO 8601. Returns one page of metrics and available pagination metadata, with at most 100 rows.

Input Schema

Name	Required	Description
`ids`	No	Set of IDs to filter by
`page`	No	Page number to retrieve (0-based indexing)
`size`	No	Results per page from 1 to 100; default 100. Use successive zero-based page values and response pagination metadata for more results.
`sort`	No	Sorting criteria (e.g., 'spent,desc', 'cpl,asc', 'experimentId,spent,desc')
`tags`	No	Set of tag IDs to filter by
`goals`	No	Filter by campaign goals
`adName`	No	Filter by specific ad name
`maxCpl`	No	Maximum cost per lead threshold
`minCpl`	No	Minimum cost per lead threshold
`endDate`	No	endDate in ISO 8601 format (YYYY-MM-DDThh:mm:ssZ), e.g., `startDate=2025-06-12T14:30:00.123Z`).
`keyword`	No	Filter by specific keyword
`channels`	No	Filter by marketing channels
`endpoint`	No	Specific endpoint to query. If not specified, will be auto-determined from query context. Use 'customAudience/group' for target groups.
`maxLeads`	No	Maximum number of leads threshold
`maxSpend`	No	Maximum spend threshold
`minLeads`	No	Minimum number of leads threshold
`minSpend`	No	Minimum spend threshold
`adFormats`	No	Filter by ad format types. Applied to ads endpoint automatically.
`offerName`	No	Filter by specific offer name
`startDate`	No	startDate in ISO 8601 format (YYYY-MM-DDThh:mm:ssZ), e.g., `startDate=2025-06-12T14:30:00.123Z`).
`offerTypes`	No	Filter by offer types. LG=Lead Gen forms, LP=Landing Pages
`oppsEndDate`	No	End date for opportunities data in ISO 8601 format
`campaignName`	No	Filter by specific campaign name
`creativeName`	No	Filter by specific creative name
`visibilities`	No	Filter by visibility status. The platform knows only VISIBLE (live) and ARCHIVED; there is no HIDDEN value and sending one is rejected with a 400.
`accountTagIds`	No	Set of account tag IDs to filter by
`audienceTypes`	No	Filter by audience types
`experimentIds`	No	Set of experiment IDs to filter by
`oppsStartDate`	No	Start date for opportunities data in ISO 8601 format
`showWithSpend`	No	Show only experiments/ingredients with spend data
`customFieldIds`	No	Custom field IDs to include
`experimentList`	No	Experiment list filter
`experimentName`	No	Filter by specific experiment name
`budgetGroupName`	No	Filter by specific budget group name
`maxAudienceSize`	No	Maximum audience size threshold
`minAudienceSize`	No	Minimum audience size threshold
`skipCustomFields`	No	Skip custom fields in response
`customAudienceName`	No	Filter by specific custom audience name
`usedInActiveExperiments`	No	Filter for ingredients used in active experiments only
`launchedExperimentStatuses`	No	Filter Performance Metrics by experiment launch statuses only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / size / description

Previous value: -"Number of results per page. Default 100; raise it freely (up to 10000) for comprehensive full-dataset analysis."New value: +"Results per page from 1 to 100; default 100. Use successive zero-based page values and response pagination metadata for more results."

changedInput schema / properties / size / maximum
```
Previous value: -10000New value: +100
```

First observedSep 16, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare read-only, non-destructive, closed-world behavior, and the description adds useful behavioral context beyond them: pagination, at most 100 rows per page, return of pagination metadata, and ISO 8601 date formatting. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with no wasted language. It front-loads what the tool reads, then explains endpoint selection, date format, and pagination behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema and read-only annotations, the description covers the key invocation context: report selection via endpoint, date format, and pagination limits. It still leaves sibling-tool differentiation to the agent, but is otherwise complete for this high-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameter semantics are already well documented in the schema. The description mentions that the endpoint argument selects the report and dates use ISO 8601, but this largely repeats schema-level information and adds little beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: read paginated performance metrics for ads, audiences, creatives, offers, target groups, or keywords. It is clear what the tool does, but it does not explicitly distinguish itself from sibling analytics tools such as experiment_performance_stats, budget_group_performance, or account_level_stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the listed report types and the statement that the endpoint argument selects the report, but there is no explicit guidance on when to choose this tool over sibling analytics tools. No exclusions or alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?