Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

get lsa account report

get_lsa_account_report
Read-onlyIdempotent

Read the authorized advertiser's live Google Local Services aggregate account report, including actual spend, currency and charged lead totals. Requires linked manager-account access. Dates are calendar dates inclusive at both ends. Source may lag by 30 minutes. Connected phone calls means duration over 30 seconds; responsiveness is the previous 90 days. This is not signed-case revenue or lead-rating reporting.

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": {
      "business_id": "<business_id>",
      "connection_id": "<connection_id>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_lsa_account_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes
business_idYes
connection_idYes

Output Schema

NameRequiredDescriptionDefault
errorNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description adds meaningful operational context: manager-account access requirements, inclusive date semantics, a 30-minute source lag, and metric definitions for connected calls and responsiveness. It also clarifies what the report is not, reducing misuse risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded: the first sentence establishes the core operation, followed by access requirements, date semantics, freshness, metric definitions, and exclusions. Every sentence adds useful information without repetition.

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 output schema and annotations, the description covers the most important behavioral and domain context: access prerequisites, date inclusivity, data lag, metric definitions, and exclusions. It remains slightly incomplete because it does not clarify the two ID parameters or explicitly route against the closest sibling tool.

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 0%, so the description must carry parameter meaning. It adds important semantics for start_date and end_date by stating they are calendar dates inclusive at both ends, but it does not explain business_id or connection_id, leaving two required parameters under-specified.

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 states a specific verb and resource: reading the live Google Local Services aggregate account report, including spend, currency, and charged lead totals. It also distinguishes the scope from signed-case revenue and lead-rating reporting. It does not explicitly name the closest sibling, get_lsa_report, so sibling differentiation is present but not fully explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the tool is appropriate by stating it requires linked manager-account access and by excluding signed-case revenue and lead-rating reporting. However, it does not explicitly say when to use this tool versus get_lsa_report or other LSA-related siblings, leaving routing partly to inference.

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

All CallMCP — Phone Call MCP Server toolsInspect
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