Skip to main content
Glama

List Ad Accounts

postly_list_ad_accounts
Read-onlyIdempotent

Lists the paid ads networks and ad accounts connected to a Postly workspace, such as Google Ads and Meta Ads, with each account ID, name, currency, and whether it is selected for reporting. Use provider:account_id as the account key for other ads tools. 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_ad_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesPostly workspace ID.

Output Schema

NameRequiredDescriptionDefault
codeNo
dataNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds value beyond them by disclosing the auth requirement (ads.read), the response fields (account ID, name, currency, selected-for-reporting flag), and the key format consumed by other tools.

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 tight sentences with no filler: the resource and returned fields come first, then the actionable key format and permission requirement. Every clause carries information an agent needs before calling.

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?

With an output schema present, return formatting needn't be explained, and the description still summarizes the key returned fields. Annotations cover safety, the one required param is documented, and the permission plus provider:account_id convention give the agent everything needed to call it and use its output.

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?

There is a single parameter with 100% schema description coverage ('Postly workspace ID.'), so the baseline is 3. The description adds no scoping detail about workspace_id (e.g., how to obtain one or what happens across workspaces), so it does not exceed the schema's contribution.

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?

States a specific verb ('Lists') and a precisely scoped resource ('paid ads networks and ad accounts connected to a Postly workspace'), and enumerates the returned fields. It implicitly separates itself from sibling tools like postly_list_social_accounts and postly_list_ad_campaigns by naming the ad-network layer rather than social accounts or campaigns.

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?

Gives clear downstream guidance ('Use provider:account_id as the account key for other ads tools') and states the required permission scope ('Requires ads.read'), which tells the agent where this tool fits in the ads workflow. It does not name an explicit alternative or an exclusion case, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources