Pendo

Return the set of metadata that is available from the accounts table for each account. It is a set of . separated metadata field names to information about that field, including the type. Here is an example return value

{ "metadata.custom.ARR" : "float", "metadata.pendo.donotprocess" : "boolean" }

PERFORMANCE: This is a fast-running tool.

Retrieve account data and metadata OR just the counts of matching accounts by running aggregation queries directly against the account dataset. Every response entity will conceptually be an account of that subscription.

USE THIS TOOL FOR: Getting account information, metadata, and account counts with flexible filtering options.

PERFECT FOR QUERIES LIKE:

• "Get all accounts with their custom metadata fields"
• "Show me accounts from a specific segment"
• "How many accounts match certain criteria?" (set count=true)
• "Get account metadata like ARR, company size, or custom properties"

WHAT THIS TOOL RETURNS:

• Account data with selected metadata fields (without select passed in, no metadata fields are returned)
• Account counts when count=true is specified
• Results filtered by segments, specific account IDs, or other criteria

FILTERING OPTIONS:

• Filter by specific account ID
• Filter by account segments
• Select specific metadata fields to include

This tool executes aggregation queries directly and returns results immediately. For available metadata fields, use the accountMetadataSchema tool. Example usage of metadata fileds is select=["metadata.agent.is_paying","metadata.auto.lastvisit"].

PERFORMANCE: This is a fast-running tool.

Query aggregated activity metrics (events, minutes, unique visitors, unique accounts) for pages, features, track types, accounts, or visitors within a date range.

Use this tool to answer questions about usage patterns, engagement metrics, and activity counts. Supports filtering by account, visitor, segment, or specific item IDs, and grouping results by various dimensions.

USE FOR: Getting activity metrics from various sources with several filtering options.

EXAMPLES:

• Get account activity metrics for the account ID XYZ → dateRange={range:'relative', lastNDays:30}
• What are the most active pages in the last 30 days? → dateRange={range:'relative', lastNDays:30}
• How many visitors used feature ABC in the last 7 days? → dateRange={range:'relative', lastNDays:7}
• Show activity for the top 5 track types → dateRange={range:'relative', lastNDays:30}
• How many views did page X get in the last 30 days? → entityType='page', itemIds=['pageId'], count=true, dateRange={range:'relative', lastNDays:30}
• Count total events for feature X in the last week → entityType='feature', itemIds=['featureId'], count=true, dateRange={range:'relative', lastNDays:7}
• Return only the total number of matching visitors for a query → set count=true
• Query specific date range → dateRange={range:'custom', startDate:'2024-01-01', endDate:'2024-01-31'}
• Get page activity for January 2024 → entityType='page', dateRange={range:'custom', startDate:'2024-01-01', endDate:'2024-01-31'}
• Which visitors used feature X in Q1 2024? → entityType='feature', itemIds=['featureId'], group=['visitorId'], dateRange={range:'custom', startDate:'2024-01-01', endDate:'2024-03-31'}
• Which features have the most rage clicks → frustrationMetrics=true, entityType='feature', group=['visitorId'], sort=['-rageClickCount']
• What is the count of unique events for account → entityType='account', dateRange={range:'relative', lastNDays:30}
• Which visitors were active on the most days? → entityType='visitor', group=['visitorId'], sort=['-daysActive'], limit=5, dateRange={range:'relative', lastNDays:30}

NOT FOR: guides and polls; use the guidemetricstool instead.

RETURNS:

• Raw JSON array [{requestId, rows: [...], time, url}]
• When count=true: Returns a minimal JSON result with a 'count' field containing the sum of events (if itemIds provided), count of distinct group values (if group provided), or count of distinct entities
• Aggregated activity metrics for events, minutes spent, visitors, accounts, and (if frustrationMetrics set) some 'frustration' metrics.
• Results can be grouped by a provided field.
• Results can be sorted by a provided field.
• By default, results are limited at 1000.

FILTERING OPTIONS:

• Filter by account ID
• Filter by visitor ID
• Filter by item IDs (i.e. page, feature, track type)

SORT OPTIONS:

• Any SELECT/GROUP field (accountId, day, featureId, itemId, month, pageId, trackTypeId, visitorId, week)
• numEvents - total event count
• numMinutes - total minutes spent
• uniqueAccountCount - count of unique accounts
• uniqueVisitorCount - count of unique visitors
• daysActive - count of unique days active
• if frustrationMetrics param is set, any frustration metric: errorClickCount, rageClickCount, uTurnCount, deadClickCount

The maximum time range for this tool is 367 days.

PERFORMANCE: This is a fast-running tool.

Generates AI-clustered topics from customer feedback matching the given filters. Each topic contains a name, description, and count of related insights. Use this for high-level overviews of the most common themes in a feedback subset.

PERFORMANCE: This is a slow-running tool.

Retrieves key customer feedback insights extracted from raw feedback matching the given filters. Each item includes a summary, explanation, and supporting quote. Use this when the user wants to see actionable feedback insights which have been distilled from the raw customer feedback. Note: insights can also be referred to as 'highlights'

PERFORMANCE: This is a slow-running tool.

Retrieves the original, raw customer feedback matching the given filters. Each item includes id, title, description, and info about the account and visitor which gave the feedback. Use this when the user wants the full raw feedback, as opposed to the extracted insights or clustered topics. A maximum of 30 items will be returned, however there may be more matching the filter set.

PERFORMANCE: This is a slow-running tool.

Get comprehensive guide performance analysis including reach, engagement, and effectiveness metrics.

