Postly MCP

Get Ads Overview

postly_get_ads_overview

Read-onlyIdempotent

Fetches paid ads performance for one connected ad account: spend, impressions, clicks, conversions, CTR, CPC, CPM, cost per result, and ROAS, with a per-campaign breakdown. Use a period of 1 to 90 days, or all_time where the network supports it. Requires ads.read.

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": {
      "workspace_id": "<workspace_id>",
      "account": "<account>"
    },
    "name": "postly_get_ads_overview"
  }
}

Input Schema

Name	Required	Description
`from`	No	Start date as YYYY-MM-DD. Required unless all_time.
`until`	No	End date as YYYY-MM-DD, at most 90 days after from. Required unless all_time.
`account`	Yes	Ad account key as provider:account_id, for example google:1234567890.
`all_time`	No	Use lifetime totals where the network supports them.
`campaign_id`	No	Optional native ad campaign ID to focus the overview on.
`workspace_id`	Yes	Postly workspace ID.

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description doesn't need to repeat safety. It instead adds real behavioral context: the ads.read scope requirement and the network-dependent limitation on all_time. It stops short of describing pagination or how per-campaign rows are ordered/limited.

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 front-loaded sentences with no filler; the metric enumeration is dense but arguably redundant given an output schema exists. Nothing is buried or repeated.

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

Completeness4/5

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

With an output schema, rich read-only annotations, and full parameter coverage, the description supplies the remaining essentials: auth scope, date-range bounds, and the per-campaign granularity. Only account/currency or timezone conventions are unaddressed, which is minor.

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 adds only the 1-day lower bound on the period (the schema states the 90-day upper bound) and restates the all_time network caveat already present in the schema, so it contributes little beyond structured fields.

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 a specific verb ('Fetches') and resource ('paid ads performance for one connected ad account') and enumerates the exact metrics returned plus the per-campaign breakdown. This clearly separates it from postly_get_account_analytics and postly_list_ad_campaigns, though it never names an alternative 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?

Gives one concrete usage rule — a period of 1 to 90 days, or all_time where supported — plus the ads.read prerequisite. It does not say when to choose this over postly_get_campaign_report or postly_compare_ads, so routing between the ads analytics siblings is left to inference.

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

All Postly MCP tools Inspect

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

Need Help?