Skip to main content
Glama

post_call_log_delete_all

Deletes all call log entries at once. Clears the complete call history.

Instructions

Remove all CallEntry call entries

Error codes: internal_error, invalid_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoid
typeNoThe valid call types are: — Values: `missed`: Missed incoming call; `accepted`: Incoming call; `outgoing`: Outgoing call
datetimeNoCall creation timestamp. — Unix timestamp (seconds since epoch).
numberNoCallee number for outgoing calls. Caller number for incoming calls.
nameNoCallee name for outgoing calls. Caller name for incoming calls.
durationNoCall duration in seconds.
newNoCall entry as not been acknowledged yet.
contact_idNoIf the number matches an entry in the contact database, the id of the matching contact.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

As a destructive action, the description lacks details on side effects, authorization, or irreversibility. Error codes are mentioned but not explained. No annotations to supplement.

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 very short and includes error codes, which is efficient. However, the brevity sacrifices necessary detail, making it borderline under-specified.

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

Completeness2/5

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

For a complex tool with many optional parameters and destructive behavior, the description is insufficient. It does not explain parameter usage, return behavior (despite output schema), or operational details.

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

Parameters2/5

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

Despite 100% schema coverage, the description does not clarify how the 8 optional parameters interact with the 'delete all' behavior. The name suggests no filtering, but parameters imply possible selection, causing confusion.

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?

The description clearly states the action ('Remove all CallEntry call entries') and the resource, distinguishing it from single-entry delete tools like 'delete_call_log_id' by using 'all'.

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 guidance on when to use this tool vs alternatives (e.g., 'delete_call_log_id' for single entries) or any prerequisites. Error codes hint at potential issues but do not provide usage context.

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/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server