Skip to main content
Glama

activities_create

Create a new activity by specifying subject, type, and due date. Optionally link to deals, persons, organizations, projects, or leads.

Instructions

Create a new activity. Subject, type, and due_date are required. Can link to deals, persons, organizations, projects, or leads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesActivity subject (required)
typeYesActivity type (required)
due_dateYesDue date in YYYY-MM-DD format (required)
due_timeNoDue time in HH:MM format (optional)
durationNoDuration in HH:MM format (optional)
user_idNoUser ID to assign the activity to
deal_idNoDeal ID to link the activity to
person_idNoPerson ID to link the activity to
org_idNoOrganization ID to link the activity to
project_idNoProject ID to link the activity to
lead_idNoLead ID to link the activity to
noteNoActivity note
locationNoActivity location
public_descriptionNoPublic description
busy_flagNoMark as busy in calendar
participantsNoArray of participants
attendeesNoArray of attendees
doneNoMark as done
custom_fieldsNoCustom fields as key-value pairs
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the creation action and linking capability but omits information about idempotency, side effects, permission requirements, or error handling.

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 extremely concise with two sentences covering purpose, required fields, and linking capabilities. No unnecessary words or redundancy.

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?

Given the complexity (19 parameters, no output schema, no annotations), the description provides essential purpose but lacks behavioral details, error scenarios, or return value hints. It is adequate but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by highlighting required fields and linking options. However, most parameters are self-explanatory from the schema, so the description's incremental contribution is moderate.

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 the action ('Create a new activity') and identifies the resource. It distinguishes from sibling tools like activities_update or activities_list by specifying the creation action and required fields.

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?

The description specifies required parameters (subject, type, due_date) and optional linking to deals, persons, etc., providing context for when to use this tool. However, it does not explicitly state when not to use it or compare to alternatives.

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/iamsamuelfraga/mcp-pipedrive'

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