Skip to main content
Glama

get_audience_health

Check the health and delivery readiness of a custom audience. View match rate, audience size, and operation status.

Instructions

Get health status and delivery readiness of a custom audience. Shows match rate, size, and operation status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audience_idYesCustom audience ID

Implementation Reference

  • Registration and handler for the 'get_audience_health' tool. Fetches health status (approximate count bounds, operation status, delivery status, permission for actions) of a custom audience by ID via the Meta API.
    // ─── get_audience_health ────────────────────────────────────
    server.tool(
      "get_audience_health",
      "Get health status and delivery readiness of a custom audience. Shows match rate, size, and operation status.",
      {
        audience_id: z.string().describe("Custom audience ID"),
      },
      async ({ audience_id }) => {
        try {
          const { data, rateLimit } = await client.get(`/${audience_id}`, {
            fields: "id,name,approximate_count_lower_bound,approximate_count_upper_bound,operation_status,delivery_status,permission_for_actions",
          });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Input schema for get_audience_health: requires a single 'audience_id' string parameter.
    {
      audience_id: z.string().describe("Custom audience ID"),
    },
  • Registration of the tool named 'get_audience_health' via server.tool() with description and handler.
    server.tool(
      "get_audience_health",
      "Get health status and delivery readiness of a custom audience. Shows match rate, size, and operation status.",
      {
        audience_id: z.string().describe("Custom audience ID"),
      },
      async ({ audience_id }) => {
        try {
          const { data, rateLimit } = await client.get(`/${audience_id}`, {
            fields: "id,name,approximate_count_lower_bound,approximate_count_upper_bound,operation_status,delivery_status,permission_for_actions",
          });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are present, so the description must fully convey behavioral traits. It mentions what the tool shows but does not disclose idempotency, required permissions, side effects, 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?

The description is two sentences, front-loaded with the main purpose, and contains no extraneous information.

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?

For a simple one-parameter tool with no output schema, the description adequately states what it returns. However, it could be more complete by specifying the return format or structure.

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?

The schema covers 100% of parameters with a brief description. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 gets health status and delivery readiness of a custom audience, listing specific outputs (match rate, size, operation status). It distinguishes from siblings like get_audience and get_delivery_estimate.

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?

The description implies usage for checking audience health, but does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites.

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/mikusnuz/meta-ads-mcp'

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