Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_async_report

Check an async Meta Ads insight report's status and retrieve completed results by report run ID, with pagination and selected fields.

Instructions

Check status and retrieve results of an async insight report.

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor for the result page
limitNoMaximum result rows per page
fieldsNoComma-separated insight fields to return once the job completes
report_run_idYesReport run ID from create_async_report
include_resultsNoFetch /{report_run_id}/insights when the job is complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.6.1
    • addedInput schema / properties / after
      Added value: +{
+  "description": "Pagination cursor for the result page",
+  "type": "string"
+}
    • changedInput schema / properties / fields / description
      Previous value: -"Comma-separated fields to return"New value: +"Comma-separated insight fields to return once the job completes"
    • addedInput schema / properties / include_results
      Added value: +{
+  "default": true,
+  "description": "Fetch /{report_run_id}/insights when the job is complete",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum result rows per page",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
  2. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a read-only status-check and retrieval but does not state whether the operation is idempotent, what happens if the job is incomplete, whether pagination is automatic, or any auth/rate-limit requirements. This is a minimal behavioral disclosure for a polling tool.

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 a single front-loaded sentence with zero wasted words. It immediately conveys what the tool does without unnecessary preamble.

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?

While the parameter schema is fully documented, the description is sparse for a tool with no output schema and no annotations. It does not explain the response shape, how status is returned, or when results become available, leaving meaningful contextual gaps for an agent invoking an async report retrieval tool.

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 100%, so all five parameters are documented in the schema. The description adds no additional parameter meaning or formatting guidance beyond what the schema already provides, which is the expected baseline when the schema is complete.

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?

The description states a specific verb and resource: 'Check status and retrieve results of an async insight report.' This clearly identifies the tool's function and separates it from creation tools like create_async_report, though it does not explicitly name any sibling for differentiation.

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?

Usage is implied: the async report context suggests this is called after create_async_report and potentially repeatedly to poll for completion. However, the description provides no explicit when-to-use guidance, prerequisites, or alternatives, leaving the agent to infer the workflow.

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

Deploy Server

Other Tools