Comunicate.eu

Campaniile (planurile editoriale)

list_campaigns

Read-onlyIdempotent

Campaniile organizației: obiectiv, buget, site-uri permise, articole legate.

Use when the user asks about their editorial plans (campaigns) or you need a campaign id. Do not use for publications: use list_publications.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_campaigns"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Câte rezultate pe pagină. Ex.: 10
`cursor`	No	De unde continuă lista: valoarea `nextCursor` din răspunsul anterior. Lipsă sau 0 = prima pagină.
`status`	No	Doar campaniile în starea dată: DRAFT, ACTIVE, PAUSED, COMPLETED sau ARCHIVED.

Output Schema

Name	Required	Description	Default
`items`	No	array of {id, name, status}. Editorial plans of the organisation.
`nextCursor`	No	number\|string\|null. Pass it as `cursor` to get the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026

removedInput schema / $schema

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

removedInput schema / properties / cursor / maximum
```
Removed value: -9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "items": {
+      "description": "array of {id, name, status}. Editorial plans of the organisation."
+    },
+    "nextCursor": {
+      "description": "number|string|null. Pass it as `cursor` to get the next page; null on the last page."
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedNov 7, 2026

addedInput schema / properties / cursor / description

Added value: +"De unde continuă lista: valoarea `nextCursor` din răspunsul anterior. Lipsă sau 0 = prima pagină."

addedInput schema / properties / limit / description

Added value: +"Câte rezultate pe pagină. Ex.: 10"

addedInput schema / properties / status / description

Added value: +"Doar campaniile în starea dată: DRAFT, ACTIVE, PAUSED, COMPLETED sau ARCHIVED."

Changed2 schema fields changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / cursor / maximum
```
Added value: +9007199254740991
```
First observedOct 31, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description adds useful context that results carry allowed sites and linked articles, but says nothing about pagination behavior, default result count, or what an empty list means beyond what the schema already covers.

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?

Two sentences, zero padding, and the scope statement precedes the routing guidance. Every clause earns its place, though the mixed Romanian/English register is a minor stylistic inconsistency rather than a clarity problem.

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?

With an output schema present, a fully documented 3-parameter input schema and rich annotations, the description covers the remaining gaps: what the resource is, what it contains, and when to choose it over list_publications. Nothing an agent needs to invoke it correctly is missing.

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%: limit, cursor and the status enumeration are all documented in the schema, including how nextCursor maps back to the cursor input. The description adds no additional parameter semantics such as default status filter behavior, so the baseline of 3 applies.

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 names the resource (the organization's campaigns) and the concrete payload fields it returns (objective, budget, allowed sites, linked articles), so an agent knows exactly what it gets back. The verb is only implied by the tool name 'list_campaigns' rather than stated in the description, which keeps it just short of a full 5.

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 states both the positive trigger ('when the user asks about their editorial plans (campaigns) or you need a campaign id') and the exclusion with an explicit alternative ('Do not use for publications: use list_publications'). This is exactly the routing information an agent needs among 26 sibling tools.

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.