Skip to main content
Glama

AdAce Ads

by website.adace
OverviewDiscussionsAdmin

Account performance

get_performance
Read-onlyIdempotent

Account performance for the period: impressions, clicks, spend, conversions, CTR, CPC by campaign. null means “unavailable”, not zero. Days in preliminary_days may still change.

Input Schema

NameRequiredDescriptionDefault
date_toNoPeriod end, YYYY-MM-DD, no later than yesterday; up to 31 days. Optional: by default yesterday (the account's time zone when known, otherwise UTC).
date_fromNoPeriod start, YYYY-MM-DD, a completed day. Optional: without dates the last 7 completed days are used (date_from = date_to − 6 days).
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / date_from / description
      Previous value: -"Period start, YYYY-MM-DD, a completed day"New value: +"Period start, YYYY-MM-DD, a completed day. Optional: without dates the last 7 completed days are used (date_from = date_to − 6 days)."
    • changedInput schema / properties / date_to / description
      Previous value: -"Period end, YYYY-MM-DD, no later than yesterday; up to 31 days"New value: +"Period end, YYYY-MM-DD, no later than yesterday; up to 31 days. Optional: by default yesterday (the account's time zone when known, otherwise UTC)."
    • changedInput schema / required
      Previous value: -[
-  "account_id",
-  "date_from",
-  "date_to"
-]New value: +[
+  "account_id"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already covering the read-only, idempotent, and non-destructive nature, the description adds valuable behavioral context: null values mean 'unavailable' rather than zero, and preliminary days may still change. This goes beyond structured data without contradicting it.

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 a single front-loaded sentence followed by two brief clarifications. Every sentence earns its place with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description lists the returned metrics, clarifies null semantics, and notes the preliminary days caveat. Date defaults are covered in the schema, and annotations handle safety. The definition is complete for correct invocation.

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 67%; date_to and date_from are documented in the schema, but account_id is not. The description adds no parameter-level meaning beyond what the schema already provides, so a baseline 3 is appropriate.

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 clear purpose: retrieving account performance metrics (impressions, clicks, spend, conversions, CTR, CPC) by campaign for a period. It is specific about what the tool does but does not explicitly distinguish it from siblings like compare_periods or find_anomalies.

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?

No guidance on when to use this tool versus alternatives is provided. The description only describes the output, leaving the agent to infer the appropriate context from the name and siblings.

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

All AdAce Ads 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