Skip to main content
Glama
affilync
by affilync

listAvailableCampaigns

Read-only

Find active affiliate campaigns accepting new affiliates. Filter by category and page through available opportunities.

Instructions

List campaigns available to join as an affiliate. Shows active campaigns accepting new affiliates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
categoryNoFilter by category
page_sizeNoItems per page (default 20, max 50)
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. Description adds value by clarifying the result set contains only 'active' and 'accepting new affiliates' campaigns, which is not in annotations.

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 concise sentences, no wasted words, front-loaded with the main action. Every sentence earns its place.

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?

No output schema, and description does not specify what fields the returned campaigns contain (e.g., id, name, category). For a data-fetching tool, this omission reduces completeness.

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 has 100% coverage with descriptions for all 3 parameters. Description does not add extra parameter context beyond schema, so baseline is appropriate.

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?

Description clearly states 'List campaigns available to join as an affiliate' and specifies 'active campaigns accepting new affiliates', making it distinct from sibling tools like listBrandCampaigns (brand-side) and listActiveCampaigns (likely different criteria).

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?

No explicit guidance on when to use this tool versus alternatives like joinCampaign, searchCampaigns, or listActiveCampaigns. Context signals show many related tools but no comparative advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/affilync/affilync-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server