Skip to main content
Glama
Sign In
@kadam-net/mcp-server

@kadam-net/mcp-server

Official
by kadam-official
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

kadam_adv_set_campaign_rss

Idempotent

Point a native campaign at an RSS feed to import creatives on a schedule, or send an empty link to stop importing while keeping existing creatives.

Instructions

Point a native campaign at an RSS feed so creatives are imported from it, or stop the import by sending an empty link. Native campaigns only — other formats are rejected. The import runs on a schedule, so a success here means the feed was saved, not that creatives exist yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaignId": "<campaignId>",
      "link": "<link>"
    },
    "name": "kadam_adv_set_campaign_rss"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesFeed URL. Pass an empty string to stop importing; imported creatives stay
campaignIdYesCampaign ID, must be a native campaign
keepRemovedCreativesNoKeep creatives whose item left the feed; false archives them on the next import
pauseAfterModerationNoImported creatives stay paused after moderation so they can be reviewed first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only supply idempotentHint, so the description carries real behavioral weight and delivers it: the import is scheduled rather than immediate, success means the feed was saved and not that creatives exist yet, and stopping the import leaves already-imported creatives in place. That success-semantics caveat is exactly the kind of context annotations cannot express.

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?

Three tight sentences, front-loaded with the primary action and effect, then the eligibility constraint, then the asynchronous caveat. Every sentence carries information the agent needs.

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?

For a 4-parameter mutation with no output schema and thin annotations, the description covers the main risks: format restriction, async scheduling, and non-destructive stop behavior. Minor gaps remain (it never touches the moderation/removal flags), though the schema does document those.

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% and the schema already documents the empty-string stop convention, native-campaign requirement, and both boolean flags. The description repeats the empty-link behavior rather than adding new parameter meaning, so the baseline 3 applies.

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?

States a specific verb+resource ('point a native campaign at an RSS feed') and covers both directions of the operation (set vs. stop via empty link). The 'native campaigns only — other formats are rejected' clause scopes it precisely, and no sibling tool touches RSS feeds, so the agent can pick it without ambiguity.

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?

Gives clear when-to-use conditions for both modes: set a feed to import creatives, or send an empty link to stop. It does not name an alternative tool for related work (e.g., manual creative creation), but the usage context itself is unambiguous.

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

Deploy Server

Other Tools