Skip to main content
Glama
Sign In

Searchwire

by io.github.LambdaLabsHQ
OverviewDiscussionsAdmin

Apps competing for the same keywords

app_competitors
Read-only

The apps that rank for the same store keywords as an app, most shared keywords first, with shared keyword count, average rank and volume (United States, English). $0.02 a call plus $0.002 a competitor.

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": {
      "app_id": "<app_id>"
    },
    "name": "app_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20.
storeNo"apple" (App Store, default) or "google" (Google Play).
app_idYesThe number in an App Store link (e.g. "964220645"), or with store "google" the package name (e.g. "org.telegram.messenger").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, and the description adds two valuable traits: per-call pricing ($0.02 plus $0.002 per competitor) and a fixed locale scope (United States, English). Cost awareness materially affects whether an agent should call this. Return-format detail is light but the key behavioral facts are disclosed.

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?

Two dense sentences: the first front-loads the resource, ordering, and returned fields; the second carries cost. Nothing is redundant and the most decision-relevant facts lead.

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?

With no output schema, the description correctly enumerates the return fields (shared keyword count, average rank, volume) and ordering. Locale and pricing are also disclosed. Minor gaps: no mention of result limits/pagination behavior or empty-result semantics, but the essentials are covered.

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 app_id format, the store enum, and the limit default. The description adds no parameter-level detail beyond what the schema states, so the baseline 3 applies.

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?

States a specific resource: apps ranking for the same store keywords as a given app, plus the ordering (most shared keywords first) and returned fields. It is clearly distinct from app_keywords (which would return keywords for an app) even though it doesn't name siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the resource description, but there is no explicit when-to-use or when-not guidance, and no comparison to alternatives like app_keywords or app_search. An agent must infer the competitive-analysis context.

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

All Searchwire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources