Skip to main content
Glama

Set channel membership

set_channel_membership
DestructiveIdempotent

Mark or unmark up to 100 products for one connected sales channel (prom, rozetka, ebay, olx, …). It changes what the CRM intends to send: on Prom and Rozetka the next feed pull adds or drops the product; on eBay it only makes the product a channel member — a listing exists only after create_ebay_drafts and publish_ebay_drafts. It never arms a sync. Adding picks up active products only. Returns { affected, skipped } — skipped were already in that state. Refused until the workspace owner switches on AI publishing. Idempotent. The result echoes the workspace.

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": {
      "listed": "<listed>",
      "platform": "<platform>",
      "productIds": "<productIds>"
    },
    "name": "set_channel_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
listedYestrue marks the products for this channel; false unmarks them. This only changes what the CRM intends to send — it never arms a sync and never creates a listing by itself. Unmarking a product on Prom drops it from the next feed pull.
platformYesThe connected sales channel to change membership on (e.g. prom, rozetka, ebay, olx).
productIdsYesThe exact products to change, at most 100 ids fetched with search_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "prom",
      -  "rozetka",
      -  "woocommerce",
      -  "shopify",
      -  "olx",
      -  "amazon",
      -  "ebay",
      -  "google_merchant"
      -]New value: +[
      +  "prom",
      +  "rozetka",
      +  "woocommerce",
      +  "shopify",
      +  "olx",
      +  "amazon",
      +  "ebay",
      +  "google_merchant",
      +  "vinted",
      +  "etsy"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses concrete consequences (on Prom and Rozetka the next feed pull adds or drops the product), the return payload { affected, skipped } with the meaning of 'skipped', and a hard authorization gate ('refused until the workspace owner switches on AI publishing'). The only weakness is that 'Idempotent' merely restates idempotentHint=true rather than adding anything new.

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?

It is front-loaded with purpose and channel scope, then behavior, then return shape, then the auth gate — a sensible order with no filler sentences. It is dense to the point of being terse in a few clauses (the eBay clause packs three ideas), but nothing is extraneous.

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?

No output schema exists, yet the description supplies the return shape, the meaning of each field, the precondition that must be satisfied first, the batch cap, and the per-channel effect. For a destructive, idempotent batch mutation that is everything an agent needs to call it safely.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: 'Adding picks up active products only' constrains what the listed=true flag actually does for inactive products, and the eBay semantics of the platform value are spelled out where the enum alone is silent. The listed/platform/productIds meanings themselves are already fully documented in the 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?

The description gives a precise verb pair and resource ('Mark or unmark up to 100 products for one connected sales channel') plus concrete channel examples. It immediately contrasts itself with listing-creation siblings (create_ebay_drafts / publish_ebay_drafts), so an agent can separate membership from publishing without opening any schema.

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

Usage Guidelines5/5

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

It names the alternatives and the exact condition that selects them: on eBay this only makes a product a channel member, and a listing exists only after create_ebay_drafts and publish_ebay_drafts. It also states what the tool is not ('never arms a sync') and that adding only picks up active products, which routes the agent correctly before and after the call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources