---
canonical_url: "https://docs.composio.dev/toolkits/contentsquare_mcp"
markdown_url: "https://docs.composio.dev/toolkits/contentsquare_mcp.md"
product: "platform"
version: null
last_updated: null
---

# Contentsquare MCP

Contentsquare MCP gives agents authorized access to experience-analytics projects and metrics through Contentsquare's hosted service.

- **Category:** model context protocol
- **Auth:** DCR_OAUTH
- **Composio-managed OAuth available?** No
- **Tools:** 21
- **Triggers:** 0
- **Slug:** `CONTENTSQUARE_MCP`
- **Version:** 20260910_00

## Tools

### Computefunnel

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_FUNNEL`

Computes 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `funnel` | object | Yes |  |
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `pageMappingId` | number | Yes | The mapping ID that the page groups belong to. Page groups must be from this mapping. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `unit` | string ("sessions" | "users") | Yes |  |
| `steps` | array | Yes |  |

### Computeimpact

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_IMPACT`

Computes 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `base` | object | Yes | Base configuration for the impact analysis |
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `compare` | object | No | Optional comparison configuration to compare impact metrics across different date ranges, device types, or user segments. |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `projectId` | number | Yes | Project ID for analysis context. |
| `conversionGoal` | number | Yes | Conversion goal ID for calculating segment performance metrics.        Must be from the available goals list. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `base` | object | Yes |  |
| `compare` | string | No |  |
| `evaluation` | object | No |  |

### Computejourney

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_JOURNEY`

Computes 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `journey` | object | Yes |  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `pageMappingId` | number | Yes | Page mapping ID containing the relevant page groups for analysis. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes |  |
| `size` | number | Yes |  |
| `children` | array | Yes |  |

### Computepagecomparison

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_PAGE_COMPARISON`

Computes 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `pageMapping` | number | Yes | The mapping for the page groups that the user wants to compare |
| `conversionGoal` | number | No | An id of a goal that's used by the "Conversion rate of selected goal" metric. |
| `pageGroupsToCompare` | array | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes |  |

