Skip to main content
Glama
meertrack

Meertrack MCP

Official
by meertrack
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get competitor

get_competitor
Read-only

Retrieve a competitor's complete profile and their most recent activities across all tracked sections, including blog posts, press, case studies, and more. Use the competitor ID obtained from listing competitors.

Instructions

Wraps GET /competitors/{id}. Returns a single competitor's full profile plus the most recent items from each tracked section. Sections returned (with per-section item caps):

  • blog-posts (up to 3), press-posts (3), case-studies (3)

  • job-listings (5), ads (5), pricing (1), messaging (5)

  • metrics-claimed (5), logos (5)

  • linkedin-posts (3), x-posts (3), reviews (3), youtube-videos (3), events (3)

These are overview caps — for the full list in any section call list_activities with competitor_ids=[id] and the relevant section and NO from/to, which returns the complete all-time roster (paginated).

Chaining: Use after list_competitors — pass the id from a result row. For an activity timeline across sections, call list_activities with competitor_ids=[id] instead. Errors: not_found (no such competitor in this workspace), competitor_inactive (archived — reactivate in dashboard), forbidden_competitor (different workspace), unauthorized, rate_limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCompetitor id from `list_competitors`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations indicate readOnlyHint; description adds caps per section, explains overview vs full list, and references list_activities for complete data. No contradiction.

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

Conciseness5/5

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

Well-structured with bullet points, clear separation of sections, chaining, and errors. Concise yet comprehensive; every sentence adds 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?

Given the output schema exists, description details returned data (full profile + recent items per section with caps) and errors, making it complete.

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 already describes the single parameter 'id' as 'Competitor id from list_competitors.' Description does not add further detail, so baseline of 3 is appropriate.

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?

Clearly states it returns a single competitor's full profile plus most recent items from each tracked section, listing specific sections. Distinguishes from siblings like list_competitors and list_activities.

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?

Explicitly says to use after list_competitors, pass the id. Also advises when to use list_activities instead for a full timeline. Includes error cases.

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