Pendo

Get app-level usage metrics over time. Groups events into buckets of the requested period (daily/weekly/monthly) and returns one row per bucket with app-wide totals: active visitors, active accounts, events, average active time (a duration object {seconds, display}), and the four frustration counts (totalErrorClickCount, totalRageClickCount, totalUTurnCount, totalDeadClickCount). The average metric matches the requested period: avgDailyActiveTime, avgWeeklyActiveTime, or avgMonthlyActiveTime. Audience can be scoped via an inline segmentPipeline; scope can also be narrowed to a single app via appId. minEvents restricts every bucket to the visitors with at least that many events in that bucket, applied independently per bucket, so one call tracks an engagement threshold across the whole range. It counts events rather than visits, so it is not a returning-visitor measure. USE FOR: Trend questions about whole-app usage over a window - e.g. 'how did active visitors trend over the last 12 weeks?', 'are rage clicks across our apps trending up?'. With minEvents, tracks a per-bucket event threshold over time - e.g. 'visitors with at least 2 events per month'. EXAMPLES: - How did active visitors trend over the last 12 weeks? - Total events per week across all apps over the last quarter - Are rage clicks across our apps trending up over the last 30 days? - How many visitors had at least 2 events in each of the last twelve months? RETURNS: - meta.dateRange: resolved startDate and endDate (YYYY-MM-DD) - meta.period: echoed bucket size (daily|weekly|monthly) - meta.metrics: list of metric names returned per bucket - rows: one entry per time period, containing a 'bucket' string (YYYY-MM-DD or YYYY-MM), a startTime (epoch ms), and metric values; numeric metrics zero-fill for empty buckets

