Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by ckalima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pipedrive_update_organization

Idempotent

Update an existing Pipedrive organization's name, address, owner, labels, visibility, and custom fields by specifying its ID.

Instructions

Update an existing organization in Pipedrive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "pipedrive_update_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrganization ID to update
nameNoNew name
addressNoNew organization address as a structured object (v2). Provide 'value' for the full address.
owner_idNoNew owner user ID
label_idsNoLabel IDs to set on organization
visible_toNoNew visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company
custom_fieldsNoCustom field values as object with field keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.4.0
    • changedInput schema / properties / address / description
      Previous value: -"New address"New value: +"New organization address as a structured object (v2). Provide 'value' for the full address."
    • addedInput schema / properties / address / properties
      Added value: +{
+  "admin_area_level_1": {
+    "description": "Admin area level 1 (e.g. state)",
+    "type": "string"
+  },
+  "admin_area_level_2": {
+    "description": "Admin area level 2 (e.g. county)",
+    "type": "string"
+  },
+  "country": {
+    "description": "Country",
+    "type": "string"
+  },
+  "locality": {
+    "description": "Locality (e.g. city)",
+    "type": "string"
+  },
+  "postal_code": {
+    "description": "Postal code",
+    "type": "string"
+  },
+  "route": {
+    "description": "Route (e.g. street)",
+    "type": "string"
+  },
+  "street_number": {
+    "description": "Street number",
+    "type": "string"
+  },
+  "sublocality": {
+    "description": "Sublocality (e.g. neighborhood)",
+    "type": "string"
+  },
+  "subpremise": {
+    "description": "Subpremise (e.g. apartment/suite number)",
+    "type": "string"
+  },
+  "value": {
+    "description": "The full address",
+    "type": "string"
+  }
+}
    • changedInput schema / properties / address / type
      Previous value: -"string"New value: +"object"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations provide idempotentHint=true and destructiveHint=false, but the description does not add further behavioral context (e.g., partial update behavior, permissions, or error scenarios). For a mutation tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is concise and front-loaded. It contains no fluff, though it could be slightly more informative.

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

Completeness2/5

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

Despite good input schema coverage, the description lacks information about return values (no output schema) and does not explain update behavior or side effects. A more complete description would discuss partial updates and the response.

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 baseline is 3. The description itself does not add parameter-level details beyond what the schema already provides.

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?

The description clearly states the action ('Update') and resource ('existing organization'), distinguishing it from the sibling 'pipedrive_create_organization'. It is specific and 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'pipedrive_create_organization' for creation). There are no prerequisites or exclusions mentioned.

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