Skip to main content
Glama

Create news

create_news

Publish news announcements in OpenProject to share release notes, weekly reports, or maintenance updates with the entire project team.

Instructions

Publish a news announcement in a project.

Use it for release notes, a weekly report, a maintenance window — anything the whole project should see on its overview page. The author is the authenticated account and is set by the server; project members watching the project are notified.

Returns the created entry {id, title, summary, description, project, author, created_at, updated_at, can_manage}; the id is what update_news and delete_news consume.

Pitfalls: this needs the 'manage news' permission in that project, which exists only while the project has the news module enabled — a 403 is about the account or the module, never about the text. title is required and rejected when blank (checked here, before the request). There is no draft state: the entry is public to everyone who can view the project the moment it is created. News is not a work package — for something that needs assigning and tracking use create_work_package instead.

Cross-references: list_news to see what is already published (and to avoid duplicates); update_news to correct an entry afterwards; list_projects for the project id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesHeadline, required, up to 256 characters. This is what readers see in the project overview and in notification digests.
summaryNoOptional teaser shown under the headline, up to 255 characters. Plain text, not markdown. Omit for none.
project_idYesNumeric id (or URL identifier, resolved for you) of the project to publish in. The project cannot be changed afterwards, and it must have the news module enabled.
descriptionNoThe announcement body as markdown — headings, lists and links all render. Omit for a headline-only entry.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNews id — what get_news, update_news and delete_news consume.
titleNoHeadline of the announcement.
authorNoUser who published it ({id, name}); set by the server.
projectNoProject the announcement belongs to ({id, name}).
summaryNoShort teaser OpenProject shows under the headline; may be empty. The full body is NOT here — read it with get_news(news_id=...).
can_manageNoTrue when this account may change or delete this entry (OpenProject renders the update/delete links only with the 'manage news' permission). False means update_news and delete_news would fail with 403.
created_atNoISO 8601 UTC publication timestamp.
updated_atNoISO 8601 UTC timestamp.
descriptionNoThe announcement body as markdown (raw); html is dropped. Empty string when the entry has only a headline and summary.
Behavior5/5

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

Goes far beyond the basic annotations by disclosing server-set author, member notifications, permission requirements ('manage news'), 403 semantics, no draft state, immediate public visibility, and that the returned id feeds update/delete tools. This rich behavioral context is not present in the annotations.

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 description is long but well-structured: one-sentence purpose, usage, return shape, pitfalls, and cross-references. Every section earns its place; the pitfalls are essential. While not ultra-short, the length is justified by the tool's complexity and failure modes.

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?

Covers all bases: purpose, usage, expected output, permissions, edge cases (403, blank title), API behavior (no draft, immediate public), and relationships to sibling tools. The output schema is explained with the returned fields and how the id is consumed. Very complete for a create operation.

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 description coverage is 100%, so baseline is 3. The description adds meaningful extra context: project_id cannot be changed afterwards, title blank-check happens before the request, summary is plain text not markdown, and description supports markdown. This goes beyond the schema's own field descriptions.

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?

The description opens with a specific verb and resource: 'Publish a news announcement in a project.' It clearly defines the scope (project overview page) and explicitly distinguishes this from work packages ('News is not a work package'), making it easy to identify against siblings like create_work_package.

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?

Provides explicit when-to-use guidance: 'Use it for release notes, a weekly report, a maintenance window — anything the whole project should see on its overview page.' It also names an alternative: 'use create_work_package instead' for assignable/trackable items, and cross-references list_news/update_news/list_projects.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kar-thik/openproject-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server