Skip to main content
Glama

AffiliateSpy

by io.affiliatespy
OverviewDiscussionsAdmin

Start quick scan (free preview)

start_quick_scan

Free quick scan of an App Store, Google Play or website URL: creates the tracked app and queues the scan. No plan needed (one quick-scan app per unpaid account, 6 an hour). Preview only (masked handles, no contacts). Accounts WITH a plan should use start_scan for the full scan instead. Takes 20 to 60 seconds to return because the intake (competitors, search queries) runs first; then call get_quick_scan_preview, which waits server-side until the scan is done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesApp Store URL, Google Play URL, app name, or website domain.
kindNoDefault app.
marketNoMarket label such as "United States"; defaults to US.
confirmNoSet true after the user confirmed an action the guard flagged as hard to undo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Set true after the user confirmed an action the guard flagged as hard to undo.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses meaningful behaviors: it creates a tracked app, queues work, enforces free-tier limits, masks handles, and takes 20–60 seconds because intake runs first. This gives the agent accurate expectations about latency and 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.

Conciseness5/5

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

The description is dense yet well structured, front-loading the core function before adding constraints, alternatives, timing, and follow-up steps. Every sentence contributes necessary operational context without repetition.

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?

For a tool with no output schema, the description covers the full call flow: what the tool does, what limits apply, how long it takes, and what to call next. An agent has everything needed to invoke it correctly and manage expectations.

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 all four parameters, including URL formats, kind enum, market default, and confirm semantics. The description adds little parameter-specific detail, which is acceptable given the schema coverage.

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 states a specific verb and resource: it starts a free quick scan of an App Store, Google Play, or website URL, creating the tracked app and queuing the scan. It also clearly distinguishes itself from start_scan, so an agent can identify the correct tool without ambiguity.

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?

The description explicitly says when to use this tool: for accounts without a plan, and it directs accounts with a plan to use start_scan instead. It also tells the agent to follow up with get_quick_scan_preview, giving clear operational guidance.

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

All AffiliateSpy 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