- Category: model context protocol
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 21
- Triggers: 0
- Slug:
CONTENTSQUARE_MCP - Version: 20261018_00
Tools
Computefunnel
Computefunnel
Slug:
CONTENTSQUARE_MCP_COMPUTE_FUNNELComputes funnel analysis to measure drop-offs and conversions across key steps in a user journey. Analyzes conversion rates, drop-off points, and time to completion across up to 32 steps.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Output
Computeimpact
Computeimpact
Slug:
CONTENTSQUARE_MCP_COMPUTE_IMPACTComputes impact quantification analysis comparing conversion performance between segments. Provides metrics including conversion rates, bounce rates, session time, pageviews, and revenue impact with statistical significance testing.Input Parameters
Optional comparison configuration to compare impact metrics across different date ranges, device types, or user segments.
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Conversion goal ID for calculating segment performance metrics. Must be from the available goals list.
Output
Computejourney
Computejourney
Slug:
CONTENTSQUARE_MCP_COMPUTE_JOURNEYComputes user navigation journeys, visualizing how visitors navigate your site. Provides hierarchical tree structure showing common paths, drop-off points, and navigation patterns. Supports forward (from landing pages) and reverse (from exit pages) analysis up to 7 steps.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Output
Computepagecomparison
Computepagecomparison
Slug:
CONTENTSQUARE_MCP_COMPUTE_PAGE_COMPARISONComputes page comparison analysis comparing key performance metrics across multiple page groups (2-10). Provides metrics: views, bounce rate, exit rate, scroll rate, time spent, activity level, load times, and conversion rates.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Array of page group IDs to compare (minimum 2, maximum 10). All page groups must belong to the selected page mapping as ‘pageMapping’ field.
Output
Computepagegroupmetrics
Computepagegroupmetrics
Slug:
CONTENTSQUARE_MCP_COMPUTE_PAGE_GROUP_METRICSCompute page metrics, at the page group level. Use it to get an overview of the performance of the fraction of the website.Input Parameters
Device type to filter the analysis. If not provided, all devices are included.
Array of metrics to compute. Available metrics by category: - Base metrics (available for all projects): activityRate, bounceRate, elapsedTime, exitRate, foldHeight, interactionTime, landingRate, loadingTime, pageHeight, scrollRate, uniqueVisits, views, viewsVisits, visits, uniqueUsers - Ecommerce metrics (only for ecommerce projects): avgSessionLifetimeRevenue - Goal metrics (require goalId parameter): conversionRate - Error metrics: visitWithErrors - Frustration Score metrics
Array of dimensions to group the metrics by. If not provided, no grouping is applied. Supported dimensions: path, prefix, appVersion, appVersionSemVer, browserMajorVersion, browserName, browserVersion, city, countryCode, density, deviceId, language, manufacturer, model, osVersion, platformName, platformVersion, screenHeight, screenWidth, sdkBuildNumber, sessionConnectivityTypes, day.
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
End date for the analysis computation in YYYY-MM-DDTHH:mm format (e.g., 2025-10-05T00:00). Must not be later than current time or earlier than the start date. Maximum date range is 92 days.
ID of the page group to compute metrics for. It can be found in the tool listing page groups
Start date for the analysis in YYYY-MM-DDTHH:mm format (e.g., 2025-10-01T00:00). Must not be later than current time or later than the end date.
Output
Computesitemetrics
Computesitemetrics
Slug:
CONTENTSQUARE_MCP_COMPUTE_SITE_METRICSComputes aggregated metrics across the entire website. Returns data grouped by specified dimensions (device, date, browser, country, etc.). Filters: time period (startDateTime/endDateTime), device type (DESKTOP/MOBILE/TABLET/ALL), conversion goals (goalId), or advanced user filters (userFilter for browsers, goals, segments, page interactions). Use dimensions parameter to group results. Defaults to no grouping if not specified.Input Parameters
Device type to filter the analysis. If not provided, all devices are included.
Array of metrics to compute. Available metric types: - Basic site metrics: bounceRate, sessionTimeAverage, viewsVisits, visits, pageviewAverage - Goal site metrics: conversionCount, conversionRate - Ecommerce site metrics: cartAverage, revenue, transactionRate, transactionCount - Error metrics: visitWithErrors - Frustration Score metrics
Array of dimensions to group the metrics by. If not provided, no grouping is applied. Supported dimensions: appVersion, appVersionSemVer, browserMajorVersion, browserName, browserVersion, city, countryCode, density, deviceId, language, manufacturer, model, osVersion, platformName, platformVersion, screenHeight, screenWidth, sdkBuildNumber, sessionConnectivityTypes, day.
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
End date for the analysis computation in YYYY-MM-DDTHH:mm format (e.g., 2025-10-05T00:00). Must not be later than current time or earlier than the start date. Maximum date range is 92 days.
Start date for the analysis in YYYY-MM-DDTHH:mm format (e.g., 2025-10-01T00:00). Must not be later than current time or later than the end date.
Output
Getpagegroupsformapping
Getpagegroupsformapping
Gettoperrorsbyimpactongoal
Gettoperrorsbyimpactongoal
Slug:
CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_IMPACT_ON_GOALGet top errors ranked by impact on conversion goals. Shows business-critical errors affecting revenue and conversions. USE for: business impact analysis, revenue-critical issues, prioritizing fixes by business value, conversion impact of errors. Requires mappingId and goalId to analyze goal-specific impact.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Error category filter. Options: ‘all’ (default), ‘JS’ (JavaScript errors), ‘API’ (backend API failures), ‘CUSTOM’ (custom errors), ‘CRASH’ (application crashes), ‘FLUTTER’ (Flutter mobile errors).
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Output
Gettoperrorsbymissedopportunity
Gettoperrorsbymissedopportunity
Slug:
CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_MISSED_OPPORTUNITYGet top errors ranked by missed business opportunities (eCommerce focused). Shows revenue impact of errors. USE for: eCommerce missed revenue opportunities, lost sales analysis, revenue impact of errors. Always uses goalId -1 for eCommerce analysis. Requires mappingId.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Error category filter. Options: ‘all’ (default), ‘JS’ (JavaScript errors), ‘API’ (backend API failures), ‘CUSTOM’ (custom errors), ‘CRASH’ (application crashes), ‘FLUTTER’ (Flutter mobile errors).
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Output
Gettoperrorsbysessionswitherrors
Gettoperrorsbysessionswitherrors
Slug:
CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_SESSIONS_WITH_ERRORSGet top errors ranked by sessions with errors. Main widget for general error analysis showing error trends, rates, and most frequent errors. USE for: general error questions, error trends, most frequent errors, volume comparisons, overall error patterns. This is the primary tool for error analysis.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Error category filter. Options: ‘all’ (default), ‘JS’ (JavaScript errors), ‘API’ (backend API failures), ‘CUSTOM’ (custom errors), ‘CRASH’ (application crashes), ‘FLUTTER’ (Flutter mobile errors).
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Time interval granularity for time-series data. Valid values: MINUTE, HOUR, DAY, WEEK, MONTH.
Metric display format. ‘percent’: rates/trends (default). ‘unit’: absolute volumes.
Output
Gettoppagegroupsbylostconversions
Gettoppagegroupsbylostconversions
Slug:
CONTENTSQUARE_MCP_GET_TOP_PAGE_GROUPS_BY_LOST_CONVERSIONSGet page groups ranked by lost conversions due to errors. Shows business impact of errors by page groups. USE for: page group impact analysis, page-level conversions, top pages losing conversions, business impact by page groups. Requires mappingId and goalId to analyze conversion impact.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Error category filter. Options: ‘all’ (default), ‘JS’ (JavaScript errors), ‘API’ (backend API failures), ‘CUSTOM’ (custom errors), ‘CRASH’ (application crashes), ‘FLUTTER’ (Flutter mobile errors).
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Output
Gettoppagesbysessionswitherrors
Gettoppagesbysessionswitherrors
Slug:
CONTENTSQUARE_MCP_GET_TOP_PAGES_BY_SESSIONS_WITH_ERRORSGet pages most affected by errors in a scatter plot comparing error volume with page traffic. USE for: identifying pages most affected by technical issues, development resource focus, scatter plot analysis of pages vs error rates. Supports both ‘pagegroups’ (default) for category-level analysis and ‘pages’ for detailed URL-level analysis. Requires mappingId parameter.Input Parameters
Timezone for date calculations (IANA timezone format, e.g., ‘America/New_York’, ‘Europe/Paris’).
Date range for analysis. “from” must be earlier than or equal to “to”. “to” must be earlier than or equal to current time. “from” must not be earlier than the <earliest data> in the <User Data> tag. Maximum range is 92 days. Dates use YYYY-MM-DDTHH:mm:ss format.
Error category filter. Options: ‘all’ (default), ‘JS’ (JavaScript errors), ‘API’ (backend API failures), ‘CUSTOM’ (custom errors), ‘CRASH’ (application crashes), ‘FLUTTER’ (Flutter mobile errors).
Optional filter to analyze a subset of users based on browser type, goal completion, segment membership, or page interactions (bounce, exit, landing). Supports nested filter sets with AND/OR logic. Available filter types: browser, goal, segment, pageview_bounce, pageview_exit, pageview_landing.
Aggregation level for page analysis. ‘pagegroups’: grouped page categories (default). ‘pages’: individual page URLs.
Output
Listprojects
Listprojects
Slug:
CONTENTSQUARE_MCP_LIST_PROJECTSReturns a list of projects (id and name) accessible to the userRecommendgoals
Recommendgoals
Recommendmappings
Recommendmappings
Recommendpagegroups
Recommendpagegroups
Recommendsegments
Recommendsegments
Slug:
CONTENTSQUARE_MCP_RECOMMEND_SEGMENTSRecommend segments based on user engagement and usage frequency (how often segments are viewed, used in analyses, etc.) within the platform. A project with no recent engagement data falls back to the most recently updated segments instead.- This tool cannot page. When
totalexceedsreturned, raiselimitinstead
Input Parameters
Output
Number of segments this response had available to rank: those whose engagement data was read, or every segment in the project when there is none. May exceed the number returned — raise limit to see more. On an exceptionally active project the engagement read is itself capped, so this counts what was ranked rather than every segment that has ever been engaged with.
Array of segments ranked by popularity, or — on a project with no engagement data — ordered by most recently updated.
Searchgoals
Searchgoals
Searchmappings
Searchmappings
Searchsegments
Searchsegments
Slug:
CONTENTSQUARE_MCP_SEARCH_SEGMENTSSearch and retrieve segments for a project, optionally filtered by name.- To find a segment by name, pass
textrather than listing segments and scanning the result: the filter is applied before any row limit, so a filtered answer is complete even on a project too large to list. Pass one contiguous fragment of the name, not several words that may not be adjacent - NEVER describe a segment list as complete unless
offsetplusreturnedequalstotal— on a single calloffsetis 0, and while paging it is the position of the page in hand.returnedcounts one page, so on its own it reachestotalonly when the whole list fits in one - When a response carries
nextOffset, pass it back asoffsetto read the next page; its absence means no further page can be read — which is not the same as having reachedtotal - Every page of a large project costs a full read of it, so do not walk one in default-sized pages: narrow with
textwhere the task allows it, and where the whole list is genuinely needed raiselimitso it arrives in as few calls as possible
Input Parameters
Filter by name on a contiguous, case-insensitive substring. A multi-word value matches only where those words appear adjacently and in that order.
Number of results to skip from the start of the returned ordering. Use with limit to page through results.
Output
Total number of results available for this request. Compare with returned to tell whether this response is complete.
Array of segments matching the search criteria, ordered with default segments first, then most recently updated first.