Skip to main content
Glama
meertrack

Meertrack MCP

Official
by meertrack

List activities

list_activities
Read-only

Retrieve a full catalog or recent changes of competitor activities. Filter by sections (e.g., case studies, pricing) and date window to monitor specific updates.

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 15: blog-posts, press-posts, job-listings, ads, pricing, case-studies, linkedin-posts, x-posts, reviews, youtube-videos, events, messaging, metrics-claimed, logos, sitemap-urls).

  • 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.

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) 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

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
paginationYesShared cursor-pagination envelope.
Behavior5/5

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

Annotations declare `readOnlyHint: true`, and the description adds rich behavioral context: pagination behavior (cursor, limit, default 50), heavy fields omitted, and error types (invalid_parameter, invalid_cursor, unauthorized, rate_limited). No contradiction with annotations.

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?

Well-structured with headers, bullet points, and clear sections. Slightly verbose but each paragraph serves a purpose: modes, filters, pagination, and error handling. Could be tightened slightly, but no redundant sentences.

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?

Given the complexity (two modes, pagination, heavy fields, error handling), the description is comprehensive. It explains return values like `pagination.next_cursor` and `has_more`, and references `get_activity_items` for full detail, leaving no critical gaps.

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% (all parameters documented). The description adds meaningful context beyond schema: explains that `from`/`to` switch to change feed, default `limit` is 50, and cursor usage. This aids agent in understanding parameter interplay.

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?

The description clearly states it wraps `GET /activity` and explains the two modes (roster and change feed), with specific verbs (list, pull, fetch) and resource (activities). It distinguishes from siblings by referencing `get_activity_items` for heavy fields.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use each mode (roster for full list, change feed for 'what shipped recently') and includes a matching tip. Does not explicitly exclude alternatives, but the sibling tools are differentiated implicitly, e.g., `get_activity_items` for fetching full payloads.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/meertrack/meertrack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server