AIsa Apollo

Update Call Records

put_apollo_phone_calls_id

Destructive

Update call records. Requires a master API key.

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`id`	Yes	Call record ID.
`logged`	No	Whether to create an individual record.
`status`	No	Call status.
`user_id`	No	Caller user IDs.
`duration`	No	Duration in seconds.
`end_time`	No	ISO 8601 end time.
`to_number`	No	Dialed phone number.
`account_id`	No	Account ID.
`contact_id`	No	Contact ID.
`start_time`	No	ISO 8601 start time.
`from_number`	No	Caller phone number.
`phone_call_outcome_id`	No	Outcome ID.
`phone_call_purpose_id`	No	Purpose ID.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes one genuinely non-redundant fact — the master API key requirement — but says nothing about what the destructive update replaces, whether omitted fields are cleared or preserved, or PUT replace-vs-merge semantics.

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 prose is two short, front-loaded sentences with no filler. The injected pricing HTML comment block is noise, but the authored content itself is tight and not padded.

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?

With an output schema present, return values need not be explained, and all parameters are documented in the schema. However, for a 13-parameter destructive mutation with destructiveHint=true and idempotentHint=false, the description omits partial-vs-full update semantics and any effect of the call, leaving the definition only minimally viable.

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% across all 13 parameters, so the schema already carries the semantics and the baseline of 3 applies. The description adds no parameter-level meaning (e.g., that only the required id is needed and the rest are optional fields to change), leaving it purely a restatement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Update call records"), which is marginally more informative than the name alone, but it adds no detail beyond the title "Update Call Records" and does not distinguish this mutation endpoint from siblings such as post_apollo_phone_calls or get_apollo_phone_calls_search. It is clear but generic.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., post_apollo_phone_calls for creation), and no exclusions. "Requires a master API key" is a prerequisite, not usage guidance, so the agent gets no routing help.

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

All AIsa Apollo 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?