Comunicate.eu

Publicările

list_publications

Read-onlyIdempotent

Publicările organizației cu starea fiecăreia (așteaptă aprobare, în coadă, publicat, eșuat), paginat.

Use when the user asks what was ordered or published and in what state. Do not use when you already have the id: use get_publication.

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_publications"
  }
}

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 publicările în starea dată. Ex.: AWAITING_APPROVAL, QUEUED, SCHEDULED, PUBLISHED, FAILED, CANCELLED

Output Schema

Name	Required	Description	Default
`items`	No	array of {id, status, publishedUrl, publishedAt}. Ordered publications.
`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, status, publishedUrl, publishedAt}. Ordered publications."
+    },
+    "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 publicările în starea dată. Ex.: AWAITING_APPROVAL, QUEUED, SCHEDULED, PUBLISHED, FAILED, CANCELLED"

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the status spectrum and pagination, but says nothing about default ordering, default page size, or how many pages to expect — modest value on top of structured data.

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, both load-bearing: the first scopes purpose and output, the second routes the agent. The list-vs-get distinction is front-loaded and there is no filler or repetition.

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 read-only paginated list with full schema coverage, an output schema, and complete annotations, the definition covers what the tool returns and when to pick it over its sibling. Only minor operational details (default ordering, default page size behavior) are unstated, which is acceptable given the schema and output schema carry that weight.

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 limit, cursor, and status are all documented in the schema, including the nextCursor convention and example status values. The description's parenthetical state list roughly mirrors the status parameter and omits SCHEDULED/CANCELLED, adding no new parameter meaning, so the baseline of 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 resource (the organization's publications), what it returns (each one's status), and the paginated nature of the response, enumerating the states explicitly. It also explicitly distinguishes itself from get_publication by contrasting list vs. by-id retrieval.

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 an explicit when-to-use ('when the user asks what was ordered or published and in what state') and an explicit when-not-to-use that names the alternative sibling by name ('Do not use when you already have the id: use get_publication'). Nothing 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.