Skip to main content
Glama
voucherifyio

voucherify-core-mcp

Official
by voucherifyio

list_campaigns

List all campaigns to resolve a campaign ID from a campaign name. Returns a full catalog for name-based matching.

Instructions

List all campaigns with basic information for campaign resolution.

Primary Use Case: Resolve campaign ID when user provides only campaign name or partial name. Returns comprehensive list of all campaigns for further name-based matching.

Behavior:

  • Retrieves all campaigns (up to 1000) in single request

  • No filtering - returns complete campaign catalog

  • Avoid multiple calls as results are comprehensive

No Parameters Required: This tool requires no input parameters and returns all available campaigns.

Returns: JSON array of campaign objects, each containing:

  • id: Campaign identifier starting with 'camp_'

  • name: Human-readable campaign name

  • campaign_type: Campaign type (e.g., 'DISCOUNT_COUPONS', 'GIFT_VOUCHERS')

  • created_at: ISO 8601 creation timestamp

Example Output: [ { "id": "camp_abc123def456", "name": "Summer Sale 2025", "campaign_type": "DISCOUNT_COUPONS", "created_at": "2025-01-01T00:00:00.000Z" }, { "id": "camp_xyz789ghi012", "name": "Holiday Promotions", "campaign_type": "GIFT_VOUCHERS", "created_at": "2024-12-01T00:00:00.000Z" } ]

Usage Pattern:

  1. Call list_campaigns() to get all campaigns

  2. Match user's campaign name against returned names

  3. Use resolved campaign ID for other campaign tools

Limitations:

  • Maximum 1000 campaigns returned

  • No filtering options available

  • Results sorted by creation date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Clearly states behavior: retrieves up to 1000 campaigns, no filtering, single request, sorted by creation date. Includes limitations and example output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is verbose but well-structured with sections (primary use case, behavior, no parameters, returns, example, usage pattern, limitations). Every sentence adds value; front-loaded with key information.

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

Completeness5/5

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

Tool has no parameters and output schema exists (example given). Description covers purpose, behavior, limitations, usage pattern, and return structure. Completely adequate for a simple list tool.

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

Parameters4/5

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

No parameters, schema coverage 100%. Baseline 4 for 0 params. Description adds value by explicitly stating no parameters needed and explaining that no input is required.

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 it lists all campaigns for campaign resolution, with specific verb 'list' and resource 'campaigns'. Distinguishes from siblings like get_campaign by returning comprehensive list for name-based matching.

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?

Explicit primary use case is resolving campaign ID from name. Provides usage pattern and warns against multiple calls. Does not explicitly state when NOT to use, but limitations (no filtering) imply alternatives may be needed for filtered results.

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/voucherifyio/core-mcp'

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