Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_organizations_create

Create a new organization in Pipedrive with custom fields by name or key, and set labels via label_ids.

Instructions

Create a new organization. Supports custom fields by name or key, and the native Label field via label_ids (IDs or label names).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOrganization name
addressNoOrganization address
owner_idNoUser ID of the owner
label_idsNoNative Label field. Label option IDs or label names (e.g. [367] or ['Test / Internal']). Replaces existing labels; pass [] to clear. Sent as top-level label_ids, not a custom field.
visible_toNoVisibility: 1=owner only, 3=owner's group, 5=owner's group+sub, 7=everyone
custom_fieldsNoCustom fields by API key (e.g. { 'abc123hash': 'value' })
custom_fields_by_nameNoCustom fields by human-readable name (e.g. { 'Tier': 'Enterprise' })

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • addedInput schema / properties / address / description
      Added value: +"Organization address"
    • addedInput schema / properties / custom_fields / description
      Added value: +"Custom fields by API key (e.g. { 'abc123hash': 'value' })"
    • addedInput schema / properties / custom_fields_by_name / description
      Added value: +"Custom fields by human-readable name (e.g. { 'Tier': 'Enterprise' })"
    • addedInput schema / properties / label_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Native Label field. Label option IDs or label names (e.g. [367] or ['Test / Internal']). Replaces existing labels; pass [] to clear. Sent as top-level label_ids, not a custom field."
+}
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / visible_to / description
      Added value: +"Visibility: 1=owner only, 3=owner's group, 5=owner's group+sub, 7=everyone"
  2. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful payload behavior — custom fields can be addressed by name or API key, and label_ids accepts IDs or label names — but says nothing about required permissions, duplicate-name behavior, defaults for owner_id/visible_to, or what the call returns.

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, action first, with the special-case parameters (custom fields, labels) in the follow-up. No filler or restatement of the tool name.

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?

A 7-parameter mutation tool with nested objects, no annotations and no output schema needs more than this. The parameter surface is covered by the schema, but an agent gets no signal about write permissions, duplicate handling, or the shape of the created record.

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 description coverage is 100%, so the schema already explains name, address, owner_id, visible_to and label_ids in detail; the description only echoes that custom fields work by name or key. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a new organization") that an agent can immediately separate from the sibling read tools (organizations_list/get/search) and the mutating siblings (update/delete/merge). It does not explicitly name or contrast those siblings, but the create semantics are unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing about duplicate handling, whether to search for an existing organization first (organizations_search exists), or prerequisites such as owner/visibility defaults. Usage is only implied by the verb.

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

Deploy Server

Other Tools