Conecto

Import from Pipedrive

import_from_pipedrive

Idempotent

Import a Pipedrive account: organizations (as companies), persons (as contacts, linked to their organization), deals (won, lost or the open stage, value, currency, expected close date, organization and person), notes (on their person's timeline, else added to their deal or organization) and activities (as tasks on their person, open or done, with their due time). Needs the API token of a Pipedrive user who can see the records. The API token is in Pipedrive under Settings > Personal preferences > API. Called without its token, it answers at once with a link for the owner, who types the token on a Conecto page, so it never passes through the chat (from_a_terminal does the same from a terminal); account.credential_added says when the import started, with its call_id. company_domain (the acme in acme.pipedrive.com) is optional. Wrong credentials are refused before anything is reserved or charged; the token is kept only encrypted while the import runs, then erased. Contacts match existing ones by email, companies by domain, then name. Runs in the background for up to 15 minutes and imports up to max_records records; when more remain, the result has next_cursor: call again with the same arguments plus next_cursor to continue. Running it again never duplicates anything: changed records are updated, unchanged ones skipped. Unchanged records are free, and 1,000 imported records cost $1. max_records x $0.001 is reserved while it runs and only what was imported is charged; lower max_records if your balance is smaller. Costs $0.001 per record imported (created or updated); nothing if none are found. Runs in the background: the reply has a call_id; poll it with the account_get_call tool or GET /v1/calls/.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`api_token`	No	The Pipedrive API token. Leave it out to get the link instead.
`max_records`	No	The most records this run may create or update (and reserve $0.001 each for).
`next_cursor`	No	The next_cursor a previous run of this import returned, to continue where it stopped.
`company_domain`	No	Optional: the "acme" in acme.pipedrive.com.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / api_token / description

Previous value: -"The Pipedrive API token."New value: +"The Pipedrive API token. Leave it out to get the link instead."

changedInput schema / required

Previous value: -[
-  "api_token"
-]New value: +[]

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: credential handling via a secure link, token encryption and erasure, refusal of wrong credentials before reservation, matching rules, background execution up to 15 minutes, cursor-based pagination, idempotent updates that never duplicate, and detailed cost/reservation mechanics. These details go well beyond the provided hints and are consistent with them.

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

Conciseness3/5

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

The description is front-loaded with purpose and entity mappings, which is good, but it is very long and contains noticeable redundancy—background execution and cost mechanics are each restated multiple times. It could be tightened without losing essential information.

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

Completeness5/5

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

For a complex, multi-entity import tool with no output schema, the description covers everything an agent needs: authentication flow, entity mapping, idempotency, pagination, pricing, and how to poll for completion. No key behavioral or contextual detail is missing.

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 four parameters are already documented. The description reinforces some meaning (e.g., why to leave out api_token, lowering max_records based on balance) but largely repeats what the schema already states rather than adding substantial new parameter-level semantics.

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 opens with a specific verb and resource ('Import a Pipedrive account') and immediately enumerates the exact entity mappings (organizations as companies, persons as contacts, deals, notes, activities). This clearly distinguishes it from sibling import tools such as import_from_hubspot or import_csv.

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?

It gives clear context for when to use this tool: importing a Pipedrive account, with instructions for supplying or omitting an API token, handling optional company_domain, and resuming with next_cursor. It does not explicitly state when not to use it or name alternative import tools, which is the only missing element for a 5.

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

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?