Skip to main content
Glama

call_logs_list

Retrieve call logs for the authenticated user with pagination. Access phone call details including duration, outcome, and linked records like persons and deals.

Instructions

Get all call logs assigned to the current user.

Retrieves call logs with pagination support. Returns logs for phone calls including duration, outcome, and associated records.

Workflow tips:

  • Returns call logs for the authenticated user

  • Use start and limit for pagination

  • Each call log includes phone numbers, duration, outcome, and timestamps

  • Can be linked to persons, organizations, deals, and leads

  • Cached for 1 minute for better performance

Common use cases:

  • List recent calls: { "start": 0, "limit": 50 }

  • Paginate through calls: { "start": 50, "limit": 50 }

  • Get all call history: Iterate through pages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoPagination start
limitNoNumber of items to return (max 50)
Behavior4/5

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

No annotations provided, but the description discloses caching (1 minute), return fields, and association with other entities. It also implies read-only behavior. This adds value beyond the input schema.

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 and bullet points, but could be slightly more concise. It is front-loaded with the core purpose.

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?

Covers pagination, caching, return fields, and common use cases. No output schema exists, but the description adequately explains the response structure.

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 already covers both parameters (start, limit) with descriptions. The description reinforces the max limit of 50 and provides usage examples, but does not add new semantic information beyond the schema.

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 'Get all call logs assigned to the current user' and lists specific fields (duration, outcome, associated records). It distinguishes from sibling tools like call_logs_get and call_logs_create by focusing on listing with pagination.

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 explicit workflow tips and common use cases with JSON examples for pagination. However, it does not specify when not to use this tool or mention alternatives like a search function (which doesn't exist for call logs).

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