FavCRM

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/io.favcrm/favcrm/admin

create_broadcast

Create a DRAFT WhatsApp or SMS broadcast campaign. The broadcast is NOT sent — admin must review and send it from the Broadcasts page.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Campaign name
`channel`	No	Channel (default whatsapp)
`templateId`	No	Message template ID to use
`scheduledAt`	No	ISO date to schedule the broadcast
`recipientFilter`	No	Audience for this draft. Omit for all customers, use { tagIds: ["..."] } for the legacy tag filter, or provide recipientType with the required recipientIds, segmentId, or tierId.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 4, 2026

removedInput schema / properties / recipientFilter / additionalProperties
```
Removed value: -{}
```

addedInput schema / properties / recipientFilter / anyOf

Added value: +[
+  {
+    "properties": {
+      "recipientType": {
+        "const": "all",
+        "type": "string"
+      },
+      "tagIds": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "recipientType"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "recipientIds": {
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "recipientType": {
+        "const": "individual",
+        "type": "string"
+      }
+    },
+    "required": [
+      "recipientType",
+      "recipientIds"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "recipientType": {
+        "const": "segment",
+        "type": "string"
+      },
+      "segmentId": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "recipientType",
+      "segmentId"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "recipientType": {
+        "const": "tier",
+        "type": "string"
+      },
+      "tierId": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "recipientType",
+      "tierId"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "tagIds": {
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      }
+    },
+    "required": [
+      "tagIds"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / recipientFilter / description

Previous value: -"Filter criteria for recipients, e.g. { tagIds: [\"...\"] }"New value: +"Audience for this draft. Omit for all customers, use { tagIds: [\"...\"] } for the legacy tag filter, or provide recipientType with the required recipientIds, segmentId, or tierId."

removedInput schema / properties / recipientFilter / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / recipientFilter / type
```
Removed value: -"object"
```

First observedJun 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no detailed annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint are all false or unhelpful), the description carries the behavioral burden. It discloses the key side-effect by explicitly stating 'The broadcast is NOT sent' and requiring admin review, which goes beyond simply saying 'create'. It does not mention auth requirements or rate limits, but the central draft behavior is clear.

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?

The description is two concise sentences with no filler. It front-loads the most important information ('DRAFT') and the critical operational constraint ('NOT sent'), which earns its place and avoids redundant details.

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

Completeness3/5

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

For a tool with a complex recipientFilter schema and no meaningful annotations, the description correctly points to the draft-and-review workflow, but it does not mention any caveats about scheduledAt, template requirements, or how repeated executions behave. The schema covers parameter descriptions, and the output schema handles return values, so the context is adequate but not exhaustive.

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%, so each parameter (name, channel, templateId, scheduledAt, recipientFilter) already carries rich descriptions in the schema. The tool description adds no field-level meaning, so it neither improves nor harms parameter understanding, matching the baseline for fully covered schemas.

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 uses a specific verb ('Create') with a specific resource ('DRAFT broadcast campaign') and identifies the channels ('WhatsApp or SMS'). It also clearly distinguishes this from simply creating a normal campaign by emphasizing the draft status and mandatory admin review/send from the Broadcasts page, making it easy to tell apart from siblings like create_campaign.

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?

The description explicitly communicates the primary use case: creating a draft broadcast that will not be sent until an admin acts on it. While it does not name alternative tools or instruct when not to use it, the workflow context ('admin must review and send it') tells the agent that this is the correct choice when a draft is intended for human approval.

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

All FavCRM 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?