Skip to main content
Glama

Ads overview

get_ads_overview
Read-onlyIdempotent

Meta ads spend, ROAS, campaign count and pending approvals for the workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ads_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds value by disclosing exactly what data comes back (spend, ROAS, campaign count, pending approvals) and that it is workspace-scoped. However, it does not disclose the time window, currency/units, or whether pending approvals are truncated, which are real behavioral gaps for a metrics read.

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?

One sentence with no filler, and the metric inventory is front-loaded so an agent can pattern-match on 'ROAS' or 'spend' immediately. Nothing redundant is said.

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?

With no output schema and no parameters, the description carries the full burden of explaining what an agent receives, and it only partly does so. The metric list is a good start, but the reporting period, granularity, and shape of the response are unstated, leaving an agent unable to tell whether this answers 'how are ads doing this week' or 'all time'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description's phrase 'for the workspace' correctly signals that scoping is implicit in the caller's context rather than passed as an argument, which is the only parameter-adjacent fact worth knowing here.

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 sentence names a specific resource (Meta ads data for the workspace) and enumerates the metrics covered: spend, ROAS, campaign count, pending approvals. The implied action is a read/retrieve, and 'overview' distinguishes it from the sibling get_ad_campaign_details without opening either schema. It lacks an explicit verb, which keeps it just below top marks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus get_ad_campaign_details, get_performance_digest, or get_plan_and_usage. An agent must infer from the metric list that this is the summary-level entry point. No prerequisites or exclusions are given.

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