socialloop-mcp

Add Affiliate Code

add_affiliate_code

Extend an affiliate to another ticket tier — adds the tier to their promo code with its own discount and optional commission. Requires event_id + affiliate_id + ticket_class_id + discount; you must be a host.

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": {
      "event_id": "<event_id>",
      "affiliate_id": "<affiliate_id>",
      "ticket_class_id": "<ticket_class_id>",
      "discount_type": "<discount_type>",
      "discount_value": "<discount_value>"
    },
    "name": "add_affiliate_code"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes
`affiliate_id`	Yes
`discount_type`	Yes
`discount_value`	Yes
`commission_type`	No
`ticket_class_id`	Yes
`commission_value`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Description adds auth requirement ('you must be a host') beyond annotations. However, it does not disclose potential side effects (e.g., overwriting existing tiers), idempotency, or response shape. Annotations are minimal, so description carries some burden but leaves gaps.

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 sentences: first states purpose and key feature, second lists requirements. No redundant words, efficient and front-loaded.

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

Completeness3/5

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

Given no output schema and 7 params, description covers purpose, required params, and auth but lacks success behavior, optional commission details, and usage differentiation from sibling tools. Adequate but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description must compensate. It mentions required parameters (event_id, affiliate_id, ticket_class_id, discount) and optional commission, but does not explain each parameter's meaning (e.g., discount_type vs discount_value, commission_type). This provides marginal addition but insufficient guidance for 7 parameters.

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 clearly states the verb 'extend' and resource 'affiliate to another ticket tier', distinguishing it from siblings like 'add_affiliate' or 'create_promo_code'. It also lists required parameters and a prerequisite (host status), making the purpose unambiguous.

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?

The description implies usage when adding a tier to an affiliate's promo code but does not explicitly state when to use this tool versus alternatives such as 'create_promo_code' or 'update_affiliate_commission'. No exclusions or alternative tools are mentioned.

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

All socialloop-mcp 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.