Skip to main content
Glama

call_logs_create

Create a call log with phone number, outcome, and timestamps. Link it to contacts, deals, or leads in Pipedrive.

Instructions

Add a new call log to track phone call activity.

Creates a call log with phone numbers, outcome, duration, and timestamps. Can be linked to persons, organizations, deals, leads, and activities.

Workflow tips:

  • to_phone_number, outcome, start_time, and end_time are required

  • Outcome describes call result (e.g., connected, no_answer, busy, voicemail)

  • Use ISO 8601 format for timestamps

  • Link to records using person_id, org_id, deal_id, or lead_id

  • Associate with an activity using activity_id

  • Add notes for call details

Common use cases:

  • Log successful call: { "to_phone_number": "+1234567890", "outcome": "connected", "start_time": "2024-12-10T10:00:00Z", "end_time": "2024-12-10T10:15:00Z" }

  • Log missed call: { "to_phone_number": "+1234567890", "outcome": "no_answer", "start_time": "2024-12-10T10:00:00Z", "end_time": "2024-12-10T10:00:30Z" }

  • Link to person: Include "person_id": 123

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_phone_numberYesPhone number called
outcomeYesCall outcome (e.g., connected, no_answer, busy, voicemail)
start_timeYesCall start time in ISO 8601 format
end_timeYesCall end time in ISO 8601 format
user_idNoID of the user who made the call
activity_idNoID of the associated activity
subjectNoCall subject/title
durationNoCall duration in seconds (e.g., "120")
from_phone_numberNoPhone number that made the call
person_idNoID of the person associated with the call
org_idNoID of the organization associated with the call
deal_idNoID of the deal associated with the call
lead_idNoUUID of the lead associated with the call
noteNoAdditional notes about the call
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 burden. It explains that the tool creates a record and can link to other entities, but does not disclose side effects, rate limits, or specific permissions needed. It is adequate but not highly detailed.

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 moderately long but well-organized with sections like 'Workflow tips' and 'Common use cases'. The first sentence immediately conveys the purpose. There is minimal redundancy.

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

Completeness4/5

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

Given the tool's complexity (14 parameters, no output schema), the description provides examples and tips that cover common scenarios. It could mention expected return values, but overall it is fairly complete.

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 clarifying the meaning of 'outcome', specifying ISO 8601 format for timestamps, and providing examples. This goes beyond the schema descriptions.

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 the tool's purpose: 'Add a new call log to track phone call activity.' It specifies the verb (create) and resource (call log), and distinguishes from sibling tools like call_logs_list, call_logs_get, etc.

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?

The description provides workflow tips, lists required fields, and includes common use cases with example JSON objects. It gives clear context but does not explicitly state when not to use this tool.

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