Jepto

Return basic account context (name, plan, status) for the current session.

Account_Info

Run a marketing platform action for a client after preview; user confirms in the app. Always use Actions_List first to obtain action_id and inputs.

Actions_Execute

Catalog of marketing platform actions (inputs, risk, descriptions). Call before Actions_Execute.

Actions_List

Default tool for analytics questions: numbers, trends, comparisons, breakdowns, and reports from connected sources (e.g. Google Ads, GA4, Google Business Profile). Pass structured arguments: clientId, startDate and endDate (YYYY-MM-DD), measures, sources, optional dimensions, filters, timeDimension, granularity, limit/offset, and order as an object like {"googleAds.date":"asc"}. Use Datasource_List for valid source IDs; use Analytics_Schema when metric or dimension names are unknown.

Analytics_Query

Discover available analytics fields across connected data sources for a client. Use this when the right metrics or dimensions are unknown, ambiguous, or need confirmation before calling the Analytics_Query tool.

Analytics_Schema

Jepto Budget Tracker: manage advertising and marketing spend budgets in Jepto—set monetary caps, periods, and scope (all campaigns or specific campaign IDs) on connected platforms such as Google Ads. This is spend tracking against connected data sources, not general business or household budgeting. Actions: list and info for discovery and summaries; read for the full budget plus report payload when editing; create, update, and delete. Create requires clientId, datasourceId, service, title, startDate, authEmail, connectionIds, target amount, and related options (graph type, notifications, etc.). IMPORTANT: When allCampaigns=false and campaignIds is provided,ALWAYS first call Analytics_Query with:- measures: any valid metric (e.g., 'googleAds.clicks',- sources: ['googleAds'],- dimensions: ['googleAds.campaign_name'] or ['googleAds.campaign_id'],- startDate: recent date rangeMutations use preview first with an empty confirmObject. This applies to actions create, update, and delete; The user will confirm via clicking the 'Confirm' button in the MCP app.Integrators: resolve datasource and connection fields from the client's linked data sources (Datasource_List) and confirm them before creating budgets. Use Analytics_Query to justify target and which campaigns merit a budget.Decide on default values: title from platform + scope + period; target from analytics spend context; graphType from user preference or analytics trends; period from existing budgets or analytics context. Do not ask the user for routine fields.

Budget_Tracker

Get structured profile and business details for a client.

Client_Info

Search stored notes and knowledge for a client by keyword or topic.

Client_Knowledgebase

List clients in the account and their ids for use with other tools.

Client_List

List connected data sources and integrations for a client (or supported integration types when clientId is omitted). Use before Budget_Tracker, KPI flows, or analytics when you need dataSourceId, connectionIds, or authEmail.

Datasource_List