Comunicate.eu

Modifică o campanie

update_campaign

DestructiveIdempotent

Schimbă obiectivul, notele, bugetul sau site-urile permise ale unei campanii.

Use when changing the goal, notes, budget, period or allowed sites of an existing campaign. Do not use when creating one: use create_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": {
      "campaignId": "<campaignId>"
    },
    "name": "update_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	No	Numele campaniei. Ex.: Lansare clinică Cluj, toamna 2026
`notes`	No	Planul editorial: teme, calendar, unghiuri; înlocuiește notele vechi.
`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
`campaignId`	Yes	Campania, din list_campaigns sau create_campaign.
`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; înlocuiesc lista veche.

Output Schema

Name	Required	Description
`id`	No	string
`name`	No	string
`status`	No	string
`articleCount`	No	number

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 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; înlocuiesc lista veche."New value: +"Site-urile permise; înlocuiesc lista veche."

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 / campaignId / description

Previous value: -"Id-ul campaniei (UUID), din list_campaigns sau create_campaign."New value: +"Campania, din list_campaigns sau create_campaign."

removedInput schema / properties / campaignId / 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)$"

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"
+    },
+    "name": {
+      "description": "string"
+    },
+    "status": {
+      "description": "string"
+    }
+  },
+  "type": "object"
+}

Changed10 schema fields changedNov 7, 2026

addedInput schema / properties / allowedSiteIds / description

Added value: +"Id-urile site-urilor permise (UUID), cel mult 500; înlocuiesc lista veche."

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 / campaignId / description

Added value: +"Id-ul campaniei (UUID), din list_campaigns sau create_campaign."

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 / notes / description

Added value: +"Planul editorial: teme, calendar, unghiuri; înlocuiește notele vechi."

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"

Changed7 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 / campaignId / 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 / 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

A3.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds no behavioral context of its own beyond purpose: it does not say whether omitted fields are left untouched, that notes and allowedSiteIds overwrite prior values, or what a destructive update implies. The overwrite semantics exist only in the schema field descriptions, not here.

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?

Short and front-loaded, with the exclusion and alternative in the second sentence where it belongs. Minor waste: the Romanian opening sentence largely duplicates the English usage sentence, so the same field list is presented twice in two languages.

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 10-parameter mutation with full schema descriptions, rich annotations and an output schema, the description needs only to state purpose and routing, which it does. The one real gap is partial-update semantics — what happens to fields that are omitted — which an agent calling a destructive update would want stated.

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%, with per-field Romanian descriptions including units (bani, credite) and replacement semantics, so the schema carries the load. The description only names a subset of fields and adds no syntax or format detail beyond the schema; 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 ("Schimbă") plus the exact resource (an existing campaign) and enumerates the mutable fields: goal, notes, budget, period, allowed sites. The English sentence adds the period and the explicit contrast with create_campaign, so an agent can distinguish it from the sibling without opening the 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?

Gives both sides of the routing decision: use when changing an existing campaign's attributes, do not use when creating one, and names the correct alternative (create_campaign). Nothing about when-to-use is left to inference.

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

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