Skip to main content
Glama

Local Services ads report

local_services_report
Read-only

Generates a read-only Local Services ads report covering campaign spend, leads by type and status, charges, credits, and Google verification checks; excludes lead contact details.

Instructions

Local Services ads (read-only): spend per Local Services campaign, leads by type, status, charge and credit, and Google's verification checks on the business. No lead contact details.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "local_services_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.44.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so 'read-only' is largely redundant. The one genuinely additive detail is the data-scope caveat that lead contact details are excluded, which prevents wasted calls. Nothing is said about response size, pagination, or whether the look-back window affects data freshness, so the added value beyond annotations is modest.

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?

A single compact sentence front-loads the tool's domain and immediately follows with the list of report sections. Every clause carries information about content or scope; 'read-only' is the only near-redundant element given the annotations.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the report sections plus the exclusion of lead contact data. For a two-parameter read-only report tool this is sufficient, though it could note that results are scoped to the customer_id account rather than aggregated across accounts.

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%, with both parameters (customer_id, days) fully documented including the 1-90 range and the default of 30. The description adds no parameter-level meaning such as how the look-back window interacts with lead status or credit reporting, so the baseline of 3 applies.

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 names the specific resource (Local Services ads) and enumerates the report content: spend per campaign, leads by type, status, charge/credit, and verification checks. This clearly separates it from generic siblings like analytics_report or merchant_report. It lacks an explicit verb (e.g., 'retrieve' or 'returns'), but the noun-plus-contents phrasing makes the operation unambiguous.

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 '(read-only)' marker and 'No lead contact details' set expectations about what this tool is and is not for, implying it is the reporting path for Local Services advertisers. However, no explicit when-to-use guidance or routing against alternatives such as run_gaql is given, so the agent must infer selection from the domain name alone.

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