Skip to main content
Glama
jie8357IOII

google-my-business-mcp

by jie8357IOII

gmb_performance_locations_fetchmultidailymetricstimeseries

Read-onlyIdempotent

Fetch daily performance metrics for a Google Business Profile location over a specified date range. Returns per-day values for selected metrics like calls, clicks, and impressions to analyze trends.

Instructions

GET v1/{+location}:fetchMultiDailyMetricsTimeSeries. Returns the values for each date from a given time range that are associated with the specific daily metrics. Note: Only daily data is available. Hourly metrics are not supported. Example request: GET https://businessprofileperformance.googleapis.com/v1/locations/12345:fetchMultiDailyMetricsTimeSeries?dailyMetrics=WEBSITE_CLICKS&dailyMetrics=CALL_CLICKS&daily_range.start_date.year=2022&daily_range.start_date.month=1&daily_range.start_date.day=1&daily_range.end_date.year=2022&daily_range.end_date.month=3&daily_range.end_date.day=31

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoSelector specifying which fields to include in a partial response.
$.xgafvNoV1 error format.
locationYesRequired. The location for which the time series should be fetched. Format: locations/{location_id} where location_id is an unobfuscated listing id.
quotaUserNoAvailable to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
prettyPrintNoReturns response with indentations and line breaks.
dailyMetricsNoRequired. The metrics to retrieve time series for.
dailyRange.endDate.dayNoDay of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
dailyRange.endDate.yearNoYear of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
dailyRange.endDate.monthNoMonth of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
dailyRange.startDate.dayNoDay of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
dailyRange.startDate.yearNoYear of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
dailyRange.startDate.monthNoMonth of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the important limitation that hourly metrics are not supported, and the example request clarifies the URL structure. This goes beyond annotations without contradicting them.

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 reasonably concise, front-loads the purpose, and includes a practical example. The URL in the example is long but serves as a concrete illustration. No unnecessary filler.

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?

Despite no output schema, the description adequately states what is returned (values per date) and key constraints (daily only). With 12 parameters, the schema and example cover usage. Some details about response format are missing but not critical given the clarity of the purpose.

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

Parameters4/5

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

Schema description coverage is 100%, so parameters are already well-documented. The description's example request adds value by showing how to specify multiple dailyMetrics and construct the date range, which helps parameter usage.

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 tool returns daily metric values for each date in a given time range. The verb 'Returns' and resource 'daily metrics time series' are specific. However, it does not differentiate from the similar sibling tool 'gmb_performance_locations_getdailymetricstimeseries'.

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?

The description provides no guidance on when to use this tool versus alternatives. It notes that only daily data is available, which is a constraint rather than usage guidance. No alternative tools or scenarios are mentioned.

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/jie8357IOII/google-my-business-mcp'

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