Postly MCP

List Ads

postly_list_ads

Read-onlyIdempotent

Lists individual ads with their performance for a period, across all connected ad accounts or one account or network. Each ad includes key and snapshot_id for postly_compare_ads. Page with offset and next_offset, then next_account when several accounts are listed. 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>"
    },
    "name": "postly_list_ads"
  }
}

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.
`offset`	No
`search`	No	Optional text to match the ad, campaign, or ID.
`status`	No	Optional native status filter such as ACTIVE or PAUSED.
`account`	No	Optional account key (provider:account_id). Omit to list every connected account.
`network`	No	Optional ads network such as google or meta. Ignored when account is set.
`all_time`	No	Use lifetime totals where the network supports them.
`workspace_id`	Yes	Postly workspace ID.
`account_index`	No	Optional next_account value from a previous page.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful non-schema context: ads.read permission is required, results include key/snapshot_id for postly_compare_ads, and pagination uses offset/next_offset plus next_account for multi-account results.

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?

Three dense sentences, front-loaded with what the tool returns and scoped by account/network. Each sentence adds operational value: output identity, comparison handoff, pagination, and required permission.

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?

The tool is a read-only list operation with annotations covering safety, a 90% documented schema, and an output schema. The description covers purpose, account scope, pagination, auth, and downstream use, though it leaves date-range/all_time semantics to the schema.

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 high at 90%, so the schema already documents most parameters. The description adds some meaning around account/network scope and pagination, but does not materially explain search, status, all_time, or date-range parameter behavior beyond what the schema provides.

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 names a specific verb and resource ('Lists individual ads') and immediately adds scope and output ('with their performance for a period, across all connected ad accounts or one account or network'). It distinguishes the tool from campaign-level siblings and points to postly_compare_ads for ad comparison.

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?

It clearly explains when to use the tool for individual ad performance across all accounts or one account/network, and references postly_compare_ads for comparison use. It lacks an explicit contrast with postly_get_ads_overview or postly_list_ad_campaigns, but the usage context is otherwise clear.

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?