### Computepagegroupmetrics

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_PAGE_GROUP_METRICS`

Compute page metrics, at the page group level. Use it to get an overview of the performance of the fraction of the website.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `device` | string ("all" | "desktop" | "mobile" | "tablet") | No | Device type to filter the analysis. If not provided, all devices are included. |
| `goalId` | number | No | Goal ID to filter the analysis. If not provided, no goal filtering is applied. |
| `metrics` | array | No | 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 |
| `projectId` | number | Yes | Project ID for analysis context. |
| `dimensions` | array | No | 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. |
| `userFilter` | object | No |      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. |
| `endDateTime` | string | Yes | 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. |
| `pageGroupId` | number | Yes | ID of the page group to compute metrics for. It can be found in the tool listing page groups |
| `startDateTime` | string | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `values` | array | Yes |  |

### Computesitemetrics

**Slug:** `CONTENTSQUARE_MCP_COMPUTE_SITE_METRICS`

Computes 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `device` | string ("all" | "desktop" | "mobile" | "tablet") | No | Device type to filter the analysis. If not provided, all devices are included. |
| `goalId` | number | No | Goal ID to filter the analysis. If not provided, no goal filtering is applied. |
| `metrics` | array | No | 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 |
| `projectId` | number | Yes | Project ID for analysis context. |
| `dimensions` | array | No | 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. |
| `userFilter` | object | No |      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. |
| `endDateTime` | string | Yes | 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. |
| `startDateTime` | string | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `values` | array | Yes |  |

### Getpagegroupsformapping

**Slug:** `CONTENTSQUARE_MCP_GET_PAGE_GROUPS_FOR_MAPPING`

Retrieve all page groups for a specific mapping, sorted alphabetically by name.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `mappingId` | number | Yes | The ID of the mapping to retrieve page groups for |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of page groups for the specified mapping, sorted alphabetically by name |

### Gettoperrorsbyimpactongoal

**Slug:** `CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_IMPACT_ON_GOAL`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `goalId` | number | Yes |    Conversion goal for error impact measurement. Use -1 for eCommerce goal.  |
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `errorType` | string ("all" | "JS" | "API" | "CUSTOM" | "CRASH" | "FLUTTER") | No |    Error category filter.   Options: 'all' (default), 'JS' (JavaScript errors), 'API' (backend API failures), 'CUSTOM' (custom errors), 'CRASH' (application crashes), 'FLUTTER' (Flutter mobile errors). |
| `mappingId` | number | Yes |    Page mapping ID for grouping pages.   Must be from the available mappings list.  |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `analysisScope` | string | Yes |  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `errorsListData` | string | Yes |  |

### Gettoperrorsbymissedopportunity

**Slug:** `CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_MISSED_OPPORTUNITY`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `goalId` | number | No |        Conversion goal for missed opportunity measurement. Use -1 for eCommerce goal.      |
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `errorType` | string ("all" | "JS" | "API" | "CUSTOM" | "CRASH" | "FLUTTER") | No |    Error category filter.   Options: 'all' (default), 'JS' (JavaScript errors), 'API' (backend API failures), 'CUSTOM' (custom errors), 'CRASH' (application crashes), 'FLUTTER' (Flutter mobile errors). |
| `mappingId` | number | Yes |    Page mapping ID for grouping pages.   Must be from the available mappings list.  |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `analysisScope` | string | Yes |  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `errorsListData` | string | Yes |  |

### Gettoperrorsbysessionswitherrors

**Slug:** `CONTENTSQUARE_MCP_GET_TOP_ERRORS_BY_SESSIONS_WITH_ERRORS`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `errorType` | string ("all" | "JS" | "API" | "CUSTOM" | "CRASH" | "FLUTTER") | No |    Error category filter.   Options: 'all' (default), 'JS' (JavaScript errors), 'API' (backend API failures), 'CUSTOM' (custom errors), 'CRASH' (application crashes), 'FLUTTER' (Flutter mobile errors). |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `granularity` | string ("MINUTE" | "HOUR" | "DAY" | "WEEK" | "MONTH") | No |      Time interval granularity for time-series data.     Valid values: MINUTE, HOUR, DAY, WEEK, MONTH.    |
| `analysisScope` | string | Yes |  |
| `errorDisplayUnit` | string ("unit" | "percent") | No | Metric display format.     'percent': rates/trends (default).     'unit': absolute volumes.    |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `errorRateData` | string | No |  |
| `errorChartData` | string | Yes |  |
| `errorTrendData` | string | Yes |  |
| `errorsListData` | string | Yes |  |

### Gettoppagegroupsbylostconversions

**Slug:** `CONTENTSQUARE_MCP_GET_TOP_PAGE_GROUPS_BY_LOST_CONVERSIONS`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `goalId` | number | Yes |    Conversion goal for error impact measurement. Use -1 for eCommerce goal.  |
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `errorType` | string ("all" | "JS" | "API" | "CUSTOM" | "CRASH" | "FLUTTER") | No |    Error category filter.   Options: 'all' (default), 'JS' (JavaScript errors), 'API' (backend API failures), 'CUSTOM' (custom errors), 'CRASH' (application crashes), 'FLUTTER' (Flutter mobile errors). |
| `mappingId` | number | Yes |    Page mapping ID for grouping pages.   Must be from the available mappings list.  |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `analysisScope` | string | Yes |  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `pageGroupsListData` | string | Yes |  |

### Gettoppagesbysessionswitherrors

**Slug:** `CONTENTSQUARE_MCP_GET_TOP_PAGES_BY_SESSIONS_WITH_ERRORS`

Get 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `locale` | string | No |    Locale for date/time formatting in BCP 47 format (e.g., 'en-US', 'fr-FR').  |
| `timezone` | string | No |    Timezone for date calculations (IANA timezone format, e.g., 'America/New_York', 'Europe/Paris').  |
| `dateRange` | object | Yes |    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. |
| `errorType` | string ("all" | "JS" | "API" | "CUSTOM" | "CRASH" | "FLUTTER") | No |    Error category filter.   Options: 'all' (default), 'JS' (JavaScript errors), 'API' (backend API failures), 'CUSTOM' (custom errors), 'CRASH' (application crashes), 'FLUTTER' (Flutter mobile errors). |
| `mappingId` | number | Yes |    Page mapping ID for grouping pages.   Must be from the available mappings list.  |
| `projectId` | number | Yes | Project ID for analysis context. |
| `deviceType` | object | Yes |  |
| `userFilter` | object | No |      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. |
| `displayType` | string ("pagegroups" | "pages") | No |        Aggregation level for page analysis.       'pagegroups': grouped page categories (default).       'pages': individual page URLs.      |
| `analysisScope` | string | Yes |  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `scatterChartData` | string | Yes |  |

### Listprojects

**Slug:** `CONTENTSQUARE_MCP_LIST_PROJECTS`

Returns a list of projects (id and name) accessible to the user

### Recommendgoals

**Slug:** `CONTENTSQUARE_MCP_RECOMMEND_GOALS`

Recommend goals based on user engagement and usage frequency (how often goals are viewed, used in analyses, etc.) within the platform.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of goals to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of goals based on popularity |

### Recommendmappings

**Slug:** `CONTENTSQUARE_MCP_RECOMMEND_MAPPINGS`

Recommend mappings based on user engagement and usage frequency (how often mappings are viewed, used in analyses, etc.) within the platform.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of mappings to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of mappings matching the search criteria |

### Recommendpagegroups

**Slug:** `CONTENTSQUARE_MCP_RECOMMEND_PAGE_GROUPS`

Recommend page groups based on user engagement and usage frequency (how often page groups are viewed, used in analyses, etc.) within the platform.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of page groups to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of page groups based on popularity |

### Recommendsegments

**Slug:** `CONTENTSQUARE_MCP_RECOMMEND_SEGMENTS`

Recommend 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 `total` exceeds `returned`, raise `limit` instead

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of segments to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `total` | number | Yes | 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. |
| `result` | array | Yes | Array of segments ranked by popularity, or — on a project with no engagement data — ordered by most recently updated. |
| `returned` | number | Yes | Number of results in this response. |
| `nextOffset` | number | No | Never returned by this tool, which takes no offset. Raise limit to see more segments. |

### Searchgoals

**Slug:** `CONTENTSQUARE_MCP_SEARCH_GOALS`

Search and retrieve goals for a project.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of goals to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of goals matching the search criteria |

### Searchmappings

**Slug:** `CONTENTSQUARE_MCP_SEARCH_MAPPINGS`

Search and retrieve mappings for a project.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | number | No | Maximum number of mappings to return. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result` | array | Yes | Array of mappings matching the search criteria |

### Searchsegments

**Slug:** `CONTENTSQUARE_MCP_SEARCH_SEGMENTS`

Search and retrieve segments for a project, optionally filtered by name.

- To find a segment by name, pass `text` rather 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 `offset` plus `returned` equals `total` — on a single
  call `offset` is 0, and while paging it is the position of the page in hand. `returned` counts one page,
  so on its own it reaches `total` only when the whole list fits in one
- When a response carries `nextOffset`, pass it back as `offset` to read the next page; its absence means no
  further page can be read — which is not the same as having reached `total`
- Every page of a large project costs a full read of it, so do not walk one in default-sized pages: narrow with
  `text` where the task allows it, and where the whole list is genuinely needed raise `limit` so it arrives
  in as few calls as possible

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | No | Filter by name on a contiguous, case-insensitive substring. A multi-word value matches only where those words appear adjacently and in that order. |
| `limit` | number | No | Maximum number of segments to return. |
| `offset` | number | No | Number of results to skip from the start of the returned ordering. Use with limit to page through results. |
| `projectId` | number | Yes | Project ID to get data for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `total` | number | Yes | Total number of results available for this request. Compare with returned to tell whether this response is complete. |
| `result` | array | Yes | Array of segments matching the search criteria, ordered with default segments first, then most recently updated first. |
| `returned` | number | Yes | Number of results in this response. |
| `nextOffset` | number | No | Offset to pass to read the next page of results. Absent once a response reaches the end. |

### Submitmcpfeedback

**Slug:** `CONTENTSQUARE_MCP_SUBMIT_MCP_FEEDBACK`

Submit feedback about your MCP server experience. Help us improve by rating tools and sharing your thoughts!

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `rating` | string ("1" | "2" | "3" | "4" | "5") | Yes | Rating from 1 (poor) to 5 (excellent) |
| `comment` | string | No | Optional feedback comment to help us understand your experience |
| `toolName` | string | No | Specific tool you are providing feedback about (optional) |
| `projectId` | number | Yes | The ID of the project submitting feedback |