buildPendoSegment: Purpose: Describe one visitor segment by visitor or account ID, activity on Pages, Features, TrackEvents, Guides, Poll responses, the elements inside a guide, segment membership, or metadata. Input shape: pass definition as an array of rule groups. Top-level groups are ANDed together; rules within a group are ORed together. For one ANDed rule, wrap it in a single-item group. SINGLE CALL CONTRACT (important): The ENTIRE segment, including every AND clause and every OR clause, MUST be built with ONE call to this tool. Never split a segment across multiple calls. Combine all clauses into a single definition array and pass it once. Calling the tool more than once produces multiple unrelated segments, NOT one combined segment, so the AND/OR logic between the calls is lost. Mapping a request to a single definition: - Split the request into top-level AND clauses. - Each AND clause becomes one group (one inner array) in the definition. - Inside a clause, every OR alternative becomes one rule object in that group. - A clause with no OR is a group containing a single rule object. CLAUSE COVERAGE (important): Account for EVERY clause in the request. Before returning, count the AND clauses in the request and confirm the definition has exactly that many top-level groups, then confirm every OR alternative inside each clause is present as a rule object. Never drop, merge, or skip a clause. If the request mentions a page rule, a feature rule, and a track event rule joined by AND/OR, all of them must appear. A request like "(X OR Y) AND Z" has 2 top-level groups (one for "X OR Y", one for "Z") and 3 rule objects total; returning fewer groups or rules is wrong. Full example (combining AND and OR in one call): Request: "(visitors who spent > 15 minutes on page A in May OR have NOT seen page B in the last year) AND triggered track event C on fewer than 5 days in the last 7 days" Correct single definition (one tool call): [ [ { "entityType": "page", "entityId": "A", "metric": "eventTime", "operator": ">", "threshold": 15, "condition": "between", "first": "2026-05-01", "last": "2026-05-31" }, { "entityType": "page", "entityId": "B", "metric": "notseen", "condition": "withinLast", "lookbackAmount": 12, "granularity": "months" } ], [ { "entityType": "trackEvent", "entityId": "C", "metric": "daysActive", "operator": "<", "threshold": 5, "condition": "withinLast", "lookbackAmount": 7, "granularity": "days" } ] ] The first group (the two page rules) is ORed together; that group is then ANDed with the second group (the track event rule). This is ONE call, not two. REQUIRED FIELDS AND CONDITION CHOICE (important): Activity metrics with non-empty supportedConditions MUST include an explicit "condition" field. It is the discriminator that selects which time/frequency fields apply, and it is NOT optional for those metrics. Always choose condition from the chosen metric's supportedConditions. Do NOT rely on the presence of first/last, lookbackAmount/granularity, or date to imply the condition; you must still set condition explicitly for activity metrics. For example: - first + last present => you MUST also set condition: "between" - lookbackAmount + granularity => you MUST also set condition: "withinLast" - date present => you MUST also set condition: "since" Segment membership metrics are the exception: - isMemberOfSegment and isNotMemberOfSegment have supportedConditions: [] by design. - For these metrics, omit "condition" entirely. Do NOT add "ever" or infer any default condition. - supportedConditions: [] means "no condition field", not "choose a default condition". Visitor and account ID rules are conditionless and metricless: - Use entityType: "visitor" or "account". - Use operator: one of "==", "!=", "contains", "!contains", "empty", "!empty". Omit it to default to "==". - Use entityId for the comparison value with "==", "!=", "contains", and "!contains". - Use an empty entityId with "empty" and "!empty". - Example: { "entityType": "visitor", "entityId": "bob@example.com" }. - Example: { "entityType": "visitor", "entityId": "@example.com", "operator": "contains" }. - Example: { "entityType": "account", "entityId": "acme-corp" }. Metadata rules are also conditionless and metricless: - Use entityType: "metadata". - Use entityId for the full metadata key, e.g. "visitor.agent.job_role". - Use operator: one of "==", "!=", ">=", "<=", "contains", "!contains", "empty", "!empty". - Use value for "==", "!=", ">=", "<=", "contains", and "!contains". Omit value for "empty" and "!empty". - Time and date metadata values may use ISO 8601, e.g. "2025-12-31T23:59:59Z". - Example: { "entityType": "metadata", "entityId": "visitor.agent.job_role", "operator": "==", "value": "Software engineer" }. Event-property filters narrow page, feature, or track-event aggregation rules by a property on each event: - Add one eventProperty object with property, operator, and (except for empty/!empty) value. - For a custom event property, use its plain property name. Custom properties are supported on feature and trackEvent rules. - For historical metadata captured on an event, use kind.group.field, e.g. "visitor.agent.user_job_role". Historical metadata is supported on page, feature, and trackEvent rules. - Event properties require an aggregation metric such as eventCount or daysActive; they cannot be added to seen/used counter metrics. - Use listCountables eventPropertyNames to discover custom properties. Historical metadata must currently be promoted. - Example: visitors who ran a report with the "source" filter in the last 30 days: [ [ { "entityType": "trackEvent", "entityId": "<reportRanTrackEventId>", "metric": "eventCount", "operator": ">=", "threshold": 1, "condition": "withinLast", "lookbackAmount": 30, "granularity": "days", "eventProperty": { "property": "filter", "operator": "==", "value": "source" } } ] ] Guide element rules cover clicks on one button, link or close icon inside a guide: - Use entityType: "guideElement". - Use entityId for the GUIDE id, stepId for the step the element sits on, and elementId for the element's uiElementId, e.g. { "entityType": "guideElement", "entityId": "<guideId>", "stepId": "<guideStepId>", "elementId": "pendo-button-a1b2c3d4", "metric": "eventCount", "operator": ">=", "threshold": 1, "condition": "withinLast", "lookbackAmount": 30, "granularity": "days" }. - One getEntity call gives both ids: steps[].stepId and the steps[].elements[].uiElementId nested under it. Never guess either. - eventCount is the only supported metric, and it counts clicks on that element in the chosen window: - "clicked it" => operator ">=", threshold 1 - "did not click it" => operator "==", threshold 0 - click counts => any operator, e.g. "clicked it more than 3 times" is operator ">", threshold 3 - stepId does not narrow the count. - Only withinLast and between are available, so a click rule is always scoped to a window. Poll response rules select visitors by a numeric poll response: - Use entityType: "poll", entityId for the guide id, and pollId for its poll. - Resolve pollId from getEntity's guide steps[].polls[] output; select the poll whose type is the poll type. Never guess a pollId. - Use metric: "response", a numeric operator and threshold, plus a supported condition. - Conditions ever, since (with date), withinLast, and between are supported. A response range requires two separate top-level AND groups, not one OR group. For example, responses from 7 through 10 in the last 30 days: [ [{ "entityType": "poll", "entityId": "<surveyGuideId>", "pollId": "<pollId>", "metric": "response", "operator": ">=", "threshold": 7, "condition": "withinLast", "lookbackAmount": 30, "granularity": "days" }], [{ "entityType": "poll", "entityId": "<surveyGuideId>", "pollId": "<pollId>", "metric": "response", "operator": "<=", "threshold": 10, "condition": "withinLast", "lookbackAmount": 30, "granularity": "days" }] ] Resolution steps 1. Choose entityType from EntityTypes. 2. For visitor or account, use entityId + optional operator and stop here. 3. For metadata, use entityId + operator + optional value and stop here. 4. For activity and segment entities, choose metric from EntityTypes[entityType].supportedMetrics. 5. Look up Metrics[metric]. 6. If Metrics[metric].supportedConditions is non-empty, choose condition from that list and look up Conditions[condition]. 7. The final rule fields are: EntityTypes[entityType].requiredFields + Metrics[metric].requiredFields + Conditions[condition].requiredFields, only when a condition is required. Time phrase resolution examples: - "this year" / "so far this year" / "year to date" => condition: "since", date: "2026-01-01" - "this month" / "month to date" => condition: "since", date: "2026-06-01" - "since 2026-01-01" => condition: "since", date: "2026-01-01" - "last year" => condition: "between", first: "2025-01-01", last: "2025-12-31" - "in the last year" => condition: "withinLast", lookbackAmount: 12, granularity: "months" - "between 2026-01-01 and 2026-06-05" => condition: "between", first: "2026-01-01", last: "2026-06-05" - "in March" => condition: "between", first: "2026-03-01", last: "2026-03-31" - "last 3 weeks" => condition: "withinLast", lookbackAmount: 3, granularity: "weeks" - "last 7 days" => condition: "withinLast", lookbackAmount: 7, granularity: "days" CONDITION CHOICE FOR TIME PHRASES (important): - Use "since" (set only date) for any open-ended period running from a start date up to now: "this year", "this month", "year to date", "so far", "since <date>". Do NOT express these as "between ... today". - Use "between" (set first + last) ONLY for a closed range whose end is a specific past date or the last day of a named calendar period (e.g. "in March", "last year", "between X and Y"). - Use "withinLast" (set lookbackAmount + granularity) for rolling windows: "last N days/weeks/months". - Set ONLY the fields the chosen condition requires. Never combine date with first/last in one rule. A segment should be just as valid in a week's time as it is today, so never hardcode today's date as an endpoint. For a fixed/named calendar period (e.g. "in March") use "between" spanning the entire period even if it has not finished yet. For an open-ended current period (e.g. "this year", "this month") use "since" with the period's start date, which stays valid going forward. EntityTypes: visitor: requiredFields: entityType: "visitor" entityId: String supportedMetrics: [] account: requiredFields: entityType: "account" entityId: String supportedMetrics: [] page: requiredFields: entityType: "page" entityId: String supportedMetrics: ["eventCount", "deadClicks", "errorClicks", "rageClicks", "daysActive", "uTurns", "eventTime", "seen", "notseen", "lastSeen"] feature: requiredFields: entityType: "feature" entityId: String supportedMetrics: ["eventCount", "deadClicks", "errorClicks", "rageClicks", "daysActive", "used", "notused", "lastused"] trackEvent: requiredFields: entityType: "trackEvent" entityId: String supportedMetrics: ["eventCount", "daysActive", "used", "notused", "lastused"] guide: requiredFields: entityType: "guide" entityId: String supportedMetrics: ["seen", "lastSeen", "notSeen"] poll: requiredFields: entityType: "poll" entityId: String pollId: String // the poll nested under the guide supportedMetrics: ["response"] guideElement: requiredFields: entityType: "guideElement" entityId: String stepId: String // the guide step the element sits on elementId: String // the element's uiElementId, e.g. "pendo-button-a1b2c3d4" supportedMetrics: ["eventCount"] segment: requiredFields: entityType: "segment" entityId: String supportedMetrics: ["isMemberOfSegment", "isNotMemberOfSegment"] metadata: requiredFields: entityType: "metadata" entityId: String supportedMetrics: [] agent: requiredFields: entityType: "agent" entityId: String supportedMetrics: ["eventCount", "daysActive", "used", "notused", "lastused"] Metrics: eventCount: description: Number of events for the selected entity. requiredFields: metric: "eventCount" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] deadClicks: description: Number of dead clicks for the selected page or feature. requiredFields: metric: "deadClicks" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] errorClicks: description: Number of error clicks for the selected page or feature. requiredFields: metric: "errorClicks" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] rageClicks: description: Number of rage clicks for the selected page or feature. requiredFields: metric: "rageClicks" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] daysActive: description: Number of active days for the selected entity. requiredFields: metric: "daysActive" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] uTurns: description: Number of u-turns for the selected page. requiredFields: metric: "uTurns" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] eventTime: description: Time in minutes spent on the selected page. requiredFields: metric: "eventTime" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["withinLast", "between"] response: description: Numeric poll response. Use two ANDed rules for a range. requiredFields: metric: "response" operator: Enum["==", "!=", ">=", "<="] threshold: Integer supportedConditions: ["ever", "since", "withinLast", "between"] used: description: Whether the selected feature or track event was used, optionally with a frequency threshold. requiredFields: metric: "used" supportedConditions: ["ever", "since", "withinLast", "atLeast", "atMost"] notused: description: Whether the selected feature or track event was not used. requiredFields: metric: "notused" supportedConditions: ["ever", "since", "withinLast"] lastused: description: When the selected feature or track event was last used. requiredFields: metric: "lastused" supportedConditions: ["since", "withinLast", "between"] seen: description: Whether the selected page was seen, optionally with a frequency threshold. For checking withinLast requiredFields: metric: "seen" supportedConditions: ["ever", "since", "withinLast", "atLeast", "atMost"] notseen: description: Whether the selected page was not seen. requiredFields: metric: "notseen" supportedConditions: ["ever", "since", "withinLast"] lastSeen: description: When the selected page was last seen. requiredFields: metric: "lastSeen" supportedConditions: ["since", "withinLast", "between"] isMemberOfSegment: description: Whether the visitor is a member of the selected segment. requiredFields: metric: "isMemberOfSegment" supportedConditions: [] isNotMemberOfSegment: description: Whether the visitor is not a member of the selected segment. requiredFields: metric: "isNotMemberOfSegment" supportedConditions: [] Conditions: ever: description: The metric happened at any time. requiredFields: condition: "ever" since: description: The metric happened on or after a specific date. requiredFields: condition: "since" date: DateString("yyyy-mm-dd") withinLast: description: The metric happened within a rolling time window. requiredFields: condition: "withinLast" lookbackAmount: Integer granularity: Enum["days", "weeks", "months"] between: description: The metric happened within an inclusive date range. requiredFields: condition: "between" first: DateString("yyyy-mm-dd") last: DateString("yyyy-mm-dd") atLeast: description: The metric happened at least threshold times ever requiredFields: condition: "atLeast" threshold: Integer atMost: description: The metric happened at most threshold times ever requiredFields: condition: "atMost" threshold: Integer

Compute a retention curve for an app (scope='app'), a specific page or feature (scope='page' or 'feature'), a track event (scope='trackEvent'), or a whole product area (scope='productArea'). For track events: measures how many accounts/visitors continue firing the event over time. Supports visitor-level or account-level retention (unit) and all vs first cohort modes (cohortMode='all' for all active users, 'first' for first-time users only - best for onboarding effectiveness). For scope='productArea', a user counts as active in a period if they used any page, feature, or track event in that area; guides in the area are not counted. Omit appId when the entity or area spans multiple applications - passing one restricts the curve to that application. Call this tool ONCE per question. A single call returns all periods at once - do NOT call it multiple times with different periodCount values. The analysis window is anchored to now() and works backwards. Do NOT pre-filter for 'new users in the last N days' via segmentPipeline - pass cohortMode='first' instead, which restricts to users whose all-time first interaction falls within the analysis window (truly new users, not returning users re-entering the window). Period 0 = '< 1 Month' is the % of cohort active more than once in their first period - a real metric, NOT a 100% baseline (typical rates 25-60%). Period N = % of cohort still active N periods later. activeCount at higher periods decreases because users too new to have reached that period are excluded from the denominator (dynamic denominator - correct, not missing data). summary.finalRetentionRate is the most important single number - it represents the durable retained core. USE FOR: Retention and churn questions - e.g. 'what % of users return after 3 months?', 'show me our retention curve', 'what's our churn rate?'. Not for acquisition questions ('how many new accounts did we gain?') - this tool measures continued activity of existing cohorts, not new-user counts. EXAMPLES: - What % of users return after 3 months? - Show me our retention curve - What's our account churn rate over the last 6 months? - How often do accounts that created a dashboard keep creating dashboards? - How well do we retain first-time users of this feature? - What's the retention curve for our Onboarding product area? RETURNS: - scope, entityId, cohortMode, unit, periodType: echoed query parameters - retentionCurve: list of {period, periodLabel, activeCount, multiSession, retentionRate} sorted by period - summary: {totalCohortSize, avgRetentionRate, finalRetentionRate}

