Articles in this section

Blue Triangle MCP Server: Performance Endpoint

Shelby Butt
  • Updated
Follow

Table of Contents: 

Overview

This article is the technical guide for the Performance endpoint in the Blue Triangle MCP 

Available Tools

get_performance_summary

Get summarized performance statistics grouped by dimensions (page, browser, country, time). Use for dashboards, trend analysis, and group comparisons. Use get_page_hits_raw instead for individual page-view records.

Required Parameters

Parameter Type Description
startDate integer Unix epoch start time (seconds)
endDate integer Unix epoch end time (seconds)
group array Group-by dimensions, max 3. Options: time, pageName, pageGroup, trafficSeg, country, region, agentLocation (synthetic only), browser, os, device, browserVersion, netspeed, visitorType, httpCode (synthetic only), campaignSource, campaignMedium, campaignName, isp, abSegment, datacenter, url, customCategory, customVariable

Optional Parameters

Parameter Description
columns Metrics to return. Defaults to core CWV metrics (largestContentfulPaint, cumulativeLayoutShift, intToNextPaint). See Available Metrics below for the full list, including VitalScope attribution fields.
dataType rum, native, synthetic, or basepage (default: rum)
avgType Aggregation method: geometric, arithmetic, or percentile
percentile Percentile value 0–100 (used only with avgType=percentile)
bucketSize Time bucket unit (minute, hour, day) — only used when grouping by time
bucketValue Size of each time bucket
pageName Filter by configured page name(s)
urlSearch Filter by URL substring; wildcards (*) supported
pageGroup Filter by page group
trafficSeg Filter by traffic segment
browser Filter by browser
device Filter by device
os Filter by operating system
country Filter by country (ISO 3166-1 alpha-2)
region Filter by region/state
netspeed Filter by network type: other, dialup, cable, corporate, cellular
campaignSource Filter by traffic source
campaignName Filter by campaign name
campaignMedium Filter by traffic medium
abSegment Filter by A/B test segment
datacenter Filter by data center
isp Filter by Internet Service Provider
botTraffic includeBots, excludeBots, or botsOnly
visitorType Filter by new/returning visitors (array)
resourceOnly yes or no — limit to sessions with resource data captured (default: no)
salesType Use standard sales or brand value
agentLocation Synthetic agent location code(s) — synthetic dataType only
notAllPages Set to 1 to exclude "All Pages" when grouping by page name
removeGetParams Strip query parameters from URLs
excluded Exclude beacon types: standard (0), email (4), custom (20), or a combination
customCategory Configurable data collection category (1–5)
customVariable Configurable data collection variable (1–15)
sessionID RUM or Synthetic session ID filter
limit Maximum rows to return (1–50,000)
page Result page index (min 1)
order Order by a single column/metric: time, pageHits, pageName, country, region, trafficSeg, browser, os, device
sort Sort direction (asc or desc) for the order column
returnPageNames Return page names for URL search
timezoneOffset Timezone offset in hours

Sample Request

{"startDate": 1737000000,
 "endDate": 1737086400,
 "group": ["pageName"],
 "columns": ["largestContentfulPaint", "cumulativeLayoutShift", "intToNextPaint"],
 "dataType": "rum"}

compare_performance_data

Compare performance metrics between two non-overlapping time periods — calls /performance once per period. Ideal for A/B testing, before/after analysis, and regression detection. Display results in a table with a percentage-deviation column.

Required Parameters

Parameter Type Description
startDate1 integer Period 1 start time (Unix epoch seconds)
endDate1 integer Period 1 end time (Unix epoch seconds)
startDate2 integer Period 2 start time (Unix epoch seconds)
endDate2 integer Period 2 end time (Unix epoch seconds)
group array Group-by dimensions, max 3 (same options as get_performance_summary)

Note: This tool accepts the same optional parameters as get_performance_summary (see above), including columns and dataType.

Available Metrics

Core Web Vitals & User Experience

Metric Description Unit
largestContentfulPaint Largest Contentful Paint (LCP) – loading performance ms
intToNextPaint Interaction to Next Paint (INP) – interactivity ms
cumulativeLayoutShift Cumulative Layout Shift (CLS) – visual stability score
firstContentfulPaint First Contentful Paint (FCP) – first content render ms
totalBlockingTime Total Blocking Time (TBT) – load responsiveness ms
firstInputDelayDuration First Input Delay (FID) – legacy metric ms

Advanced Attribution (VitalScope)

Available on RUM/Native dataTypes only. Use these when a user wants to know why a Core Web Vital is slow, not just the value.

Group Metrics
LCP timing LCPElementRenderDelayMS, LCPElementRenderDelayPercentage, LCPTimeToFirstByteMS, LCPTimeToFirstBytePercentage, LCPResourceDelayMS, LCPResourceLoadDelayPercentage, LCPResourceLoadTimeMS, LCPResourceLoadTimePercentage
LCP attribution LCPSelector, LCPURL
CLS timing CLSLargestShiftStart, CLSLayoutShiftCount
CLS attribution CLSLargestShiftSelector
INP timing INPStart, INPInputDelay, INPNextPaintTime, INPProcessingDuration, INPPresentationDelay
INP attribution INPTargetSelector, INPEventType, INPTarget
LoAF timing LOAFLongestScriptDuration, LOAFLongestScriptStart
LoAF attribution LOAFLongestScriptInvoker, LOAFLongestScriptSourceURL

Page Load Timing

Metric Description Unit
onload Page Onload Time – total load time ms
firstByte Time to First Byte (TTFB) – server response time ms
dns DNS Lookup Time ms
tcp TCP Connection Time ms
ssl SSL Handshake Time ms
redirect Redirect Time ms
basePage Base Page Time ms
dom DOM Processing Time ms
timeToInteractive Time to Interactive (TTI) ms
fullyLoadedTime Fully Loaded Time ms
speedIndex Speed Index – visual progress score score

Business & Traffic

Metric Description Unit
visitors Unique Visitors count
pageHits Page Views count
revenue Total Revenue – requires revenue enabled (see enable_revenue) currency
orders Total Order Count – requires revenue enabled count
jsErrorCount JavaScript Error Count (RUM/Native only) count
fidHits First Input Delay sample count (RUM/Native only) count

Error & Status Tracking

Metric Description Unit
200_code HTTP 200 (Success) – synthetic dataType count
300_code HTTP 300 (Redirects) – synthetic dataType count
400_code HTTP 400 (Client Errors) – synthetic dataType count
500_code HTTP 500 (Server Errors) – synthetic dataType count
600_code HTTP 600 (Custom Errors) – synthetic dataType count

Note: For JavaScript errors, general errors, and CSP violations with full detail rows, use get_error_data instead — see the Error Data article.

Example Queries

  • "Show me Core Web Vitals (LCP, INP, CLS) for the last 7 days"
  • "What's our LCP performance by device type this month?"
  • "Show me 95th percentile LCP by country"
  • "Compare this week's performance to last week"
  • "Show me daily onload time trends for the last 30 days"
  • "How has First Byte time changed over the past month?"
  • "Break down page load times by browser, device, and country"
  • "Show me performance metrics by A/B test segment"
  • "Compare performance across page groups by visitor type"
  • "Why is LCP slow on our homepage?" (use the VitalScope attribution metrics above)

Comments

0 comments

Please sign in to leave a comment.