keap_get_affiliate_clawbacks
Retrieve all affiliate clawbacks by providing the affiliate ID. Audits commission reversals.
Instructions
Get all clawbacks for an affiliate
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| affiliate_id | Yes | Affiliate ID |
Retrieve all affiliate clawbacks by providing the affiliate ID. Audits commission reversals.
Get all clawbacks for an affiliate
| Name | Required | Description | Default |
|---|---|---|---|
| affiliate_id | Yes | Affiliate ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided and the description lacks behavioral details such as pagination, data limits, or any side effects. Minimal disclosure beyond the core action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no unnecessary words. It is front-loaded and efficient, though very brief.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get tool with one parameter and no output schema, the description is minimally adequate but could be improved by noting return format or scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter already described as 'Affiliate ID'. The description adds no new meaning beyond what is already in the input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get all clawbacks for an affiliate' with a specific verb and resource, distinguishing it from sibling tools like keap_get_affiliate_commissions or keap_get_affiliate_payments.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. The description does not mention when to choose this over other affiliate-related get tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BusyBee3333/keap-mcp-2026-complete'
If you have feedback or need assistance with the MCP directory API, please join our Discord server