Skip to main content
Glama
HyrosOG

Hyros MCP

by HyrosOG

Attribution Report

hyros_get_attribution_report
Read-only

Retrieve attribution metrics (ROAS, revenue, cost, ROI) for specific ads, campaigns, or ad sets across platforms. Identify best-performing ads and optimize spend.

Instructions

Get detailed attribution metrics for specific ads, campaigns, or ad sets. Use this to answer "what is my ROAS?", "how much did I earn vs spend?", "which ad has the best ROI?". Requires specifying the level (e.g., facebook_adset, google_campaign) and the IDs to query. Use hyros_get_sources to find source IDs first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated IDs based on the level (required, unless level is google_v2_keyword). E.g. for facebook_adset use the adset IDs. Use isAdAccountId=true to provide an ad account ID and get all sources within it.
levelYesAttribution level (required): the granularity of the report. Use facebook_adset for Facebook ad sets, google_campaign for Google campaigns, etc.
fieldsYesComma-separated metrics (required). Options: revenue,cost,sales,leads,calls,roas,roi,profit,refund,unique_sales,new_leads,cost_per_lead,cost_per_sale,cost_per_call,clicks,impressions,ctr,cpm,cvr,qualified_calls,unqualified_calls,30_days_ltv,90_days_ltv,1_year_ltv,new_mrr,churn_rate,aov,cac,name,parent_name. Example: "revenue,cost,sales,leads,roas,roi"
pageIdNoPagination page ID
endDateYesReport end date in ISO 8601 format, e.g. 2024-01-31T23:59:59 (required)
currencyNoCurrency for monetary values (default: user_currency)
pageSizeNoResults per page (1-250)
startDateYesReport start date in ISO 8601 format, e.g. 2024-01-01T00:00:00 (required)
isAdAccountIdNoIf true, the ids field should contain a single ad account ID and the report will include all sources in that account at the specified level
attributionModelYesAttribution model: last_click (last touch), scientific (AI-based), first_click (first touch)
dayOfAttributionNoIf true, filter by click date instead of sale date
timeGroupingOptionNoHow to group the results (default: source_link)
scientificDaysRangeNoDay range (1-30) for first ad attribution in scientific model (default: 30)
sourceConfigurationNoFilter by organic/paid sources (default: ignore_organic)
windowAttributionDaysRangeNoDays range for attribution window (0-365, default: 0)
Behavior3/5

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

The annotations already provide readOnlyHint=true. The description adds no further behavioral context (e.g., performance, data volume, pagination limits). It does not contradict annotations.

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 only two sentences, front-loaded with the core purpose, and each sentence adds value without redundancy.

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 high parameter count (15) and no output schema, the description covers the main use case but omits details on optional parameters like pagination, filters, and grouping. It is adequate but not comprehensive.

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 the baseline is 3. The description restates the need for level and IDs but adds no new semantic value beyond the schema descriptions.

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?

The description clearly states the tool retrieves attribution metrics for ads, campaigns, or ad sets, and provides example questions. It distinguishes itself from sibling tools like hyros_get_sources by referencing the need to use that tool first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use the tool (answering ROAS, ROI questions) and advises to use hyros_get_sources first. It does not explicitly state when not to use it, but the context is clear enough.

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