Skip to main content
Glama
sai4447

agentfuse-mcp

by sai4447

list_affiliate_programs

Browse affiliate programs by category to see names, commission rates, and networks. Use this to find programs before creating tracked links.

Instructions

Browse available affiliate programs in the AgentFuse catalog. Returns each program's name, slug, category, commission rate, and network. Use this to discover programs before generating tracked links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category slug. Examples: productivity, marketing, ai-voice, ai-writing, email-marketing, newsletter, automation, marketing-automation, seo-analytics, design, developer-tools. Omit to return all categories.
limitNoNumber of programs to return (default: 50, max: 100).
cursorNoPagination cursor returned from a previous call. Pass this to get the next page.

Implementation Reference

  • Handler function that calls AgentFuse REST API GET /api/catalog with optional query params (category, limit, cursor).
    async function handleListAffiliatePrograms(args) {
      const params = new URLSearchParams();
      if (args.limit)    params.set("limit", String(args.limit));
      if (args.cursor)   params.set("cursor", args.cursor);
      if (args.category) params.set("category", args.category);
    
      const qs = params.toString();
      return agentfuse("GET", `/api/catalog${qs ? "?" + qs : ""}`);
    }
  • Schema definition for list_affiliate_programs with optional inputs: category (string filter), limit (number 1-100), cursor (string for pagination).
    name: "list_affiliate_programs",
    description:
      "Browse available affiliate programs in the AgentFuse catalog. " +
      "Returns each program's name, slug, category, commission rate, and network. " +
      "Use this to discover programs before generating tracked links.",
    inputSchema: {
      type: "object",
      properties: {
        category: {
          type: "string",
          description:
            "Filter by category slug. Examples: productivity, marketing, ai-voice, ai-writing, " +
            "email-marketing, newsletter, automation, marketing-automation, seo-analytics, " +
            "design, developer-tools. Omit to return all categories.",
        },
        limit: {
          type: "number",
          description: "Number of programs to return (default: 50, max: 100).",
          minimum: 1,
          maximum: 100,
        },
        cursor: {
          type: "string",
          description:
            "Pagination cursor returned from a previous call. Pass this to get the next page.",
        },
      },
      required: [],
    },
  • src/index.js:447-447 (registration)
    Registration of the tool handler in the HANDLERS dispatch map, mapping the tool name to the handler function.
    list_affiliate_programs: handleListAffiliatePrograms,
Behavior3/5

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

The description lists the returned fields (name, slug, category, commission rate, network), which is helpful, but it does not disclose pagination behavior, rate limits, or authentication needs. Since no annotations are provided, the description carries full burden but falls short of giving rich behavioral context.

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?

The description consists of two sentences that efficiently communicate purpose, return values, and usage context without extraneous information.

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?

While the description covers the basic return fields and usage context, it lacks details on pagination (despite a cursor parameter), ordering, error handling, and performance characteristics. The absence of an output schema makes this gap more significant, so completeness is only moderate.

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?

All three parameters have descriptions in the input schema (100% coverage), so the description adds minimal additional meaning. It does not elaborate on parameter details beyond the schema, so a baseline score of 3 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?

The description uses the verb 'Browse' and identifies the resource 'available affiliate programs in the AgentFuse catalog', making the action and scope clear. It also hints at its role relative to siblings by stating 'before generating tracked links', distinguishing it from generate_tracked_link and get_affiliate_program.

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?

The description explicitly advises using this tool 'to discover programs before generating tracked links', providing clear context for when to use it. However, it does not explicitly state when not to use it or mention alternative sibling tools.

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/sai4447/agentfuse-mcp'

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