affterms — affiliate program terms

Get one program's terms

get_program

Read-onlyIdempotent

Get one tool's affiliate, referral or partner program terms. Use when someone asks about a specific program: "what does beehiiv's affiliate program pay", "does Hunter pay recurring commission", "how long is Hostinger's affiliate cookie", "what is Zyte's minimum payout". status is "listed" (commission, recurring or one-time, cookie window, minimum payout, payout method, network and notes, with the vendor page each figure was read from and the date) or "absent" (not listed: offer to submit it with submit_program, if the person agrees).

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The product or program name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already covering read-only/idempotent safety, the description adds the valuable part: the response shape, the 'listed' vs 'absent' status values, which fields a listed result carries (commission type, cookie window, minimum payout, network, notes) and provenance (source page and read date). It doesn't cover behavior for ambiguous or unmatched names.

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-loads the purpose in one sentence, then usage, then return shape. The three quoted example queries take space but each maps to a distinct field the tool returns, so they mostly earn their 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 one-parameter read tool with no output schema, the description covers purpose, triggers, return shape, and the fallback action. Only name-matching and ambiguity handling are left unstated.

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% for the single `name` parameter, so the baseline is 3. The description implies it should be a specific vendor's program name but adds no matching rules, aliases, or format guidance beyond the schema.

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 ('Get one tool's affiliate, referral or partner program terms') and scopes it to a single program versus a listing, which naturally separates it from search_programs. An agent can tell what this returns without opening the schema.

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?

Gives concrete triggering phrasings ('what does X's affiliate program pay', 'how long is X's cookie') and routes the 'absent' case to submit_program with a consent condition. It lacks an explicit exclusion telling the agent to use search_programs for discovery or multi-result queries.

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

All affterms — affiliate program terms tools Inspect

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

Need Help?