Post a message into a legacy Chat view with optional notification to all members.
Post a message into a legacy Chat view. Optionally notify all members of the view. Returns the created message's id.
| Name | Required | Description | Default |
|---|---|---|---|
| view_id | Yes | ID of the Chat view to post into. | |
| comment_text | Yes | The message body text (plain text or ClickUp markdown). | |
| notify_all | No | If true, notify everyone with access to the view. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It mentions 'legacy Chat view' (implying an older system) and returns the created message's ID, but does not cover permissions, error conditions, rate limits, or any side effects beyond the optional notification.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-loading the main action, with no wasted words. Every sentence adds essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is too brief given that there is no output schema and annotations are missing. It fails to explain what 'legacy Chat view' entails, error scenarios, or how it relates to other chat tools in the sibling list.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear descriptions for all three parameters. The description adds minimal value, merely restating the notify_all purpose. No additional details on parameter usage constraints beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Post a message into a legacy Chat view') and the resource ('legacy Chat view'). It distinguishes itself from siblings like create_chat_message and create_chat_message_reply by specifying 'legacy Chat view' and including the optional notify_all feature.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Siblings include create_chat_message (modern chat), create_chat_message_reply, etc., but the description does not explain which one to choose or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/helbertparanhos/clickup-mcp-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server