Creates a new feedback item in this subscription's qualitative customer feedback system. Returns the ID of the created feedback item. Before calling this tool, you should list product areas, and assign the feedback to the appropriate product area. Then, before submitting the feedback, repeat all non-empty fields back to the user for confirmation, resolving IDs to human-readable names. USE FOR: When the user explicitly asks you to submit product feedback, feature requests, bug reports, etc. on behalf of a customer to the qualitative customer feedback system EXAMPLES: - Create feedback for this: [paste text] - Log a feature request for dark mode support - Submit feedback that the export CSV button is confusing - Capture this bug report about broken pagination - Record this customer's request for a Slack integration RETURNS: - ID of the created feedback item This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Creates a new draft Pendo guide from raw HTML content. Each entry in rawHtmls becomes one step in the guide. Returns the guide ID and a direct URL to edit the guide in Pendo. USE FOR: When the user has generated HTML guide content (e.g. from the pendo-guide-creator skill) and wants to create a real Pendo guide from it EXAMPLES: - Create a guide from this HTML - Send this guide to Pendo - Publish these HTML files as a Pendo guide - Turn my generated guide steps into a real Pendo guide NOT FOR: Listing, searching, or querying existing guides - use listGuides or searchEntities instead RETURNS: - Guide ID of the newly created draft guide - Direct URL to the guide in the Pendo UI This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Creates a new product idea - a product enhancement or new feature request - for this subscription, and returns the ID of the created idea. Every idea must be associated with at least one application; if the user hasn't said which, resolve the correct appId(s) first. Optionally assign the idea to one or more product areas by their IDs. Before submitting the idea, repeat all non-empty fields back to the user for confirmation, resolving IDs to human-readable names. USE FOR: When the user explicitly asks you to log a product idea or feature concept into the ideas backlog EXAMPLES: - Create an idea for this: [paste text] - Log a product idea for a dark mode theme - Add an idea to support CSV exports on the reports page - Capture this idea about a bulk-edit workflow RETURNS: - ID of the created idea This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Creates a draft Orchestrate journey from templateJson and returns journeyId. Use when the user wants a custom multi-email journey that createOrchestrateJourneyFromTemplate cannot express (single built-in template only). Build templateJson to match the JSON Schema on the templateJson parameter in this tool's inputSchema. After create, call getOrchestrateJourneySteps to verify the draft graph. This tool creates the graph layout (email steps, Conditional Split nodes with Yes and No branches, wait days between steps). Segment targeting, send schedule, conversion goals, email HTML body, and the condition of each Conditional Split are not set here - configure them in the Orchestrate UI after create. USE FOR: Creating a draft Orchestrate journey when the user wants a custom multi-email journey with Conditional Splits. EXAMPLES: - User wants a welcome email then a follow-up email 3 days later: read templateJson inputSchema, build messageGraph with two Message nodes, set messageData.durationInDays to 3 on the first Message node (the wait before the follow-up) and durationInDays to 1 on the last Message node, call createOrchestrateJourneyFromJson for app 12345 - User wants email A then a Conditional Split where the Yes branch goes to email B and the No branch to exit: add a nodeType Condition node with edgeType Yes and edgeType No edges after email A; configure the condition in the Orchestrate UI - User wants an initial email, then a Conditional Split where the Yes branch sends email 1 and the No branch sends email 2: build Start -> Message (initial) -> Condition with edgeType Yes to a Message named email 1 and edgeType No to a Message named email 2, each branch ending at its own Exit node; set messageData on all three Message nodes; configure the condition in the Orchestrate UI NOT FOR: Built-in single-email create (use createOrchestrateJourneyFromTemplate). Guide nodes. Updating graph after create. Setting segment targeting, send schedule, conversion goal, email HTML content, or the condition of a Conditional Split in templateJson. Activating a journey. WORKFLOW: 1. Confirm multi-email need (not createOrchestrateJourneyFromTemplate). 2. Construct templateJson from templateJson inputSchema. 3. Create. 4. getOrchestrateJourneySteps to verify. RETURNS: - journeyId: id of the created draft journey - journeyUrl: direct URL to the journey in the Pendo UI - status: draft - validationReport: graph validation summary This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (Demo) Pendo Experience (6591622502678528)

Creates a draft Orchestrate journey from a built-in templateId and returns journeyId. Supply templateId only - the server applies a fixed messageGraph; do not send templateJson. Supported templateId values are listed in the templateId parameter enum in this tool's inputSchema. For custom multi-email journeys, use createOrchestrateJourneyFromJson (templateJson inputSchema on that tool). After create, call getOrchestrateJourneySteps to verify the draft graph. This tool only selects which built-in graph to apply. Segment targeting, send schedule, conversion goals, and email HTML body are not set here - configure them in the Orchestrate UI after create. USE FOR: Creating a draft Orchestrate journey from a built-in template (single email today). EXAMPLES: - Create a draft Orchestrate journey named 'Welcome email' with templateId mcpSingleEmailJourneyTemplate for app 12345 NOT FOR: Custom multi-email journeys (use createOrchestrateJourneyFromJson). UI layout ids from listOrchestrateJourneyTemplates. Updating graph after create. Setting segment targeting, send schedule, conversion goal, or email HTML content. Activating a journey. WORKFLOW: 1. Confirm single built-in template is enough (not createOrchestrateJourneyFromJson). 2. Call with a templateId from inputSchema enum. 3. getOrchestrateJourneySteps to verify. RETURNS: - journeyId: id of the created draft journey - journeyUrl: direct URL to the journey in the Pendo UI - status: draft - validationReport: graph validation summary This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (Demo) Pendo Experience (6591622502678528)

