Daisycon (MCP server)

getAllPublicPrograms

Read-onlyIdempotent

Get all public programs

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Filter by program ID(s)
`type`	No	Filter by advertiser type(s) (affiliatemarketing/leadgeneration)
`limit`	No	Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied); once a cursor is used, its own limit applies and this is ignored.
`cursor`	No	Pagination cursor from a previous response. Omit to start from the first page.
`fields`	No	The fields to include in each result: a list of names, or a comma-separated string as a fallback. Omit to receive every field.
`deeplink`	No	Filter by deep linking flag (true/false)
`order_by`	No	Field to sort by (id, advertiser_id, name, currency_code, start_date)
`locale_id`	No	Filter by locale ID(s)
`start_date`	No	Filter on the date a program started, as a date (Y-m-d) or as a range (json: gt, gte, lt, lte, e.g. {"gte":"2024-01-01","lte":"2024-12-31"})
`category_id`	No	Filter by category ID(s)
`productfeed`	No	Filter by productfeed flag (true/false)
`search_term`	No	Search by program name (partial match) or by program ID (exact match on a term of digits only)
`advertiser_id`	No	Filter by advertiser ID(s)
`currency_code`	No	Filter by currency code(s)
`similar_to_id`	No	Return the campaigns that resemble the given campaign ID(s), most similar first. Resemblance is based on the English campaign descriptions. The campaigns asked about are not part of the answer, and this ordering replaces order_by
`commission_cpc`	No	Filter on the cost per click a program pays, in the currency defined by currency_code, as an amount or as a range (json: gt, gte, lt, lte, e.g. {"gte":0.1,"lte":1})
`order_direction`	No	Sort direction (ASC or DESC)
`commission_fixed`	No	Filter on the fixed commission a program pays, in the currency defined by currency_code, as an amount or as a range (json: gt, gte, lt, lte, e.g. {"gte":5,"lte":25})
`commission_ratio`	No	Filter on the commission percentage a program pays, as a percentage or as a range (json: gt, gte, lt, lte, e.g. {"gte":5,"lte":25})
`supply_locale_id`	No	Filter by supply locale ID(s)
`allowed_media_type_id`	No	Filter by allowed media type ID(s)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / fields / anyOf

Added value: +[
+  {
+    "items": {
+      "enum": [
+        "advertiser_id",
+        "id",
+        "name",
+        "currency_code",
+        "type",
+        "start_date",
+        "categories",
+        "locales",
+        "supply_locales",
+        "productfeed",
+        "deeplink",
+        "allowed_media_types",
+        "commission",
+        "links"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "description": "Fallback for comma-separated values, like: 'id,name'",
+    "type": "string"
+  }
+]

changedInput schema / properties / fields / description

Previous value: -"Comma-separated list of fields to include in the response. The data of the fields left out is not fetched"New value: +"The fields to include in each result: a list of names, or a comma-separated string as a fallback. Omit to receive every field."

removedInput schema / properties / fields / type
```
Removed value: -"string"
```

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied) — once a cursor is used, its own limit applies and this is ignored."New value: +"Maximum results per page (1-1000, default 100). Only used when starting a new list (no cursor supplied); once a cursor is used, its own limit applies and this is ignored."

First observedOct 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description itself adds no behavioral context — nothing about pagination, filtering, or result shape beyond what annotations and schema already provide.

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

Conciseness3/5

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

It is a single short, front-loaded sentence with no waste, but it is under-specified rather than genuinely concise for a tool this complex. Brevity here reflects a lack of content, not efficient structure.

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

Completeness2/5

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

For a 21-parameter listing tool with heavy filtering, cursor pagination, field selection, and no output schema, the description omits any mention of pagination, filtering capability, or relationship to the sibling 'list' tool. It is inadequate for the complexity.

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 description coverage is 100% (21 params, all documented with formats, ranges, and defaults), so the schema carries the semantic burden. The description adds nothing to parameter meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('public programs'), so an agent knows the basic operation. However, it offers no differentiation from the sibling tool 'list', and the word 'all' is misleading given the 21 filtering/pagination parameters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and never mentions the sibling 'list' tool or any alternative. An agent must infer everything about selection from the tool name alone.

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

All Daisycon (MCP server) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?