Skip to main content
Glama

MetricPort

Hour and weekday performance

ads_dayparting
Read-onlyIdempotent

Cost, clicks, conversions and CPA by hour of day and by day of week. Basis for ad schedules and bid adjustments.

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": {
      "property": "<property>"
    },
    "name": "ads_dayparting"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNo
campaignNo
propertyYesGoogle Ads customer id from list_properties, e.g. 1234567890
startDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered. Beyond that the description adds little: no note on date-range defaults, possible row volume (hours×weekdays), or auth requirements for the Google Ads customer id. It only states the metric set already implied by annotations.

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?

Two compact sentences, front-loaded with the metric and grouping dimensions. Efficient, though the second sentence is somewhat thin rather than explanatory.

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?

A read-only report tool with three undocumented parameters, no output schema, and no mention of return shape or date-range behavior. An agent knows what it reports but not how to scope the call correctly.

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?

Schema coverage is 25% — only 'property' is documented. The description says nothing about campaign filtering, startDate/endDate semantics (format, default range, max window), or how campaign and dates interact, leaving three of four params unexplained.

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?

States specific metrics (cost, clicks, conversions, CPA) and the two dimensions (hour of day, day of week). Distinguishes itself from siblings like ads_device_performance or ads_geo_performance by dimension, though it doesn't name a sibling explicitly.

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?

'Basis for ad schedules and bid adjustments' implies when the output is useful, but there's no explicit guidance on when to choose this over ads_campaign_performance or ads_daily_trend, no prerequisites, and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.