Dub MCP Server

Overview Schema Source Related Servers Discussions Admin

List all events

list_events

Read-onlyIdempotent

Fetch a paginated list of events (clicks, leads, sales) for your workspace, filterable by date, device, location, and other criteria.

Instructions

Retrieve a paginated list of events for the authenticated workspace.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`os`	No	The OS to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `Windows`, `Mac,Windows,Linux`, `-Windows`.
`qr`	No	Deprecated: Use the `trigger` field instead. Filter for QR code scans. If true, filter for QR codes only. If false, filter for links only. If undefined, return both.
`end`	No	The end date and time when to retrieve analytics from. If not provided, defaults to the current date. If set along with `start`, takes precedence over `interval`.
`key`	No	The slug of the short link to retrieve analytics for. Must be used along with the corresponding `domain` of the short link to fetch analytics for a specific short link.
`url`	No	The destination URL to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `https://example.com`, `https://example.com,https://other.com`, `-https://spam.com`.
`city`	No	The city to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `New York`, `New York,London`, `-New York`.
`page`	No	The page number for pagination. The first page is `1`.
`root`	No	Filter for root domains. If true, filter for domains only. If false, filter for links only. If undefined, return both.
`event`	No	The type of event to retrieve analytics for. Defaults to 'clicks'.	clicks
`limit`	No	The number of items per page.
`order`	No	DEPRECATED. Use `sortOrder` instead.	desc
`query`	No	Search the events by a custom metadata value. Only available for lead and sale events. Examples: `metadata['key']:'value'`
`start`	No	The start date and time when to retrieve analytics from. If set, takes precedence over `interval`.
`device`	No	The device to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `Desktop`, `Mobile,Tablet`, `-Mobile`.
`domain`	No	The domain to filter analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `dub.co`, `dub.co,google.com`, `-spam.com`.
`region`	No	The ISO 3166-2 region code to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `NY`, `NY,CA`, `-NY`.
`tag_id`	No	The tag ID to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `tag_123`, `tag_123,tag_456`, `-tag_789`.
`account`	No	Exact configured private workspace profile label; not a tenant or provider account ID.
`browser`	No	The browser to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `Chrome`, `Chrome,Firefox,Safari`, `-IE`.
`country`	No	The country to retrieve analytics for. Must be passed as a 2-letter ISO 3166-1 country code (see https://d.to/geo). Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `US`, `US,BR,FR`, `-US`.
`link_id`	No	The unique ID of the link to retrieve analytics for.Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `link_123`, `link_123,link_456`, `-link_789`.
`referer`	No	The referer hostname to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `google.com`, `google.com,twitter.com`, `-facebook.com`.
`sort_by`	No	The field to sort the events by. The default is `timestamp`.	timestamp
`tag_ids`	No	Deprecated: Use `tagId` instead. The tag IDs to retrieve analytics for.
`trigger`	No	The trigger to retrieve analytics for. Valid values: qr, link, pageview. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `qr`, `qr,link`, `-qr`. If undefined, returns all trigger types.
`group_id`	No	The group ID to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `grp_123`, `grp_123,grp_456`, `-grp_789`.
`interval`	No	The interval to retrieve analytics for. If undefined, defaults to 24h.
`timezone`	No	The IANA time zone code for aligning timeseries granularity (e.g. America/New_York). Defaults to UTC.	UTC
`utm_term`	No	The UTM term to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`).
`continent`	No	The continent to retrieve analytics for. Valid values: AF, AN, AS, EU, NA, OC, SA. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `NA`, `NA,EU`, `-AS`.
`folder_id`	No	The folder ID to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `folder_123`, `folder_123,folder_456`, `-folder_789`. If not provided, return analytics for all links.
`sale_type`	No	Filter sales by type: 'new' for first-time purchases, 'recurring' for repeat purchases. If undefined, returns both.
`tenant_id`	No	The ID of the tenant that created the link inside your system. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `tenant_123`, `tenant_123,tenant_456`, `-tenant_789`.
`event_name`	No	The conversion event name to retrieve analytics for. Only available for lead and sale events. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `Sign up`, `Sign up,Purchase`, `-Sign up`.
`partner_id`	No	The ID of the partner to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `pn_123`, `pn_123,pn_456`, `-pn_789`.
`program_id`	No	Deprecated: This is automatically inferred from your workspace's defaultProgramId. The ID of the program to retrieve analytics for.
`sort_order`	No	The sort order. The default is `desc`.	desc
`utm_medium`	No	The UTM medium to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `cpc`, `cpc,social`, `-email`.
`utm_source`	No	The UTM source to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `google`, `google,twitter`, `-spam`.
`customer_id`	No	The ID of the customer to retrieve analytics for.
`external_id`	No	The ID of the link in the your database. Must be prefixed with 'ext_' when passed as a query parameter.
`referer_url`	No	The full referer URL to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `https://google.com`, `https://google.com,https://twitter.com`, `-https://spam.com`.
`utm_content`	No	The UTM content to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`).
`utm_campaign`	No	The UTM campaign to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `summer_sale`, `summer_sale,winter_sale`, `-old_campaign`.
`partner_tag_id`	No	The partner tag ID(s) to retrieve analytics for. Supports advanced filtering: single value, multiple values (comma-separated), or exclusion (prefix with `-`). Examples: `ptag_123`, `ptag_123,ptag_456`, `-ptag_789`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 3, 2026

TDQS

C2.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description only adds that results are paginated and workspace-scoped, both of which are marginal additions over the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler, and the key noun 'events' is front-loaded. But for a tool with 45 filtering parameters, one generic sentence is arguably under-specified rather than optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (45 optional filters spanning geo, device, UTM, event type, and time-range dimensions) and the absence of an output schema, the description should at least sketch the filterable dimensions and the event types. It omits all of that, leaving the agent to reconstruct the tool's purpose entirely from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 45 parameters are already documented in the schema. The description adds no parameter-level meaning beyond that baseline, so 3 is the appropriate ceiling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Retrieve a paginated list of events'), which is clearer than a tautology. However, it is generic: it never mentions the analytics nature of these events (clicks/leads/sales) or how it differs from sibling read tools like get_link_stats or retrieve_partner_analytics, so an agent must infer the distinction from the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. 'For the authenticated workspace' implies a scope but gives no decision criteria for choosing this tool over other list/analytics siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

List all events

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools