Skip to main content
Glama
HyrosOG

Hyros MCP

by HyrosOG

Ad Account Report

hyros_get_ad_account_report
Read-only

Get aggregated advertising performance metrics grouped by ad account. Analyze revenue, cost, ROAS, and other key metrics across your campaigns and ads.

Instructions

Get attribution metrics grouped by ad account. Provide the ad account ID(s) to get aggregated performance across all campaigns/ads in those accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated ad account IDs to report on (required)
fieldsYesComma-separated metrics (required). Options: revenue,cost,sales,leads,roas,roi,profit,clicks,impressions,ctr,cost_per_lead,cost_per_sale,name
pageIdNoPagination page ID
endDateYesReport end date in ISO 8601 format (required)
currencyNoCurrency for monetary values
pageSizeNoResults per page (max 250)
startDateYesReport start date in ISO 8601 format (required)
attributionModelYesAttribution model to use
dayOfAttributionNoIf true, filters by click date instead of sale date
forecastingOptionNoForecasting basis for LTV/forecast fields
scientificDaysRangeNoDay range (1-30) for first ad attribution, used with the scientific model
sourceConfigurationNoWhich sources to include in attribution
ignoreRecurringSalesNoExclude recurring sales from the report
dateTimeGroupingOptionNoGroup results by time period instead of a single aggregate row (default: ad_account). With day, a 30-day window returns 30 rows whose costs sum to the aggregate total.
newCustomerConfigurationNoCustomer cohort to include
windowAttributionDaysRangeNoAttribution window in days (0-365)
Behavior3/5

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

Annotations indicate readOnlyHint=true, so the description's 'get' aligns. However, the description adds minimal behavioral context beyond what annotations provide (e.g., no mention of rate limits or error handling).

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?

Two concise sentences with no redundancy, effectively conveying the core purpose.

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?

Given the complexity (16 parameters, no output schema), the description only covers high-level purpose. Lacks details on pagination, return format, or behavioral nuances, but schema is thorough.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema's parameter descriptions (e.g., 'ad account ID(s)' is already in schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the action ('get'), resource ('attribution metrics grouped by ad account'), and scope, clearly distinguishing it from siblings like hyros_get_attribution_report.

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 explicit guidance on when to use this tool versus alternatives such as hyros_get_attribution_report. The description only instructs to provide ad account IDs but does not exclude other scenarios.

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/HyrosOG/Hyros-MCP'

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