Skip to main content
Glama

odoo_message_post

Post messages or internal notes on any Odoo record's chatter with Markdown support, choosing between internal notes or public comments for followers.

Instructions

Post a message or internal note on any Odoo record (chatter). Body supports Markdown formatting (headers, bold, italic, tables, code blocks) — automatically converted to HTML. Use message_type='note' for internal notes (employees only) or 'comment' for public messages (visible to followers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNodefault
modelYesModel name (e.g. 'sale.order')
res_idYesRecord ID to post on
bodyYesMessage body in Markdown format
message_typeNonote = internal (employees only), comment = public (all followers)note
subjectNoMessage subject (optional)
partner_idsNoPartner IDs to notify (optional)
attachment_idsNoExisting ir.attachment IDs to attach (optional)
Behavior4/5

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

Discloses key behavioral traits: Markdown support with conversion to HTML, visibility differences between message_type values. No annotations provided, so description carries full burden and does it well.

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, front-loaded with main purpose. No redundant information. Every sentence earns its place.

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?

Sufficient for an 8-parameter tool without output schema. Covers purpose, key parameters, and behavioral aspects. Lacks details on return value, but not essential for invocation.

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?

Adds meaning beyond schema for body (Markdown formatting) and message_type (note vs. comment semantics). Schema already describes most params (88% coverage), so description adds value.

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?

Clearly states the action (post) and resource (message/internal note on any Odoo record chat) with specific verb and resource. Differentiates from siblings like odoo_create/odoo_write by focusing on chatter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use the tool (posting on chatter) and distinguishes between note (internal) and comment (public). Lacks explicit when-not or alternative tools, but context from siblings makes it clear.

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/rosenvladimirov/odoo-claude-mcp'

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