Skip to main content
Glama

persons_add_picture

Upload an image to set or update a person's profile picture in Pipedrive. Supports optional cropping for precise image adjustment.

Instructions

Add or update a person's profile picture.

Uploads an image file to set as the person's profile picture. The image will be:

  • Displayed in person records

  • Shown in lists and search results

  • Visible to users with access to the person

  • Used across the Pipedrive interface

Image requirements:

  • Format: JPEG, PNG, GIF

  • Recommended size: 512x512 pixels

  • Maximum file size: Typically 5-10 MB (check Pipedrive limits)

Cropping parameters (optional):

  • Use crop_x, crop_y to set the top-left corner of the crop area

  • Use crop_width, crop_height to define the crop dimensions

  • All crop values are in pixels

  • If not provided, the full image is used

Workflow:

  1. Read the image file as a Buffer

  2. Provide the filename (with extension)

  3. Optionally specify crop parameters

  4. The tool uploads and sets the picture

Use cases:

  • Adding profile photos for contacts

  • Updating person images

  • Visual identification in CRM

  • Personalization and branding

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPerson ID
fileYesBase64-encoded image file or file buffer
filenameYesName of the image file (e.g., "photo.jpg")
crop_xNoX coordinate for cropping (pixels)
crop_yNoY coordinate for cropping (pixels)
crop_widthNoWidth of crop area (pixels)
crop_heightNoHeight of crop area (pixels)
Behavior5/5

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

With no annotations, the description fully explains behavioral traits: how the image is displayed, requirements (format, size, file size), optional cropping, and workflow. It is transparent about what the tool does.

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 well-structured with sections (image display, requirements, cropping, workflow, use cases). It is detailed but not overly verbose, with each section adding value.

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?

No output schema exists, but the description does not mention return values or error handling. It covers image requirements and usage well, but fails to describe what the tool returns (e.g., success message, picture URL) or potential errors.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining cropping in pixels, file format requirements, and workflow steps that contextualize parameters like file, filename, and crop_*.

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 'Add or update a person's profile picture,' using a specific verb and resource. It distinguishes from sibling tool persons_delete_picture by focusing on adding/updating, not deleting.

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?

Provides workflow steps, image requirements, and use cases (e.g., adding profile photos, updating images). It gives clear guidance on when to use, though it could explicitly mention when not to use or 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