Skip to main content
Glama
gruzd1sok

admitad-mcp

by gruzd1sok

list_campaigns

List affiliate campaigns (partner programs) available to a publisher, with optional filters for status, limit, and offset.

Instructions

List affiliate campaigns (partner programs) available to this publisher.

Args: limit: Max results per page (1–500). offset: Pagination offset. status: Filter by connection status: active | pending | declined | all.

Returns list of campaigns with id, name, site_url, rating, and feed_url if available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
statusNoactive
Behavior4/5

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

No annotations provided, but the description discloses read-only behavior, pagination, and return fields (id, name, site_url, etc.). It does not mention side effects or permissions, but for a list tool this is sufficient.

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?

Concise with structured Args format. Every sentence is necessary; no fluff.

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?

Coverage is good: explains all parameters, pagination, and return fields. No output schema but description lists expected fields. Lacks error/rate limit info but adequate for this tool.

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

Parameters5/5

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

Schema coverage is 0%, yet description explains each parameter: limit (1-500), offset for pagination, and status with enum values (active, pending, declined, all). Adds high value beyond 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?

Clearly states 'list affiliate campaigns (partner programs) available to this publisher.' Specific verb+resource, and distinguishes from sibling tools like list_categories and get_campaign_feeds.

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 explains when to use (list campaigns for a publisher) but does not provide explicit when-not or alternative tools. It implicitly contrasts with other tools but no direct guidance.

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/gruzd1sok/admitad-mcp'

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