Skip to main content
Glama

Tendência diária

pixel_get_daily_trends
Read-only

Série temporal diária de uma métrica no período (para detectar tendências/anomalias). Métricas: commission, orders, clicks, spend (valores em centavos quando monetários).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
daysNoJanela em dias se start/end ausentes (1–366, default 30).
metricNoMétrica da série (default commission).
end_dateNoFim (yyyy-mm-dd, UTC). Opcional (default hoje).
start_dateNoInício (yyyy-mm-dd, UTC). Opcional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / days / maximum
      Added value: +366
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / end_date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
    • addedInput schema / properties / start_date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds one genuinely useful behavioral detail beyond that: monetary metrics are returned in cents. It says nothing about granularity when no data exists, timezone handling beyond the schema's UTC note, or response shape.

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 tightly packed sentences with the core scope front-loaded and the metric enumeration second. Nothing is wasted, though the parenthetical purpose clause and metric list partially repeat information available in the enum.

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?

For a read-only, zero-required-parameter tool with full schema coverage and no output schema, the essentials are present: what is returned (daily series), for which metrics, and the currency unit. Gaps remain around missing-data behavior and how the series is bounded/ordered, which matter for a time-series consumer.

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 defaults, the 1–366 day bound, the date pattern and UTC already documented per parameter. The description only echoes the metric list, so it adds no semantics the schema does not already carry; baseline 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 states a specific verb+resource combination: a daily time series of one metric over a period, and enumerates the available metrics (commission, orders, clicks, spend). It is clearly distinct from mutation siblings like pixel_set_budget or pixel_push_capi, though it names no sibling to contrast with reports such as pixel_get_dashboard_summary or pixel_get_roas.

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 parenthetical '(para detectar tendências/anomalias)' implies the intended use case — trend and anomaly detection — but gives no explicit when-to-use vs when-to-use-something-else guidance. An agent must infer that this tool is for per-metric longitudinal analysis rather than aggregate summaries.

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.

Resources