Skip to main content
Glama
Sign In
Meertrack MCP

Meertrack MCP

Official
by meertrack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List activities

list_activities
Read-only

List competitor activities either as an all-time roster or as a date-filtered change feed, filtering by section, change type, and competitor with cursor pagination.

Instructions

Wraps GET /activity. Two modes, selected by whether you pass a date window:

  • Roster (no from/to): the complete all-time catalog across the tracked competitors — including items that already existed when tracking began (the initial backfill). Use this to pull a full list, e.g. every customer a competitor has published a case study about: { competitor_ids: [id], sections: ['case-studies'] }. For versioned sections (job-listings, ads, logos, messaging, pricing) this is the current live snapshot, not removed history, so change_type is mostly added and total is the all-time count.

  • Change feed (with from/to): detected adds/updates/removals in that window only (excludes backfill) — the 'what shipped recently' surface.

Filters:

  • sections: restrict to specific section types (enum of 17: blog-posts, press-posts, job-listings, ads, pricing, case-studies, linkedin-posts, x-posts, reviews, youtube-videos, events, messaging, metrics-claimed, logos, sitemap-urls, leadership, web-technologies).

  • change_types: restrict to added / updated / removed (added / updated / removed).

  • competitor_ids: narrow to specific competitors.

  • from / to: ISO 8601 date-time window (inclusive). Supplying EITHER switches off roster mode; e.g. from=2026-04-16T00:00:00Z for the last 7 days.

Matching tip: for case studies the customer/company name is usually in title and/or the url slug (e.g. .../case-studies/whop) — match on both.

Section notes:

  • leadership: one row per leadership change event; there is no current-team list. data.event is the exact kind (added, removed, replaced, title_changed); change_type maps replaced and title_changed to updated. On the roster path, rows with data.initial_run: true are the leaders found on the first scan (their headline may still read "New …"), not new appointments.

  • web-technologies: one row per homepage scan that changed the tech stack, plus the first scan (roster only). data.added / data.updated / data.removed list technology names (updated = version or classification changed). change_type is added for the first scan (all three lists empty; its stack is in technologies, via get_activity_items) or an add-only scan, removed for a remove-only scan, and updated for anything else (version-only or mixed). A mixed scan that removed something is updated, not removed, so to find every addition or removal omit change_types and read the lists.

  • New sections may appear over time; treat an unknown section value as an opaque label.

Pagination: response carries pagination.next_cursor, pagination.has_more, and pagination.total (total rows matching the filters, not just this page). If has_more, call again with the cursor param set to next_cursor. Default limit is 50 to stay under Claude's tool-result size limit; max is 500. The roster can be large — keep paging until has_more is false.

Heavy fields (description, key_points, pricing_data, excerpt, summary for leadership, technologies for web-technologies) are omitted from list rows to keep them lean; fetch the full payload for rows you care about with get_activity_items (pass their ids). Chaining: get_activity_items returns full rows by id (one call for many ids). Errors: invalid_parameter (bad section/change_type/date), invalid_cursor (stale or tampered), unauthorized, rate_limited.

Input Schema

NameRequiredDescriptionDefault
toNoInclusive upper bound, ISO 8601 with offset.
fromNoInclusive lower bound, ISO 8601 with offset (e.g. `2026-04-16T00:00:00Z`).
limitNoPage size. Default 50 (tool-result size limit); max 500. Prefer smaller pages and paginate.
cursorNoOpaque cursor from a previous response's `pagination.next_cursor`. Omit on the first call.
sectionsNoFilter to specific section types (e.g. `['pricing', 'blog-posts']`).
change_typesNoFilter to specific change types. `added` is usually the interesting one.
competitor_idsNoNarrow to these competitor ids. Omit for all tracked competitors.

Output Schema

NameRequiredDescriptionDefault
dataYes
paginationYesShared cursor-pagination envelope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.3.0
    • changedInput schema / properties / sections / items / enum
      Previous value: -[
-  "blog-posts",
-  "press-posts",
-  "job-listings",
-  "ads",
-  "pricing",
-  "case-studies",
-  "linkedin-posts",
-  "x-posts",
-  "reviews",
-  "youtube-videos",
-  "events",
-  "messaging",
-  "metrics-claimed",
-  "logos",
-  "sitemap-urls"
-]New value: +[
+  "blog-posts",
+  "press-posts",
+  "job-listings",
+  "ads",
+  "pricing",
+  "case-studies",
+  "linkedin-posts",
+  "x-posts",
+  "reviews",
+  "youtube-videos",
+  "events",
+  "messaging",
+  "metrics-claimed",
+  "logos",
+  "sitemap-urls",
+  "leadership",
+  "web-technologies"
+]
    • addedOutput schema / properties / data / items / properties / change_type / description
      Added value: +"Change type: added, updated, removed."
    • removedOutput schema / properties / data / items / properties / change_type / enum
      Removed value: -[
-  "added",
-  "updated",
-  "removed"
-]
    • addedOutput schema / properties / data / items / properties / section / description
      Added value: +"Section slug: blog-posts, press-posts, job-listings, ads, pricing, case-studies, linkedin-posts, x-posts, reviews, youtube-videos, events, messaging, metrics-claimed, logos, sitemap-urls, leadership, web-technologies. New sections may appear; treat an unknown value as an opaque label."
    • removedOutput schema / properties / data / items / properties / section / enum
      Removed value: -[
-  "blog-posts",
-  "press-posts",
-  "job-listings",
-  "ads",
-  "pricing",
-  "case-studies",
-  "linkedin-posts",
-  "x-posts",
-  "reviews",
-  "youtube-videos",
-  "events",
-  "messaging",
-  "metrics-claimed",
-  "logos",
-  "sitemap-urls"
-]
  2. First observedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint already covering safety, the description still adds substantial behavior: heavy fields are omitted from rows, default limit is 50 for tool-result size, backfilled items appear on the roster, and specific error codes are named. That is far beyond what the annotations convey.

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

Conciseness4/5

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

Front-loaded with the endpoint and the two-mode split, then segmented with bullets for filters, section notes, pagination, and errors — easy to scan. It is long, and a few lines (limit default, cursor mechanics) restate the schema verbatim rather than adding value.

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

Completeness5/5

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

Covers everything an agent needs despite seven params and a large result surface: pagination loop (`has_more` -> `next_cursor`), truncated fields and the follow-up call to hydrate them, error taxonomy, and section-specific caveats. An output schema exists, and the description correctly avoids re-explaining return shapes.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds non-obvious semantics: supplying EITHER from or to switches off roster mode, change_type collapsing rules for leadership and web-technologies, and a title/url matching tip. Some of the limit and cursor text merely repeats the schema descriptions, which keeps it from a 5.

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

Purpose5/5

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

States a specific verb and resource ('Wraps GET /activity', lists activities) and immediately decomposes it into two concrete modes, roster vs change feed, so an agent can tell exactly what it returns. It also distinguishes itself from the sibling get_activity_items by capping list rows to lean fields.

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

Usage Guidelines5/5

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

Explicit mode-selection rule ('no from/to = roster', 'with from/to = change feed'), a worked example request, and a named alternative for full payloads (get_activity_items). Section-specific guidance (leadership, web-technologies) further tells the agent when to include or omit change_types.

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

Deploy Server

Other Tools