USE FOR: Analyzing specific guide performance with core metrics like reach, engagement rates, and completion analysis.

EXAMPLES:

• How is the onboarding guide performing this month?
• Show me metrics for the tooltip guide
• What are the completion rates for the walkthrough guide?
• How many users are dismissing the announcement guide?
• Show me daily guide completion trends over the last 2 weeks
• What's the weekly pattern for guide engagement?

RETURNS:

• Reach metrics: total views, unique viewers, unique accounts
• Engagement metrics: views per user, total interactions
• Effectiveness metrics: completion rate, dismissal rate
• Range periods (dayRange/weekRange): single aggregated values across entire date range
• Iterative periods (daily/weekly): time series with metrics broken down by day/week
• Raw aggregation results in JSON format

The maximum time range for this tool is 93 days.

PERFORMANCE: This is a fast-running tool.

Pendo data is split into subscriptions, which share a set of visitors and accounts. Each subscription is split into separate applications. This call returns a list of all the names and ids of all the subscriptions this user has access to, along with the names and ids of all of the applications in that subscription.

Most tools for this mcp require at least a subscription id; many also require an application id. Application ids are not unique across different subscriptions.

PERFORMANCE: This is a fast-running tool.

A tool designed for running PES (product engagement score) queries. For any score fields that aren't required or provided, default saved PES configuration options are used.

USE FOR: Analyzing the PES, which is made up of scores from feature adoption, stickiness, and growth.

EXAMPLES:

• What is the PES for this feature?
• What is adoption score for a specific feature, page, and track event?
• What is the stickiness score for accounts, weekly over monthly? (This may expressed as WAA over MAA)
• What is the stickiness score for visitors, daily over monthly, excluding weekends? (This may expressed as DAU over MAU)
• What is the growth score for accounts?

RETURNS:

• PES score and component scores (adoption, stickiness, growth)
• Individual component scores (adoption, stickiness, growth)

The maximum time range for this tool is 180 days.

PERFORMANCE: This is a fast-running tool.

Look up the names and descriptions of product entities, such as: accounts, pages, features, track types, or guides.

Useful for: finding relevant entities in the customer's product for follow-up analysis with other tools, or learning more about specific entities. Uses semantic search to find entities by conceptual meaning and relevance to natural language queries, with substring search fallback for exact matching when needed.

Tool may be used in one of two ways: 1. Get specific entities: itemIds and exactly one itemType are specified; search_fallback and search are not allowed in this case. 2. Search for relevant entities: search_fallback AND search are BOTH specified, along with one or more itemType; itemIds is not allowed in this case.

IMPORTANT: The search parameter should contain only the core query terms (e.g., "onboarding features", "Bridgeway Logistics"), not instructions or meta-commentary.

EXAMPLES:

• What features should I look at to track onboarding success?
• What parts of my app provide administrator functions?
• What communications do we have to end users advertising our annual conference?
• What instrumentation events do we collect for end-user performance?
• Which pages should I measure user activity on to see how much time users are spending in setup?
• What accounts contain 'acme' in their name?
• Do I have any accounts involved in steel manufacturing?

PERFORMANCE: This is a fast-running tool.

List all the segments. The name and the id of each segment is returned. These segments can be used for query build tools. Only publicly shared segments are returned.

PERFORMANCE: This is a fast-running tool.

Get session replay recordings with filtering by duration, activity percentage, and date range. Returns detailed session metadata including frustration events, activity scores, and app information.

USE FOR: Finding session replays with specific criteria, analyzing user session quality, identifying high-activity or problematic sessions

EXAMPLES:

• Show me recordings that occur on page 1234
• Show me session replays from the last week with high activity
• Find session replays longer than 5 minutes
• Show me session replays for visitor 1234

RETURNS:

• Session replay recordings with their URL and metadata including duration, activity percentage, frustration events, and app details. Limited to 50 replays returned.

The maximum time range for this tool is 31 days.

PERFORMANCE: This is a fast-running tool.

Return the set of metadata that is available from the visitors table for each visitor. It is a set of . separated metadata field names to information about that field, including the type. Here is an example return value

{ "metadata.auto.lastvisit" : "time", "metadata.pendo.donotproces" : "boolean" }

PERFORMANCE: This is a fast-running tool.

Retrieve visitor data and metadata OR just the counts of matching visitors by running aggregation queries directly against the visitor dataset. Every response entity will conceptually be a visitor (a person who visited the application) and their associated metadata if you use select to ask for them.

USE FOR: Getting visitor information, metadata, and visitor counts with flexible filtering options.

EXAMPLES:

• Get all visitors with their last visit time
• Show me visitors from a specific segment
• How many visitors match certain criteria? (set count=true)
• Get visitor metadata like browser, location, or custom fields
• Find visitors with a specific metadata value

WORKFLOW: Use the visitorMetadataSchema tool to explore available metadata fields, then use this tool for detailed analysis

RETURNS:

• Visitor data with selected metadata fields (without select passed in, no metadata fields are returned)
• Visitor counts when count=true is specified
• Results filtered by segments, specific visitor IDs, metadata, or other criteria
• Results are sorted by last visit time descending
• By default, results are limited to 10,000 visitors per request. If 10,000 visitors are returned, assume there are more visitors and consider refining your filters or increasing the limit.

FILTERING OPTIONS:

• Filter by specific visitor ID
• Filter by visitor segments
• Filter by metadata value for a specific metadata group and field
• Automatically filters out anonymous visitors (unless subscription allows them)

PERFORMANCE: This is a fast-running tool.