Permanently deletes a saved Pendo visitor segment. Confirm the segment name and id with the user before submitting - this cannot be undone from the agent. USE FOR: Removing a segment the user no longer needs. If the segment is referenced by a guide, another segment, or a saved report, the delete is rejected and the referencing entity is named in the error so the user can detach it first. Segments that back a feature flag must be deleted via the feature-flag tools. EXAMPLES: - Delete segment abc123. - Remove the "Old trial users" segment. RETURNS: - id: the deleted segment's id. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Fetch raw devlog events for a visitor or session, including HTTP request/response details, log levels, messages, and stack traces. Supports cross-tab replays via recordingSessionIds (array) to fetch devlogs across multiple browser tabs. Accepts a clipId or the individual fields (recordingSessionId, appId, visitorId, accountId, startTime, endTime) that identify a recording. When clipId is provided, the tool looks up the clip to resolve visitorId, accountId, appId, recordingSessionId, and time range automatically. If the user provides a session replay URL, parse the recordingSessionId from the URL path and query parameters (startTime, endTime, visitorId, accountId, appId) before calling this tool; for cross-tab replays, also parse the comma-separated crossTabSessions query parameter and pass the path ID plus those values in recordingSessionIds. USE FOR: Investigating developer console logs, network errors, or HTTP activity captured during a session replay. Use when the user provides a session replay URL (parse the URL yourself to extract params), a clip ID, or when the recordingSessionId, appId, visitorId, accountId, and time range for a session are already known. For cross-tab replays, pass the path recordingSessionId plus the comma-separated crossTabSessions query-param values as recordingSessionIds to fetch devlogs across all tabs in a single call. EXAMPLES: - Show me devlogs for this session replay: https://<hostname>/s/123/replay/player/abc - Show network requests captured in clip https://<hostname>/s/123/replay/clip/saved/xyz - What HTTP errors occurred during visitor john's session? - Fetch devlogs for clip ID abc-123 - Find devlog errors for account acme-corp - What API calls did this visitor make during their session? NOT FOR: Listing or discovering session replays. General page/feature/track-event analytics unrelated to a specific session recording. RETURNS: - Devlog events including subType (console/network), log level, message, stack trace, HTTP method, request URL, status code, request/response headers and bodies, recordingSessionId, and recordingId for cross-tab attribution. Limited to 100 events. The maximum time range for this tool is 31 days. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Get usage analytics for one known page, feature, or track event ID over a date range, including page views, feature clicks, event counts, and unique visitor ('people') and account counts. Returns {summary, rows}: summary has total events, unique visitors, unique accounts (and for pages/features, frustration counts; pages also include uTurnCount); rows are per-visitor or per-account breakdowns with events, time on entity, and days active, sorted and limited. Optionally include metadata fields for each returned visitor or account with select. Audience can be scoped via visitorIds OR an inline segmentPipeline (mutually exclusive), and/or filtered to a single accountId. USE FOR: Scalar 'how many people viewed/clicked/used it' totals and top-N visitor or account questions over a window for one known page, feature, or track event ID. EXAMPLES: - How many page views did page X get last month? - Top 20 visitors by time on page X in the last 30 days - Top 50 accounts by usage of feature Y last quarter - How many rage clicks did feature Y have last week? - Show the top 20 visitors by time on page X last month with their email and role NOT FOR: Looking up an entity ID from its name, or ranking multiple entities against each other. WORKFLOW: When the user names a page, feature, or track event but does not provide its ID, call listCountables to resolve the name to an ID, then call entityUsage with that ID. Do not substitute aggregateEntityUsage for this lookup: its limited ranking may omit the named entity. RETURNS: - summary: totalNumEvents, totalNumVisitors, totalNumAccounts (pages/features also: totalErrorClickCount, totalRageClickCount, totalDeadClickCount; pages also: totalUTurnCount) - rows: events, timeOnEntityInMinutes, daysActive per visitor or account (pages/features also: errorClickCount, rageClickCount, deadClickCount; pages also: uTurnCount); per-account rows also include numVisitors; select adds requested metadata fields

