Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_organizations_search

Search Pipedrive organizations by name, address, or custom fields to find company records and retrieve matching results with pagination.

Instructions

Search organizations by name, address, or custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term
limitNoNumber of search results per page (default 10, max 50)
cursorNoOpaque token from previous response to fetch the next page
fieldsNoFields to search in (e.g. 'name,address,custom_fields')
exact_matchNoWhether to do an exact match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque token from previous response to fetch the next page"
    • addedInput schema / properties / exact_match / description
      Added value: +"Whether to do an exact match"
    • addedInput schema / properties / fields / description
      Added value: +"Fields to search in (e.g. 'name,address,custom_fields')"
    • removedInput schema / properties / include_fields
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / limit / description
      Added value: +"Number of search results per page (default 10, max 50)"
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/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, and it discloses almost nothing: no note on pagination behavior, result caps (limit max 50), permission requirements, or whether exact_match changes matching semantics. Only the safe read nature is inferable from 'search'.

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?

A single front-loaded sentence with no filler; nothing is wasted. It is arguably under-specified rather than padded, so it earns good but not top marks for structure.

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?

With no annotations and no output schema, the description should carry more weight for a 5-parameter search tool. Pagination, result shape, and exact-match behavior are all left to the schema, which is adequate but leaves the agent without return-value expectations.

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 all five parameters are already documented in the schema, establishing a baseline of 3. The description's mention of name/address/custom fields loosely maps to the 'fields' parameter but adds no syntax or behavior beyond the schema.

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 ('Search organizations') and lists the searchable dimensions (name, address, custom fields), which conveys the search semantics. However, it never distinguishes itself from the sibling pipedrive_organizations_list or pipedrive_organizations_get, so an agent must infer the boundary.

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 when-to-use guidance, no exclusions, and no mention of the obvious alternatives (organizations_list for browsing, organizations_get for a known ID). Usage is only implied by the word 'search'.

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