Skip to main content
Glama

App Pain API

Watch competitors (alerts)

watch_competitors
Idempotent

Continuous competitor monitoring (paid plans: Starter 2 apps weekly, Pro 15 apps daily). Manage the watchlist and the alert destination; digests of NEW 1-2★ reviews and NEW/RISING pain points are pushed to a Slack / Discord / any https webhook. action: list | add | remove | set_webhook | test.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "watch_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNofor add/remove: store URL, iOS/Mac id, Android package or Steam appid
storeNooptional — inferred from appId (App Store URL or 5-12 digit id → ios, Play URL / package → android, Steam URL or 1-4 digit appid → steam); iOS and Mac App Store share the same URL shape, so pass "macos" explicitly for Mac apps. steam: details/search only for now — mining/reviews return steam_reviews_unavailable
actionYes
webhookUrlNofor set_webhook (or add): https URL, e.g. a Slack incoming webhook or Discord channel webhook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=true and destructive=false, and the description adds real value on top: plan-tier quotas (Starter 2 apps weekly, Pro 15 apps daily), the delivery channel semantics (Slack/Discord/any https webhook), and precisely what content is pushed (only NEW 1-2★ reviews, NEW/RISING pain points). It does not explain what 'test' does or whether removing an app deletes its accumulated history, so it stops short of fully describing side effects.

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 core capability and plan constraints, then delivery semantics, then the action enumeration — dense but well ordered. The closing 'action: list | add | remove | set_webhook | test' duplicates the schema enum and is the one sentence that does not fully earn its place.

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

Completeness4/5

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

For a 4-parameter mutation tool with no output schema, the description covers the essentials: what is monitored, what is delivered, where it is delivered, and the quota model. Gaps remain on return shape of 'list' and the effect of the 'test' action, but these are secondary for correct invocation.

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 coverage is 75% and the schema already documents appId formats, store inference rules, and webhookUrl, so the baseline is 3. The description's action enumeration repeats the schema enum, and it adds no per-parameter meaning beyond tying plan limits to the number of apps — useful context but not parameter-level clarification.

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 — continuous competitor monitoring with a managed watchlist and alert destination — and distinguishes it from the sibling one-shot readers (get_app_reviews, get_pain_trend, mine_app_pain_points) by emphasizing ongoing digests of NEW reviews and NEW/RISING pain points. An agent can tell immediately that this is a subscription/alerts tool rather than a query tool.

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?

The description makes the usage context clear (continuous monitoring with push delivery versus ad-hoc retrieval) and the action list shows the lifecycle operations. However, it never explicitly says when to choose this over a sibling like get_app_reviews or mine_app_pain_points for a one-off check, nor does it warn that 'add' on a Steam app will not yield mandatory review mining (that caveat lives only in the schema).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.