Comunicate.top

Creează o ciornă de articol

create_article

Salvează un articol ca ciornă în cont (nu publică nimic). Conținutul e HTML. Pentru mai multe publicații recomandăm texte unice, câte unul pe site. Comunicatele cer minimum 100 de cuvinte, articolele SEO minimum 150 și un link extern. Nu costă nimic.

Use when the user provides or asks you to write a text that should be saved as a draft. Do not use when changing an existing draft: use update_article.

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": {
      "title": "<title>",
      "contentHtml": "<contentHtml>"
    },
    "name": "create_article"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Cel mult 3 etichete
`title`	Yes	Titlul articolului.
`excerpt`	No	Rezumatul articolului.
`seoTitle`	No	Titlul SEO (eticheta title), ideal sub 60 de caractere.
`campaignId`	No	Campania (planul editorial) în care intră
`contentHtml`	Yes	Corpul articolului, HTML curat (p, h2, h3, ul, a, strong, em, img)
`focusKeyword`	No	Cuvântul-cheie principal al articolului. Ex.: implant dentar Cluj
`metaDescription`	No	Meta descrierea, ideal 140–160 de caractere, încheiată cu punct.
`featuredImageUrl`	No	Imaginea principală, adresă publică

Output Schema

Name	Required	Description
`id`	No	string. The new draft.
`title`	No	string
`status`	No	string
`version`	No	number

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

Previous value: -"Rezumatul articolului, cel mult 1.000 de caractere."New value: +"Rezumatul articolului."

changedInput schema / properties / metaDescription / description

Previous value: -"Meta descrierea pentru motoarele de căutare, cel mult 320 de caractere (ideal 140–160), încheiată cu punct."New value: +"Meta descrierea, ideal 140–160 de caractere, încheiată cu punct."

changedInput schema / properties / seoTitle / description

Previous value: -"Titlul SEO (eticheta title), cel mult 200 de caractere (ideal sub 60)."New value: +"Titlul SEO (eticheta title), ideal sub 60 de caractere."

changedInput schema / properties / title / description

Previous value: -"Titlul articolului, 3–300 de caractere."New value: +"Titlul articolului."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "id": {
+      "description": "string. The new draft."
+    },
+    "status": {
+      "description": "string"
+    },
+    "title": {
+      "description": "string"
+    },
+    "version": {
+      "description": "number"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedNov 7, 2026

addedInput schema / properties / excerpt / description

Added value: +"Rezumatul articolului, cel mult 1.000 de caractere."

addedInput schema / properties / focusKeyword / description

Added value: +"Cuvântul-cheie principal al articolului. Ex.: implant dentar Cluj"

addedInput schema / properties / metaDescription / description

Added value: +"Meta descrierea pentru motoarele de căutare, cel mult 320 de caractere (ideal 140–160), încheiată cu punct."

addedInput schema / properties / seoTitle / description

Added value: +"Titlul SEO (eticheta title), cel mult 200 de caractere (ideal sub 60)."

addedInput schema / properties / title / description

Added value: +"Titlul articolului, 3–300 de caractere."

Changed2 schema fields changedNov 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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)$"

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / tags

Added value: +{
+  "description": "Cel mult 3 etichete",
+  "items": {
+    "maxLength": 60,
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

First observedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, but the description adds genuine behavioral context beyond them: nothing is published, the call is free, content must be HTML, and there are per-type acceptance thresholds (100 words for press releases, 150 words plus an external link for SEO articles). It does not say what happens when those thresholds fail (rejection vs. silent acceptance), which is the remaining gap for a validation-heavy write.

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?

Dense and front-loaded: the core action and its non-publishing nature come first, then content rules, then the when-to-use routing. The language switches mid-description between Romanian and English, which is slightly jarring, but no sentence is filler.

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?

With nine parameters, two required, an output schema present, and full schema coverage, the description supplies the missing operational layer: draft-not-publish semantics, content format, editorial minimums, and cost. Only the failure behavior for content that violates the word-count or link rules is left unstated.

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 the schema already documents all nine fields and the baseline would be 3. The description still adds meaning the schema lacks: the content must be HTML, the word-count and external-link requirements that determine whether contentHtml is acceptable, and the advice to use unique texts across multiple publications.

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 and resource ("Salvează un articol ca ciornă") and immediately bounds scope with "(nu publică nimic)", so an agent knows this creates an unpublished draft rather than publishing content. It also contrasts explicitly with update_article, making it distinguishable from the closest sibling without opening either 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?

The English sentence gives an explicit trigger ("Use when the user provides or asks you to write a text that should be saved as a draft") and an explicit exclusion with the named alternative ("Do not use when changing an existing draft: use update_article"). Both the when and the when-not are covered with a concrete routing rule.

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

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