Get usage of a page, feature, or track event over time. Groups events into buckets of the requested period (daily/weekly/monthly) and returns one row per bucket with all available metrics. Pages get the full set (visitors, accounts, events, timeOnEntity, averageTimeOnEntityPerVisitor (duration object {seconds, display}), errorClickCount, rageClickCount, uTurnCount, deadClickCount). Features drop the time-derived metrics and uTurnCount. Track events drop all click-level frustration counts. minEvents restricts every bucket to the visitors with at least that many events on the entity in that bucket, applied independently per bucket. For a specific entity, the query can filter or group by custom event properties or event-time historical metadata. For whole-app usage over time (not a specific entity), use the appUsageTimeSeries tool instead. USE FOR: Trend questions over a window - e.g. 'how did feature X usage change over the last 12 weeks?', 'are rage clicks on page X trending up?'. With minEvents, tracks a per-bucket event threshold over time - e.g. 'visitors using feature X at least twice a month'. EXAMPLES: - How did feature X usage change over the last 12 weeks? - Are rage clicks on page X trending up over the last 30 days? - How did visitor counts trend for this account last month? - Total page views per week across all pages over the last quarter - How many visitors used feature X at least twice in each of the last six months? RETURNS: - meta.dateRange: resolved startDate and endDate (YYYY-MM-DD) - meta.period: echoed bucket size (daily|weekly|monthly) - meta.metrics: list of metric names returned per bucket - rows: one entry per time bucket with bucket (YYYY-MM-DD or YYYY-MM), startTime (timestamp object {iso, display}), and metric values; numeric metrics zero-fill and averageTimeOnEntityPerVisitor (duration object {seconds, display}) defaults to 0s for empty buckets - property-grouped rows contain propertyValues, with one stable range-ranked group set zero-filled across every bucket - sumEventProperty optionally adds a numeric event-property total per bucket and property group, zero-filled for empty buckets

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. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Returns the configuration for a given AI agent: its name, description (a human-authored summary of the agent's role and purpose, not its LLM system prompt), model preset, type, and the tool names and descriptions it has used in the specified date range. The agent config section comes from the stored agent record. The tools section is derived from runtime events in the date range and may be empty if the agent had no activity. USE FOR: Fetching the static configuration and runtime tool inventory of an AI agent. Use before analyzing issues or generating fix briefs to understand what the agent is configured to do and which tools it calls. EXAMPLES: - What is my agent's configured role and purpose? - Which tools does my agent have access to? - What model does agent X use? - Show me the full config for this agent before I debug it NOT FOR: The agent's actual LLM system prompt - this tool does not have access to that. Aggregated usage metrics, issue clusters, or conversation analysis - use the agent analytics tools for those. RETURNS: - Two labeled CSV sections: - [agent_config]: name, description (human-authored role/purpose summary, not the LLM system prompt), preset (model), type - one row. - [tools]: toolName, toolDescription - one row per tool seen in the date range; empty section if no activity found. The maximum time range for this tool is 90 days.

Fetches a grounding document that describes the current contents of a Pendo product resource so the LLM can reason about it. Today the only supported resource is a Pendo Space - a collaborative canvas of product artifacts (pages, features, guides, notes, etc.) curated by a team. Pass `resourceType` (e.g. "space") and `resourceId` (the id of that resource, e.g. a space id) to retrieve the document. Call `listSpaces` first if you need to discover a space id. The response is JSON returned by the Spaces service and typically contains a markdown `body` plus a `schema` describing the resource's contents; do not assume a shape beyond what the response declares. Use `frameId` to scope a space's context to a single frame on the canvas (and items whose parent is that frame) - useful when the user's UI is focused on that frame; omit `frameId` for the full space.

Get the configuration details of one page, feature, track event, or guide by ID. Does not include any usage or metrics. USE FOR: Understanding an entity before querying or acting on it. The name of any entity, reading a page's URL rules, the element a feature targets and the page it sits on, or a countable's event properties.For a guide, get its steps in order, each with its step ID and the interactive elements on it. EXAMPLES: - What is the page with ID abc123 and what URLs does it match? - Which element does feature xyz789 target, and what page is it on? - What event properties can I break down track event def456 by? - What are the step IDs and element IDs for guide ghi789? - Which buttons are on the second step of this guide and what do they do? NOT FOR: Usage, metrics or counts of any kind. Searching for an entity when you don't know its ID. RETURNS: - id, type, name, description, appIds, createdAt, lastUpdatedAt for every entity type. - eventPropertyNames: names of event properties attached to pages, features and track events. - page: rules and excludeRules (the URL rules that define the page). - feature: elementPathRules (CSS selector rules identifying the tagged element), and the pageId and pageName it is scoped to. - trackEvent: trackTypeRules (the event names that count towards it). - guide: state, launchMethod, and steps in the order they appear. Each step has id, name, and the pageId and elementPathRule it attaches to when it targets one. - guide steps[].polls: id, question and type ('PickList', 'NumberScale', 'FreeForm', 'NPSPoll', ...) per poll. For the answers given, use guidePollResponses. - guide steps[].elements: the buttons, close buttons and links on the step, each with uiElementId, text and actions ('Next Step', 'Dismiss Guide', 'External URL', 'Go to Step (2)', ...).

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' This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Retrieves the original, raw customer feedback matching the given filters. Each item includes id, title, description, status, and info about the account and visitor which gave the feedback. status is an object with id, name, and color fields. account is an object with id and name. visitor information is available via the createdBy and onBehalfOf objects. Each item also includes: assignee (email of the assigned user); labels, apps, and productAreas (each a list of {id, name} objects); productAreas identify the product areas the feedback is tagged to; lastUpdatedAt (epoch milliseconds, same format as createdAt); linkedIdeas (a list of the ids of ideas the feedback is linked to); importance ('Must Have', 'Nice to Have', or 'Not Interested'); and source (where the feedback originated, e.g. Portal, Salesforce, NPS). 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. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Retrieves product ideas submitted by internal product employees which describe product enhancements and new features matching the given filters. Each item includes: id, title, description, createdAt, status, effort, impact, voteCount, accountVoteCount, and votes. Each item also includes: assignee (email of the assigned user); labels, apps, and productAreas (each a list of {id, name} objects); lastUpdatedAt (epoch milliseconds, same format as createdAt); and linkedFeedbackItems (list of feedback item IDs linked to this idea). status is an object with id, name, and color fields. voteCount is the number of positive votes cast for the idea ('Must Have' and 'Nice to Have') - use this as the primary signal of demand when ranking or comparing ideas. accountVoteCount is the number of unique accounts that cast positive votes - use this to indicate breadth of interest across customers; when accountVoteCount is much lower than voteCount, it means a small number of accounts voted multiple times. 'Not Interested' votes are excluded from voteCount, accountVoteCount, and the votes list by default. Pass includeNotInterestedVotes=true when the user asks to see 'Not Interested' votes or wants all vote counts including 'Not Interested'. Each vote includes: importance ('Must Have' or 'Nice to Have'; 'Not Interested' when includeNotInterestedVotes is true); voterId (the ID of the person who cast the vote); voterType ('Visitor' in most cases, 'User' for internal users - only mention this to the user when the value is 'User'); accountId (the account associated with the vote). A maximum of 30 items will be returned, however there may be more matching the filter set. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) Pendo Free Roadmaps Test (5914217715662848) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Get full details for a single Orchestrate email campaign by ID. Returns any orchestrate email the caller can access, including journey message emails when you already have the email ID. Use list_orchestrate_emails to discover orchestrate email campaigns; use this tool when you have a specific email ID. USE FOR: Inspecting an Orchestrate email's configuration, status, schedule, audience, and template-level fields when you already have the email ID (standalone or journey-linked). EXAMPLES: - Get email details for email 123 - Show orchestrate email config for abc - What is email xyz? - Show me full details for this orchestrate email - Get email campaign by ID NOT FOR: Listing or searching emails without an ID (use list_orchestrate_emails). Email performance metrics like sends, opens, or clicks (use get_orchestrate_email_metrics). Journey configuration without a journey ID (use list_orchestrate_journeys or get_orchestrate_journey). WORKFLOW: Call list_orchestrate_emails to discover email IDs, then call this tool with emailId. RETURNS: - Orchestrate email campaign configuration for agents: name, status (UI lifecycle label for standalone emails), subject, provider (Pendo, HubSpot, Marketo, or Eloqua), email settings, audience, schedule start time, and lifecycle timestamps (publishedAt, triggeredAt, executedAt) - attributes includes journeyId when the email belongs to a journey - Integration IDs (HubSpot, Marketo, Eloqua) when the email uses an external provider This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Get performance metrics for a single Orchestrate email. Returns delivery, unique opens, unique clicks, bounces, unsubscribes, and spam complaints for Pendo emails within the requested date range. Matches Orchestrate email overview metrics in the UI. Email-level aggregates only: this tool does not return per-visitor metrics or identify which visitors sent, opened, clicked, bounced, or unsubscribed. For per-visitor engagement use getOrchestrateEmailVisitors. Use listOrchestrateEmails to discover email IDs. USE FOR: Analyzing Orchestrate email performance when you already have the email ID. Questions about sends, delivery rate, open rate, click rate, or bounces. EXAMPLES: - How did email abc perform last month? - Show delivery and open rates for orchestrate email 123 - Get email metrics for email 123 between 2025-01-01 and 2025-01-31 NOT FOR: Listing emails without an ID (use listOrchestrateEmails). Per-visitor email engagement (who opened, clicked, bounced, or unsubscribed - use getOrchestrateEmailVisitors). Journey-level metrics (use getOrchestrateJourneyMetrics). Per-step metrics for every step of a journey at once (use getOrchestrateJourneyStepMetrics). Email configuration (use getOrchestrateEmail). WORKFLOW: Call listOrchestrateEmails to discover email IDs, then call this tool with emailId and a date range. RETURNS: - Top-level emailId, startDate, endDate, plus metrics: unique-visitor counts (sent, delivered, opened, clicked, bounced, unsubscribed, complaint) and rates (deliveryRate, openRate, clickRate, clickToOpenRate, bounceRate, unsubscribeRate, complainRate). No rows or visitorId. - Rates as percentages: openRate and clickRate are % of delivered; deliveryRate, bounceRate, unsubscribeRate, and complainRate are % of sent; clickToOpenRate is % of opened. Bounce counts reflect hard bounces only (Permanent). The maximum time range for this tool is 367 days. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Get full details for a single Orchestrate journey by ID. Returns curated journey configuration including audience, status, scheduling, and goal. Does not include the step graph, linked message/email IDs, or email settings (those live on each email; use getOrchestrateEmail). Use listOrchestrateJourneys to discover journey IDs. USE FOR: Inspecting an Orchestrate journey's configuration, audience, status, scheduling, and goal when you already have the journey ID. EXAMPLES: - Get orchestrate journey details for journey 123 - Show me the full config for this orchestrate journey - What is orchestrate journey xyz? - Get orchestrate journey campaign by ID NOT FOR: Listing or searching orchestrate journeys without an ID (use list_orchestrate_journeys). Email campaign details or email settings (use get_orchestrate_email). Journey step graph or linked message/email IDs (use get_orchestrate_journey_steps). WORKFLOW: Call list_orchestrate_journeys to discover journey IDs, then call this tool with journeyId. RETURNS: - Journey configuration for agents: name, status (UI lifecycle label), audience, goal, and scheduling - Lifecycle timestamps (createdAt, updatedAt, publishedAt, firstPublishedAt) - App IDs, step count, audience targeting, and control-group settings This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Get journey-level performance metrics for a single Orchestrate journey. Covers visitor entry and exit counts and - for journeys with a goal - goal attainment. Returns journey-wide aggregates only: no per-step, per-message, or per-visitor breakdown. USE FOR: Analyzing overall Orchestrate journey performance when you already have the journey ID. Questions about visitors entered, visitors completed, or (for journeys with a configured goal) goal attainment. EXAMPLES: - How is orchestrate journey 123 performing? - How many visitors entered and exited orchestrate journey abc? - What is the goal attainment rate for this orchestrate journey? - Show journey metrics for journey 123 between 2025-01-01 and 2025-01-31 NOT FOR: Per-step or per-message metrics within the journey (use getOrchestrateJourneyStepMetrics). Per-visitor engagement lists for a single journey step (use getOrchestrateJourneyStepVisitors). The journey step graph or structure (use getOrchestrateJourneySteps). Metrics for a single email by ID (use getOrchestrateEmailMetrics). Per-visitor journey membership (which visitors entered or exited). Listing journeys without an ID (use listOrchestrateJourneys). Journey configuration (use getOrchestrateJourney). WORKFLOW: Call listOrchestrateJourneys to discover journey IDs, then call this tool with journeyId, optionally with startDate and endDate. RETURNS: - visitorsEntered: unique visitors who entered the journey - visitorsCompleted: unique entered visitors who finished the journey by reaching an Exit step or aging out (for required-goal journeys, achieving the goal also marks completion). This is a journey-exit count, NOT goal attainment - use visitorsAchievedGoal for that. For optional-goal journeys, achieving the goal does not by itself mark a visitor completed, so an achiever is counted here only once they later reach an Exit or age out - visitorsAchievedGoal: unique entered visitors who achieved the journey goal, computed independently of completion tagging (omitted for journeys with no goal). Because attainment is tracked separately from completion, this can briefly exceed visitorsCompleted while achievers are still in-flight - it is not a stable relationship - goalAttainmentRate: visitorsAchievedGoal as a percentage of visitorsEntered (omitted for journeys with no goal or when no visitors entered) - goal: the journey goal definition (type, itemType, itemId, isGoalOptional); omitted for journeys with no goal - When startDate and endDate are provided, visitorsEntered and visitorsCompleted are limited to entry/exit within that range; otherwise cumulative totals are returned - visitorsAchievedGoal and goalAttainmentRate are always cumulative (the backend goal-achievement definition is not time-bounded) and are omitted when a date range is provided; request without a date range to retrieve them The maximum time range for this tool is 367 days. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Get per-step performance metrics for a single Orchestrate journey by ID. Returns one entry per message step in execution-flow order, matching the per-step columns on the Orchestrate journey metrics page. Every count is scoped to journey entrants - visitors who entered THIS journey within the requested date range - not campaign- or guide-wide activity, so the numbers reconcile with the journey metrics page. Email steps include delivery, unique opens, unique clicks, bounces, unsubscribes, and spam complaints among those entrants. Guide steps include the journey-page guide engagement columns: viewed (entrants who saw the guide) and clicked (entrants who interacted with it), plus the derived clickRate. Survey and VOC email steps are not Orchestrate journey deliverables and carry metricUnavailableReason instead of email metrics. Other unsupported step types carry no metrics and a metricUnavailableReason instead. Use getOrchestrateJourneySteps for the full step graph, getOrchestrateEmailMetrics for a single standalone email, getOrchestrateJourneyMetrics for journey-level goal attainment, and guideMetrics for deep single-guide analytics (completions, dismissals, polls, NPS, goal adoption). USE FOR: Comparing how each step of an Orchestrate journey performed side by side: email delivery/open/click rates and guide viewed/clicked engagement per step, as shown on the journey metrics page. EXAMPLES: - How did each step in orchestrate journey 123 perform last month? - Show per-step open and click rates for orchestrate journey abc between 2025-01-01 and 2025-01-31 - Which email step in this orchestrate journey had the best open rate? - Compare guide view and click counts across the steps of orchestrate journey 123 NOT FOR: The journey step graph or message IDs without metrics (use getOrchestrateJourneySteps). Metrics for a single email by ID (use getOrchestrateEmailMetrics). Deep single-guide analytics like completions, dismissals, polls, NPS, or goal adoption (use guideMetrics). Journey-level rollup metrics or per-step journey-goal attainment (use getOrchestrateJourneyMetrics). Per-visitor step engagement lists (use getOrchestrateJourneyStepVisitors). WORKFLOW: Call listOrchestrateJourneys to discover journey IDs, then call this tool with journeyId and a date range to get per-step metrics. RETURNS: - steps: an array of message steps in execution-flow order. Each step has: stepId, stepType, position, messageId, messageType, provider (plus the per-step metric fields below) - steps[].position: 0-based index of the step in the journey's execution flow across ALL nodes (start/exit/condition nodes also consume positions, so message-step positions are non-contiguous); cross-reference with getOrchestrateJourneySteps - steps[].email: per-step email metrics among journey entrants (sent, delivered, opened, clicked, bounced, unsubscribed, complaint and the derived rates; openRate/clickRate are of delivered); present only for email steps. The page surfaces opened and clicked per step; the remaining counts are the same entrant-scoped events - steps[].guide: per-step guide engagement matching the journey metrics page - viewed (journey entrants with a guide-seen event), clicked (journey entrants with a guide-interaction event), and clickRate (clicked/viewed %); present only for guide steps. Completions, dismissals, polls, NPS, and goal adoption are not per-step here - use guideMetrics - steps[].metricUnavailableReason: present when both email and guide are null - step_type_not_supported (unsupported step type, or survey/VOC email), or message_not_found (linked email/guide missing) - steps[]: every count is scoped to visitors who entered this journey within [startDate, endDate]; a step the caller cannot access (no view permission on the message's application) returns a zero-valued metrics block, not an error or a missing step, matching the journey metrics page - journeyId, name, status, startDate, endDate, and stepCount (number of message steps returned) are top-level fields for orientation The maximum time range for this tool is 367 days. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Get the ordered step graph (nodes and edges) for a single Orchestrate journey by ID. Returns the journey's structure only: each step's type, position, and linked message IDs, plus the edges connecting the steps. Does NOT return per-step metrics (sends, opens, clicks); use getOrchestrateJourneyStepMetrics for those. Use listOrchestrateJourneys to discover journey IDs and getOrchestrateJourney for journey-level config. USE FOR: Inspecting the ordered steps of an Orchestrate journey: step types (start, message, condition, exit), the order/position of each step, the message ID and message sub-type (email or guide) of each message step, durationInDays (Email: days until the next step; Guide: days the guide stays active/eligible), and the edges that connect the steps. EXAMPLES: - Show the steps of orchestrate journey 123 - What messages are in this orchestrate journey? - List the steps and their order for orchestrate journey xyz - What is the structure of this orchestrate journey? - Which guide/email is sent at each step of orchestrate journey 123? NOT FOR: Per-step performance metrics like sends, opens, or clicks (use getOrchestrateJourneyStepMetrics). Journey-level configuration such as audience, goal, or scheduling (use getOrchestrateJourney). Listing journeys without an ID (use listOrchestrateJourneys). Email content (use getOrchestrateEmail). WORKFLOW: Call listOrchestrateJourneys to discover journey IDs, then call this tool with journeyId to retrieve the journey's steps and how they connect. Use messageId (emailId/guideId) from a step when calling getOrchestrateJourneyStepMetrics or getOrchestrateJourneyStepVisitors; stepId is a fallback graph node id. RETURNS: - steps: journey nodes in execution-flow order (same order the Orchestrate editor renders, walking from the start node; a condition's Yes branch precedes its No branch). position is the 0-based index in that flow order - name: for message steps this is the linked email/guide's display name (as shown in the Orchestrate editor); for other steps it is the node's label and may be empty - message steps additionally include messageId, messageType (Email | Guide), provider, durationInDays (Email: days until the next step; Guide: days the guide stays active/eligible for the visitor) - edges: the connections between steps (from, to, edgeType where edgeType is Regular for linear steps or Yes/No for condition branches) - startNodeId and stepCount (number of message steps) for quick orientation This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (Demo) Pendo Experience (6591622502678528)

Returns a single Pendo visitor segment by ID, including its name, definition in LLM-friendly DSL form, and optionally the guides, Orchestrate journeys, reports, compound segments, and session-replay apps that reference it. USE FOR: Inspect or read a saved segment's rules. Use when you need the current definition before modifying it, or when you need to know where a segment is in use. EXAMPLES: - Show me the definition of segment abc123. - What guides are using segment xyz789? RETURNS: - id: the segment ID. - name: human-readable segment name. - description: optional segment description (omitted if empty). - shared: whether the segment is publicly shared. - summary: plain-English description of the segment rules with entity names resolved. - definition: the segment rules in DSL form - same format accepted by create and update Segment tools. Omitted for segments authored outside the agent workflow that use features the DSL can't represent, and for segments with no rule-based definition (e.g. segment-flag or auto-managed segments). - note: only set when definition is omitted; explains why the segment can't be represented as DSL. Such segments are readable but not editable via the agent's update path. - usedBy: guides, Orchestrate journeys, reports, compound segments, and session-replay apps that reference this segment. Only present when includeUsedBy is true.

Dashboard-consistent, visitor-weighted Guide Effectiveness metrics for every guide, with optional comparison across up to 4 segments. Returns one row per guide plus an overview summary of averages across the matched set. Rates are visitor-weighted exactly as the Guide Effectiveness dashboard computes them: engagement = distinct visitors who interacted / distinct visitors who viewed; completion = distinct visitors who reached the last step / distinct visitors who reached the first step (multi-step guides only); goal adoption = converted visitors / total visitors (guides with a conversion goal only). Every rate ships with its raw numerator and denominator so sample size is visible. Aggregates cover the whole date range (no time-series buckets). Use sortBy to rank guides by a chosen metric, ascending or descending. IMPORTANT: When presenting results to the user, always state the active filters alongside the data: date range, app (if specified), segment(s), status filter, and activation filter. This lets users verify exactly which data scope produced the numbers. USE FOR: Reporting guide effectiveness that matches the Guide Effectiveness dashboard (engagement %, completion %, goal-adoption %), and comparing those rates across up to 4 segments. EXAMPLES: - How effective are our guides over the last 30 days? - Compare guide engagement and completion between the power-users and trial segments - Which guides have the lowest completion rate this month? - Show goal adoption for guides that have a conversion goal NOT FOR: Simple cross-guide ranking by raw views/dismissals (use aggregateGuideMetrics). Deep single-guide analysis with polls, NPS, or step funnels (use guideMetrics). RETURNS: - meta: resolved dateRange (startDate/endDate), the segments compared, and guideCount - summary: per-segment overview - totalViews, totalFirstTimeViews, totalVisitors, engagementRate, completionRate, goalAdoptionRate - rows: one per guide with entityId, entityName, state, launchMethod, and per-segment metric blocks (rate + raw numerator/denominator). completionRate is null for single-step guides; goalAdoptionRate is null for guides without a conversion goal This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Get per-poll response distribution and per-visitor response rows for a guide's non-NPS polls. Returns {meta, summary, rows}: summary.polls lists each poll with its question and response distribution; rows are visitor-keyed and pivoted - one column per poll, null where a visitor did not respond. limit (default 10, max 200) applies to the pivoted visitor rows after joining across all polls. USE FOR: Answering questions about how visitors responded to polls in a guide: response distributions, individual visitor answers, and per-poll breakdowns. Not for NPS guide score metrics. EXAMPLES: - What were the responses to the poll in the onboarding guide? - Show me the response distribution for guide X polls - Which visitors answered 'Yes' to the helpfulness poll? - What did visitors respond to the polls in guide G last month? RETURNS: - meta.dateRange: resolved startDate and endDate (YYYY-MM-DD) - summary.polls: array of {pollId, question, distribution: [{response, count}]} for each poll. For free-text polls (open-ended responses), freeText is true and distribution is omitted because every response is unique - refer to the per-visitor rows instead. - rows: per-visitor with visitorId, accountId, browserTime, and one column per pollId (null if no response)

Get per-visitor or per-account usage breakdown for a single guide, with time-on-guide and new vs returning viewers. totalViews excludes continue-resumed guideSeen events to match the Pendo guide-details UI. For poll guides, includes per-poll response counts and response rate in summary. USE FOR: Per-visitor or per-account guide engagement - e.g. top visitors by time on guide, which accounts are completing vs dismissing, new vs returning viewer counts. With includeElements=true, also attributes each step's clicks to the individual buttons/links on it. EXAMPLES: - Top 20 visitors by time on guide X in the last 30 days - Which accounts are dismissing the onboarding guide most? - How many new vs returning viewers did the walkthrough have this month? - Show me per-visitor completion data for the tooltip guide - Is drop-off at step 3 happening via the CTA or by dismissing the guide? - Which button on the last step of the onboarding guide gets clicked most? RETURNS: - meta.dateRange: resolved startDate and endDate (YYYY-MM-DD) - summary: totalViews, completions, dismissals, uniqueVisitors, uniqueAccounts, completionRate, dismissalRate, viewsPerUser, avgTimeOnGuide, medianTimeOnGuide (duration objects {seconds, display}), newViewers, returningViewers, isPoll - summary.polls (poll guides only): per-pollId uniqueResponseCount and totalResponseCount - rows: per-visitor or per-account rows with views, completions, dismissals, daysActive, lastSeen (timestamp object {iso, display}), timeOnGuide (duration object {seconds, display}) (per-account rows also include uniqueVisitors), sorted and limited - steps (only when includeSteps or includeElements is true): per-step array in guide step order, each with stepId, name, uniqueVisitors, viewCount. Single-step guides return one entry; step views include continue-resumed views to match the Pendo step funnel. - steps[].elements (only when includeElements=true): the step's clicked buttons/links, highest clicks first, each with uiElementId, text, type ('Button', 'Close Button', 'Link', 'Task Item', 'Image', 'Swiped Left', 'Swiped Right' or 'Unknown'), actions (what the click does, e.g. 'Next Step', 'Dismiss Guide', 'External URL', 'Go to Step (2)'), clicks, uniqueVisitors, percentOfStepClicks. Compare an element's uniqueVisitors against its step's uniqueVisitors to attribute drop-off. Only clicked elements appear, and elements since removed from the step are still counted. The maximum time range for this tool is 367 days.

Links an existing feedback item to an existing idea, associating the customer evidence with the feature request. Votes from the feedback item are propagated to the idea's vote count. USE FOR: When the user explicitly asks to link, connect, or associate a feedback item with an idea, or vice versa EXAMPLES: - Link feedback abc123 to idea xyz456 - Connect this feedback to that idea - Associate idea xyz456 with feedback abc123 RETURNS: - Confirmation that the idea and feedback item have been linked This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

List the accounts that match a segment or fuzzy-search account display names or IDs. Segment mode (the default) defines the cohort with a segmentPipeline - either a saved Pendo segment reference or a full inline pipeline produced by the segment-builder tool. Search mode fuzzy-matches both the configured account display-name field and account ID. USE FOR: Listing the accounts in a segment/cohort, getting the account total, reading account metadata fields for those accounts, or resolving a named account to its ID without an application ID. EXAMPLES: - List the accounts in segment X - Which accounts match these metadata criteria? - How many accounts are in this segment? - Show me accounts in segment X with their ARR and company size - Find the account called Acme Inc RETURNS: - summary: numAccounts (the full segment total in segment mode; the number of returned matches in search mode) - rows in both modes: accountId, name, description when available, and requested fields in a metadata object keyed by metadata path (for example, "metadata.auto.lastvisit"), capped by limit - Search rows also include relevance. Only sufficiently relevant fuzzy matches are returned; unrelated accounts are omitted

Lists detected (emergent) issues in AI agent conversations with instance counts and conversation counts. Returns a table of issue name (clusterName), summary, instance count, and conversation count per issue, plus a sample of conversationIds/eventIds for deep-diving via agentAnalyticsIssueAnalysis. It also returns visitorIds and accountIds who experienced the issue. USE FOR: Finding what problems or issues users encountered when using AI agents (e.g., incorrect answers, refusals, errors). Use when the user asks about common issues, problems, or failures with a specific agent. Refer to an issue by its clusterName, never its numeric clusterId. EXAMPLES: - What are the common issues my users are encountering using my ABC agent in the last 30 days? - What problems have users been encountering when using Acme agent in my Acme application lately? - Have we seen reduced occurrences of issues with incorrect answers in our fooBar agent since last month? - What models are most often used when users face problems with the chat agent in ScramCorp app? NOT FOR: Use listUseCases for topic/cluster analysis of conversations. Use listAiAgents to get agent IDs and names first when the user has not specified an agent. RETURNS: - Table of issues: summary, instance count, conversation count, agentId, appId, visitorIds, and accountIds. - Sorted by conversation count descending. Limited to 500 rows. The maximum time range for this tool is 90 days.

Lists all AI agents that the user has access to. AI agents are conversational assistants that can be deployed on specific pages or app-wide. AI agents have the ability to collect conversations, cluster prompts by topics/use cases, and calculate metrics like conversation counts and rage prompt detection. This tool returns agent ids and names for usage with other related agent tools.

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.

List every metadata field declared on one already-identified designated business OBJECT (see listCustomObjects) - the fields customers send on metadata events for that object (e.g. 'type', 'isShared'), the same schema accountMetadataSchema/visitorMetadataSchema expose for accounts/visitors. Empty metadataSchema means the customer has never sent metadata events for this object. USE FOR: The user asks what metadata fields, properties, or dimensions are available on a business object; or resolveBusinessObject reported a term as unmatched (with or without a suggestion) and you need the full set of declared fields to find the right one, e.g. to offer the user a corrected choice. EXAMPLES: - What metadata fields are available on the 'reportId' object? - resolveBusinessObject said 'type' doesn't match reportId's schema - what fields does it actually have? NOT FOR: Checking whether SPECIFIC terms from a question belong to the object - use resolveBusinessObject, which also fuzzy-suggests close matches for an unmatched term without needing the full list. Listing which business objects exist in the first place - use listCustomObjects. Any per-object metric - use objectAnalyticsActiveCount, objectAnalyticsBreakdown, or objectEventBreakdown. RETURNS: - field, kind, group/metadataKind (historical objects only): the object identifier that was checked, echoed back exactly as it should be passed to objectAnalyticsActiveCount, objectAnalyticsBreakdown, or objectEventBreakdown. - metadataSchema: every declared metadata field on this object, keyed by its normalized field name, with type/cardinality/sample values - empty when the customer has never sent metadata events for it. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

listCountables is a tool to find, search, look up, or list pages, features, or track events by name and return their entity IDs. These entities are collectively called "countables" - the tagged elements and custom events that Pendo tracks in your application. Use the type parameter to select which kind to list. This is the entity lookup tool to use before single-page, single-feature, or single-track-event usage analytics when the user provides a name instead of an ID. Relevant analytics questions include page views, feature clicks, event counts, unique visitor or "people" counts, unique account counts, time on page, frustration clicks, and other entity usage metrics. The trackEvent type corresponds to what other tools call trackType or TrackType. Supports search via the search param with a searchType selector: "semantic" for natural-language queries ranked by meaning, "fuzzy" for keyword matching on names and descriptions, or "substring" for case-insensitive containment match on name. Both search and searchType are required together. For features, pageId restricts discovery to features associated with one known page. Offset is ignored when search is used; use limit to control result count. USE FOR: Resolving a named page, feature, or track event to its ID before calling entityUsage; listing features associated with a page; listing or browsing countables by name; auditing what is tagged in an app; semantic, fuzzy, or substring search for countable entities. EXAMPLES: - List all pages - Show me features for this app - Which features are associated with page X? - List track events matching 'checkout' - Find pages with 'dashboard' in the name - What track events are defined? - Find features related to user onboarding - Search for pages about checkout flow - Find the ID for 'Page X' before checking how many people viewed it NOT FOR: Listing guides. Listing product areas. Usage analytics, click counts, visitor counts, or activity rankings. WORKFLOW: For analytics about one named entity, search here first. Prefer searchType='substring' with the entity name exactly as the user supplied it; if that finds no match, retry with searchType='fuzzy' or 'semantic'. Then pass the matching ID to entityUsage. Do not conclude that the entity does not exist merely because it was absent from an aggregateEntityUsage ranking, which returns only a limited set of ranked entities. RETURNS: - Summary info for each matching entity: ID, name, description, and eventPropertyNames (custom property names attached to the countable). Pages also include URL rules and exclude rules. Features include pageId and elementPathRules (CSS selector rules identifying the tagged UI element). - When search is used: results include a relevance score

List a subscription's designated business OBJECTS - the custom event properties that have been marked as analyzable business entities (e.g. 'dashboardId', 'venueId', 'orderId'). Returns each object's underlying event property name (its field) and kind, which are exactly the objectProperty argument the objectAnalytics* tools take, plus its customer-facing displayName/description when an admin has set them. Objects are NOT pages, features, or track events. USE FOR: Discovering which business objects a subscription has, and grounding an ambiguous entity name before an objectAnalytics* call. Use it when a name could mean either a business object or a page/feature (e.g. 'dashboards') to confirm the object exists and get the exact objectProperty.field to pass to objectAnalyticsActiveCount or objectAnalyticsBreakdown. The search term matches the object's field name, displayName, or description, so a customer-facing label (e.g. 'Reports') resolves even when it doesn't textually overlap the underlying field key (e.g. 'rp_obj_4471'). EXAMPLES: - What business objects can I analyze in this subscription? - Is 'dashboard' a business object or a page? - List the custom objects available for Object Analytics - Which object property identifies venues? NOT FOR: Listing pages, features, or track events - use listCountables. Counting or ranking objects, or any per-object metric - use objectAnalyticsActiveCount or objectAnalyticsBreakdown. This returns only the object property definitions, never metrics. Confirming whether a METADATA TERM (e.g. 'size', 'region', 'category') actually belongs to a specific object's own schema - use resolveBusinessObject. WORKFLOW: To resolve a specific object by name, prefer searchType='substring' with the name as the user gave it; if that returns no match, retry with searchType='fuzzy' to survive a misspelling or a loosely-worded label. Choosing the mode is your call - the server never falls back automatically. If the question references metadata terms rather than - or in addition to - one of the object names returned here, do not assume a term belongs to whichever object seems closest. Pick the most likely candidate object from this list (asking the user first if more than one plausibly fits) and call resolveBusinessObject with that object's field (and kind/group/metadataKind for historical objects) plus the terms, to confirm they're actually part of its schema before running an objectAnalytics* query. RETURNS: - One entry per designated object property: field (the event property name to pass as objectProperty.field, e.g. 'dashboardId'), and kind ('event' or 'historical'). - displayName and description: the customer-facing label and description set by an admin, when present. Absent when never set. - For historical (promoted visitor/account/parentAccount metadata) objects, group and metadataKind are also included. - promotedAt (epoch milliseconds): when the property became an analyzable object. This is the activation floor the objectAnalytics* tools apply internally - events before it are excluded - so use it to caveat data availability or pick a start date that postdates promotion. - matchedFields (substring search only): which of field/displayName/description the term matched, so you can see why an object was returned. A match on field or displayName is a strong signal; a description-only match is weaker (descriptions are free-form sentences, so the term may appear incidentally) - prefer field/displayName matches when ranking candidates. - relevance (fuzzy search only): a similarity score for ranking - higher means a closer match to the search term. Rank candidates by it; matchedFields is absent in this mode. This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

Returns all guide categories for a subscription - their IDs, names, and platform (web or mobile). Each category exists as a paired web+mobile variant with distinct IDs; use the platform filter to narrow results. USE FOR: Finding a guide category ID to associate a guide with a category, or enumerating which categories exist for a subscription. Pair with listGuides to see which guides belong to each category. EXAMPLES: - What guide categories are set up for this subscription? - List all guide categories - Show me web guide categories - Which mobile guide categories exist? - What are the available guide categories and their IDs? NOT FOR: Guide analytics or engagement metrics - use guideMetrics or guideUsage instead. To search or list guides themselves, use listGuides. RETURNS: - Array of guide categories, each with: id, name, platform (web or mobile)

List guide experiments (guide A/B tests) and return their IDs. A guide experiment splits an audience across two or more variants to compare which performs better. Each variant is either a guide or the control group (no guide, shown as isControl). Experiments move through states: draft (not started), active (running), needsReview (finished, awaiting a decision), completed. This is the lookup tool for resolving an experiment name to its ID, and for finding which experiment a guide is part of - filter by guideIds to answer "is this guide being A/B tested?". It returns experiment configuration only, not experiment results. USE FOR: Listing or browsing guide experiments; resolving an experiment name to its ID; checking which experiment a guide belongs to (guideIds); listing experiments in a given state, such as which experiments are currently running. EXAMPLES: - What guide experiments do we have? - Which guide experiments are currently running? - Is guide abc123 part of an experiment? - Show me guide experiments that have completed - List guide experiments for app 12345 NOT FOR: Guide content, targeting, or scheduling - use listGuides. Guide views, completion, or conversion metrics - use guideEffectivenessMetrics or aggregateGuideMetrics. Experiment results, audience rules, conversion goals, or which variant won - this tool returns configuration only. RETURNS: - Array of experiments with: id, name, description, state, appId, startTime, endTime - variants per experiment: variant name, guideId, groupSize (percentage of the audience assigned to the variant, summing to 100), and isControl for the control group, which has no guide FILTERING OPTIONS: - guideIds: only experiments that have one of these guides as a variant - state: only experiments in this state - draft, active, needsReview, completed - appId: only experiments scoped to that application This tool is only available to be called for the following subscriptions: pendo-internal (5668600916475904) DanJ RC Pricing & Packaging Platform (5648856195530752) PENDO_SAMPLE_DATA_SUB (5739608213684224) (External Customer) Pendo Experience Sandbox (4691349476737024) (Demo) Pendo Experience (6591622502678528)

List the guide delivery order ("throttle order") for an app. When multiple guides are eligible to show at the same time, the delivery order determines which guide takes precedence. This tool returns the ordered list of guides for the given app. An app with no ordering set returns an empty list. Guides are capped by limit (default 50). totalGuides is the full ordering length; offset and returned describe the slice in guides. When returned < totalGuides the result is truncated - tell the user which range they're seeing (e.g. "showing 1-50 of 120") and use offset to page through the rest. PRESENTATION (follow exactly): For EVERY guide, show ALL SIX of these columns, always in this order: Guide Name | Status | Segment | Page | Guide Category | Product Area Show every column even when most guides share a value and even when a column has no values. Segment is the readable segment name (e.g. "Everyone", "Browser: Chrome"). Page is "Sitewide" when the guide targets no specific page. Do NOT show the raw guideId to the user. It is for your context only, to reference guides in follow-up tool calls. EXAMPLES: - What is the guide delivery order for app xxx? - Which guide shows first when several are eligible? - Show me the throttle ordering for app xxx RETURNS: - appId, appName, totalGuides, offset, returned, and the ordered guides for the app - totalGuides/offset/returned: the full ordering length and the returned slice - surface the range to the user when truncated - guides: in delivery order. Always display these six columns per guide: Guide Name, Status, Segment, Page, Guide Category, Product Area - guideId is context-only - never shown to the user