Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

track_competitor_activity

Monitor competitor social media posts, engagement, promotions, and products to identify market trends and pricing strategies for informed business decisions.

Instructions

Track competitor social media activity to stay informed about market trends and pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
competitorsYesComma-separated competitor page names or IDs
metricsNoMetrics to track: posts, engagement, promotions, products

Implementation Reference

  • Handler function for the 'track_competitor_activity' tool. Validates input, generates mock competitor social media data (posts, engagement, promotions), and returns formatted tracking report. Currently uses simulated data; production would integrate real API tracking.
    case 'track_competitor_activity': {
      const competitors = String(args?.competitors || '');
      const metrics = String(args?.metrics || 'posts,engagement');
      
      if (!competitors) {
        return {
          content: [{
            type: 'text',
            text: `āŒ Please provide competitor page names to track.`
          }]
        };
      }
    
      const competitorList = competitors.split(',').map(c => c.trim());
      const metricsList = metrics.split(',').map(m => m.trim());
    
      // Mock competitor data
      const mockData = competitorList.map(comp => ({
        name: comp,
        postsThisWeek: Math.floor(Math.random() * 10) + 3,
        avgEngagement: Math.floor(Math.random() * 200) + 50,
        recentPromotion: Math.random() > 0.5 ? 'Yes - Sale on brushes' : 'No recent promotions'
      }));
    
      return {
        content: [{
          type: 'text',
          text: `šŸ” Competitor Activity Tracking\nšŸ“Š Metrics: ${metricsList.join(', ')}\n\n${mockData.map(comp =>
            `šŸ“ ${comp.name}\n  šŸ“ Posts this week: ${comp.postsThisWeek}\n  šŸ’¬ Avg engagement: ${comp.avgEngagement}\n  šŸŽÆ Promotions: ${comp.recentPromotion}`
          ).join('\n\n')}\n\nšŸ’” Note: This is a demonstration feature. In production, this would track public competitor pages to help you stay competitive.`
        }]
      };
    }
  • Tool schema definition including input validation for competitors (required) and optional metrics. Part of the tools array used for MCP tool listing and call validation.
    {
      name: 'track_competitor_activity',
      description: 'Track competitor social media activity to stay informed about market trends and pricing.',
      inputSchema: {
        type: 'object',
        properties: {
          competitors: { type: 'string', description: 'Comma-separated competitor page names or IDs' },
          metrics: { type: 'string', description: 'Metrics to track: posts, engagement, promotions, products' },
        },
        required: ['competitors'],
      },
    },
  • src/index.ts:516-518 (registration)
    Registers all tools (including track_competitor_activity) via the ListToolsRequestHandler, which returns the complete tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/dashboard.ts:84-84 (registration)
    Mock tool registration in dashboard's toolsData for UI demonstration.
    { name: 'track_competitor_activity', description: 'Monitor competitor activity', category: 'Social Media Management' },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool tracks activity but doesn't reveal key behaviors: whether it's a read-only operation, how data is retrieved (e.g., real-time vs. historical), rate limits, authentication needs, or what the output looks like. For a tool with no annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Track competitor social media activity') followed by the benefit. There is no wasted verbiage or redundancy, making it highly concise and well-structured.

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 (tracking social media activity with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, output format, or usage guidelines, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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 the schema already documents both parameters ('competitors' and 'metrics') with descriptions. The tool description adds no additional parameter semantics beyond what's in the schema, such as format examples or usage context. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Track competitor social media activity' with the goal 'to stay informed about market trends and pricing.' It specifies the resource (competitor social media) and outcome, though it doesn't explicitly differentiate from sibling tools like 'get_social_analytics' or 'analyze_post_performance' which might have overlapping domains.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions the general purpose but doesn't specify scenarios, prerequisites, or exclusions. With sibling tools like 'get_social_analytics' and 'analyze_post_performance' present, this lack of differentiation is a significant gap.

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/wspotter/mcpart'

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