Skip to main content
Glama
victorbenazzi

Ploomes MCP Server

Create Task

ploomes_tasks_create

Create a new task in Ploomes CRM with title, description, due date and time, and optional links to deals or contacts. Supports custom fields via OtherProperties.

Instructions

Create a new task in Ploomes CRM. Attach to a deal via DealId or to a contact via ContactId. Date and Hour are separate fields: Date is the due date (ISO 8601), Hour is the time component as a string (e.g., '14:30'). Use OtherProperties to set custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
TitleNoTask title / short summary
DescriptionNoTask description with details about what needs to be done
DateNoDue date in ISO 8601 format. This is the date component only — use Hour for the time. E.g.: "2025-06-15T00:00:00Z"
HourNoTime component as a string, separate from Date. E.g.: "14:30", "09:00". This is NOT part of the Date field — they are sent independently
DealIdNoAssociated deal ID — links the task to a specific deal/opportunity
ContactIdNoAssociated contact ID — links the task to a specific contact
OwnerIdNoOwner user ID — the user responsible for this task (use ploomes_users_list to find valid IDs)
TypeIdNoTask type ID — defines the kind of task (use ploomes_tasks_types_list to find valid IDs, e.g., Call, Meeting, Email, Visit)
OtherPropertiesNoCustom field values for the task (use ploomes_fields_list to discover available fields)
Behavior4/5

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

Annotations confirm the tool is not read-only, not destructive, and open-world. The description adds value by explaining that Date and Hour are separate fields and that OtherProperties is for custom fields. It does not contradict annotations and provides useful behavioral context beyond them.

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?

The description is two sentences with no unnecessary words. It front-loads the main purpose and immediately provides key usage details. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers input well but does not mention what the tool returns (e.g., created task object). Given no output schema, this is a gap. It also lacks guidance on validation or error conditions. Otherwise, it is adequate for a create tool.

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 is 3. The description adds meaning by clarifying that Hour is not part of Date and by referencing sibling tools (ploomes_users_list, ploomes_tasks_types_list, ploomes_fields_list) for valid IDs. This goes beyond the schema 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 clearly states that the tool creates a new task in Ploomes CRM, specifies how to attach to deals or contacts, and highlights key details about date/hour separation and custom fields. This differentiates it from sibling tools like tasks_update, tasks_delete, etc.

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

Usage Guidelines3/5

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

The description implies the tool is for creating new tasks and mentions attachment options, but it does not explicitly state when to use it versus alternatives (e.g., update, delete) or provide any exclusions. Usage is derived from 'Create' in the name rather than explicit guidance.

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/victorbenazzi/ploomes-mcp-server'

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