Comunicate.eu

Rețeaua proprie

list_own_network

Read-onlyIdempotent

Rețeaua Comunicate.eu: câte publicații are, câte sunt ale partenerilor și care sunt cele din rețea, filtrate. Merge fără cont.

Use when the user explicitly asks about the Comunicate.eu own network of publications. Do not use when choosing sites in general: use search_catalog or plan_budget, which cover the whole catalogue.

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

Input Schema

Name	Required	Description
`limit`	No	Câte publicații pe pagină. Ex.: 20
`minDa`	No	DA minim (Domain Authority). Ex.: 30
`niche`	No	Slug sau nume de nișă (ex. sanatate, business)
`cursor`	No	De unde continuă lista: valoarea `nextCursor` din răspunsul anterior. Lipsă sau 0 = prima pagină.
`search`	No	Text în nume sau descriere
`campaign`	No	Doar publicațiile care acceptă tipul
`doarNume`	No	Doar numele publicațiilor: lista întreagă, scurtă
`maxPriceCents`	No	Preț maxim pe tipul ales (implicit SEO), în cenți, fără TVA

Output Schema

Name	Required	Description
`total`	No	number. Publications matching the filters.
`publications`	No	array. Own-network publications with slug, domain, niche, DA/DR, price, turnaround.
`totalCatalog`	No	number. All publications in the catalogue.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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
```

changedInput schema / properties / limit / description

Previous value: -"Câte publicații pe pagină, 1–120. Ex.: 20"New value: +"Câte publicații pe pagină. Ex.: 20"

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

changedInput schema / properties / minDa / description

Previous value: -"DA minim (Domain Authority), de la 0 la 100. Ex.: 30"New value: +"DA minim (Domain Authority). Ex.: 30"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "publications": {
+      "description": "array. Own-network publications with slug, domain, niche, DA/DR, price, turnaround."
+    },
+    "total": {
+      "description": "number. Publications matching the filters."
+    },
+    "totalCatalog": {
+      "description": "number. All publications in the catalogue."
+    }
+  },
+  "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 publicații pe pagină, 1–120. Ex.: 20"

addedInput schema / properties / minDa / description

Added value: +"DA minim (Domain Authority), de la 0 la 100. Ex.: 30"

Changed3 schema fields changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / cursor / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / maxPriceCents / 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, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in the annotations: 'Merge fără cont' (works without an account), which tells the agent no auth is required. Beyond that it does not discuss pagination behavior or how the partner/network breakdown is returned, so it adds some but not rich context.

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 short sentences, with the resource definition front-loaded before the routing guidance. The opening clause is slightly dense and partly enumerative ('câte publicații are, câte sunt ale partenerilor și care sunt cele din rețea'), but nothing is redundant or padding.

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?

For a read-only filtered list tool with full schema coverage, an output schema and complete safety annotations, the description supplies the remaining gaps: what the endpoint returns conceptually, the no-account requirement, and routing versus catalogue-wide siblings. An agent has everything needed to call it correctly.

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 coverage is 100%, so all eight parameters including cursor paging and the campaign enum are already documented in the schema. The description adds only the generic word 'filtrate' plus a description of what the response contains, which is closer to return-value context than parameter meaning. Baseline 3 applies when the schema carries the semantics.

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 concrete verb and resource: lists the publications in the Comunicate.eu own network, with counts of total vs. partner publications and which are in the network. It explicitly names the boundary against siblings ('search_catalog or plan_budget, which cover the whole catalogue'), so an agent can distinguish it without opening any 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 a positive trigger ('when the user explicitly asks about the Comunicate.eu own network') and an exclusion with the correct alternatives for the adjacent case of general site selection. Nothing about when to route elsewhere 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.