Comunicate.top

Creează o campanie (plan editorial)

create_campaign

Un plan: nume, client, obiectiv, buget în bani sau credite, interval, site-urile permise. Nu cheltuiește nimic; articolele și publicările se leagă de el.

Use when starting an editorial plan for a client: goal, budget, period, allowed sites. Do not use when changing an existing plan: use update_campaign.

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": {
      "name": "<name>"
    },
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Numele campaniei. Ex.: Lansare clinică Cluj, toamna 2026
`notes`	No	Planul editorial propriu-zis: teme, calendar, unghiuri
`endsAt`	No	Sfârșitul campaniei. Ex.: 2027-02-28T23:59:59Z
`startsAt`	No	Începutul campaniei. Ex.: 2026-12-01T00:00:00Z
`objective`	No	Obiectivul campaniei, pe scurt. Ex.: 10 articole SEO pe nișa sănătate
`clientName`	No	Clientul sau brandul pentru care e campania.
`budgetCents`	No	Bugetul în bani (1 leu = 100 de bani), fără TVA. Ex.: 150000 = 1.500 lei
`budgetCredits`	No	Bugetul în credite (1 credit = 1 publicare pe un site acoperit de pachet).
`allowedSiteIds`	No	Site-urile permise, din search_catalog sau plan_budget.

Output Schema

Name	Required	Description
`id`	No	string. The new campaign.
`name`	No	string
`status`	No	string
`articleCount`	No	number

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedNov 7, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / allowedSiteIds / description

Previous value: -"Id-urile site-urilor permise (UUID), cel mult 500, din search_catalog sau plan_budget."New value: +"Site-urile permise, din search_catalog sau plan_budget."

removedInput schema / properties / allowedSiteIds / items / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

removedInput schema / properties / budgetCents / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / budgetCredits / maximum
```
Removed value: -9007199254740991
```

changedInput schema / properties / endsAt / description

Previous value: -"Sfârșitul campaniei, dată ISO 8601 cu oră și fus. Ex.: 2027-02-28T23:59:59Z"New value: +"Sfârșitul campaniei. Ex.: 2027-02-28T23:59:59Z"

removedInput schema / properties / endsAt / pattern

Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

changedInput schema / properties / name / description

Previous value: -"Numele campaniei, 2–150 de caractere. Ex.: Lansare clinică Cluj, toamna 2026"New value: +"Numele campaniei. Ex.: Lansare clinică Cluj, toamna 2026"

changedInput schema / properties / objective / description

Previous value: -"Obiectivul campaniei, pe scurt (cel mult 500 de caractere). Ex.: 10 articole SEO pe nișa sănătate"New value: +"Obiectivul campaniei, pe scurt. Ex.: 10 articole SEO pe nișa sănătate"

changedInput schema / properties / startsAt / description

Previous value: -"Începutul campaniei, dată ISO 8601 cu oră și fus. Ex.: 2026-12-01T00:00:00Z"New value: +"Începutul campaniei. Ex.: 2026-12-01T00:00:00Z"

removedInput schema / properties / startsAt / pattern

Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "articleCount": {
+      "description": "number"
+    },
+    "id": {
+      "description": "string. The new campaign."
+    },
+    "name": {
+      "description": "string"
+    },
+    "status": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

Changed8 schema fields changedNov 7, 2026

addedInput schema / properties / allowedSiteIds / description

Added value: +"Id-urile site-urilor permise (UUID), cel mult 500, din search_catalog sau plan_budget."

addedInput schema / properties / budgetCents / description

Added value: +"Bugetul în bani (1 leu = 100 de bani), fără TVA. Ex.: 150000 = 1.500 lei"

addedInput schema / properties / budgetCredits / description

Added value: +"Bugetul în credite (1 credit = 1 publicare pe un site acoperit de pachet)."

addedInput schema / properties / clientName / description

Added value: +"Clientul sau brandul pentru care e campania."

addedInput schema / properties / endsAt / description

Added value: +"Sfârșitul campaniei, dată ISO 8601 cu oră și fus. Ex.: 2027-02-28T23:59:59Z"

addedInput schema / properties / name / description

Added value: +"Numele campaniei, 2–150 de caractere. Ex.: Lansare clinică Cluj, toamna 2026"

addedInput schema / properties / objective / description

Added value: +"Obiectivul campaniei, pe scurt (cel mult 500 de caractere). Ex.: 10 articole SEO pe nișa sănătate"

addedInput schema / properties / startsAt / description

Added value: +"Începutul campaniei, dată ISO 8601 cu oră și fus. Ex.: 2026-12-01T00:00:00Z"

Changed6 schema fields changedNov 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / allowedSiteIds / items / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / budgetCents / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / budgetCredits / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / endsAt / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

addedInput schema / properties / startsAt / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

First observedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds behavior beyond them: it explicitly states no money is spent ('Nu cheltuiește nimic') despite budget parameters, and explains the downstream relationship (articles and publications attach to the campaign). It does not address duplicate names, permission requirements, or what the response contains.

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?

Two tight sentences plus a two-clause routing line; the core framing ('a plan with these fields, spends nothing') is front-loaded. The bilingual duplication is understandable for a Romanian-facing product but slightly redundant, keeping it short of a 5.

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?

With 9 parameters (only 1 required), full schema coverage, and an output schema that carries return values, the description covers what an agent needs to select and invoke correctly. The only gap is that it does not hint that the other 8 parameters are optional, letting the agent infer that from the schema alone.

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 still adds meaning by surfacing the money-vs-credits budget choice and stating that allowed sites are the ones permitted for the plan. It does not add format or constraint detail beyond the schema, which already carries examples for every field.

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?

The description identifies the resource precisely (an editorial plan/campaign) and enumerates its components: name, client, objective, money-or-credit budget, interval, allowed sites. It is clearly distinguishable from update_campaign, though the actual creation verb appears only implicitly through 'starting an editorial plan' rather than a direct 'creates X' statement.

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?

Explicit when-to-use ('starting an editorial plan for a client: goal, budget, period, allowed sites') and explicit when-not-to-use ('changing an existing plan'), with the alternative sibling named directly: update_campaign. Nothing is left for the agent to infer about routing.

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

All Comunicate.top 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.