Skip to main content
Glama

AffiliateSpy

by io.affiliatespy
OverviewDiscussionsAdmin

List website placements

list_websites
Read-onlyIdempotent

Roundup articles, affiliate sites and videos promoting your competitors, best fit first (acceptance score), with SERP position, competitors featured, per-receipt link facts, and whether YOUR app is featured. Sites flagged out of outreach (review_reason) are left out unless include_flagged is set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 100.
app_idNoProject id from list_apps. Omit to use your most recently added project.
keywordNoFilter by the SERP keyword.
missing_youNoOnly placements that do NOT feature your app (outreach targets).
featuring_rivalNoOnly placements featuring at least one competitor.
include_flaggedNoAlso return sites flagged out of outreach (competitor, not a publisher, unsafe, needs review).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / app_id
      Added value: +{
+  "description": "Project id from list_apps. Omit to use your most recently added project.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_flagged
      Added value: +{
+  "description": "Also return sites flagged out of outreach (competitor, not a publisher, unsafe, needs review).",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/safe. The description adds real behavioral context beyond that: results are sorted best-fit-first by acceptance score, and review_reason flagged sites are excluded by default. This is meaningful disclosure the annotations do not provide.

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?

Two dense sentences with the resource and ordering front-loaded and the flagged-site exclusion rule at the end. No wasted filler, though the first sentence packs many clauses.

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?

No output schema exists, so the description usefully enumerates the key return fields (SERP position, competitors, link facts, your-app status), and annotations carry the safety profile. Complete enough to call correctly for a filtered list tool.

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 parameters are already documented; baseline is 3. The description reinforces include_flagged's filtering semantics and the acceptance-score ordering, but adds little beyond the schema's own descriptions.

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 the specific resource (roundup articles, affiliate sites, videos promoting competitors) and the key attributes returned (SERP position, competitors featured, whether your app is featured). This distinguishes it well from list_competitors and list_creators, though it never explicitly names a 'list' verb or the sibling it replaces.

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 only implied from the resource description; there is no explicit 'use this when' guidance or named alternative among the many list_* siblings. It does hint at when flagged sites appear (unless include_flagged is set), which is a small usage cue but not a routing rule.

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