Comunicate.eu

Caută în catalog

search_catalog

Read-onlyIdempotent

Site-urile pe care se poate publica, cu preț pe tip de campanie (cenți, fără TVA), DR/DA, nișe și cum ar plăti organizația (credit, bani, indisponibil). preturi dă minimul, mediana și maximul pe toate rezultatele. Cu niche arată doar publicațiile care chiar se ocupă de nișă; siSiteGenerale: true adaugă și site-urile generale cu o rubrică pe tema asta. Implicit 10, paginat cu cursor.

Use when the user wants to browse or filter publications by niche, price, DR/DA or name. Do not use when the user states a budget and wants a ready plan: use plan_budget.

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": "search_catalog"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Ordinea: DR_DESC (implicit), DA_DESC, PRICE_ASC, PRICE_DESC sau NAME_ASC.
`limit`	No	Câte rezultate pe pagină (fără cont, cel mult 20). Ex.: 10
`minDa`	No	DA minim (Domain Authority). Ex.: 30
`minDr`	No	DR minim (Domain Rating). 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, adresă sau descriere
`campaign`	No	Tipul de campanie; lista, prețul și filtrele de preț se raportează la el. Implicit SEO
`language`	No	Limba publicațiilor. Implicit ro
`maxPriceCents`	No	Preț maxim pe tipul ales, în cenți, fără TVA
`affordableOnly`	No	Doar site-urile pe care organizația le poate plăti acum (cere cheie)
`siSiteGenerale`	No	Cu `niche`: include și site-urile generale care doar au o rubrică pe tema asta

Output Schema

Name	Required	Description
`nota`	No	string. Note to tell the user.
`total`	No	number. Matches (the public search shows the first 120).
`entries`	No	array. Publications: id, name, url, niches, DA/DR, price per campaign type (cents, VAT excluded).
`preturi`	No	object. Min, median and max price of the matches, in cents.
`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.

Changed7 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 rezultate pe pagină, 1–50 (fără cont, cel mult 20). Ex.: 10"New value: +"Câte rezultate pe pagină (fără cont, cel mult 20). Ex.: 10"

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"

changedInput schema / properties / minDr / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "entries": {
+      "description": "array. Publications: id, name, url, niches, DA/DR, price per campaign type (cents, VAT excluded)."
+    },
+    "nextCursor": {
+      "description": "number|string|null. Pass it as `cursor` to get the next page; null on the last page."
+    },
+    "nota": {
+      "description": "string. Note to tell the user."
+    },
+    "preturi": {
+      "description": "object. Min, median and max price of the matches, in cents."
+    },
+    "total": {
+      "description": "number. Matches (the public search shows the first 120)."
+    }
+  },
+  "type": "object"
+}

Changed5 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ă, 1–50 (fără cont, cel mult 20). Ex.: 10"

addedInput schema / properties / minDa / description

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

addedInput schema / properties / minDr / description

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

addedInput schema / properties / sort / description

Added value: +"Ordinea: DR_DESC (implicit), DA_DESC, PRICE_ASC, PRICE_DESC sau NAME_ASC."

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

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior on top: default page size of 10, cursor-based pagination, that `preturi` aggregates over all results rather than the current page, and that `affordableOnly` requires an API key. It does not state what happens when unauthenticated results are requested (the 20-cap only appears in the schema).

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?

The outcome-bearing content is front-loaded in the first sentence, followed by a compact usage paragraph in a separate block. Minor redundancy between 'Implicit 10, paginat cu cursor' and the schema's cursor/limit descriptions, and the mixed Romanian/English register slightly hurts scannability.

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 12-parameter, zero-required search tool with an output schema and rich annotations, the description covers the non-obvious parts: aggregate price semantics, niche broadening, pagination and default page size. Nothing critical is missing, though a note on how it differs from `list_publications` would close the remaining gap.

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 baseline would be 3, but the description goes further by explaining the interaction between `niche` and `siSiteGenerale` (general sites with a section on the topic are added, not substituted) and the scope of the `preturi` aggregate. It leaves the `sort` and `campaign` defaults to the schema, which already documents them well.

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 first sentence states a concrete resource (publishable sites) and the attributes returned per site: price per campaign type in cents excl. VAT, DR/DA, niches, and payment feasibility. It also explains the aggregate `preturi` block and how `niche` plus `siSiteGenerale` change the result set. It does not distinguish itself from the sibling `list_publications`, so an agent must infer the split itself.

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 (browse/filter publications by niche, price, DR/DA or name) and explicit when-not (user states a budget and wants a ready plan), with the alternative named directly: `plan_budget`. This is exactly the routing an agent needs to choose between the two.

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.