Skip to main content
Glama

growthintel-mcp

Creative Performance Tool

creative-performance-tool
Read-onlyIdempotent

Returns the authenticated tenant's paid ad creative performance, ranked by lead volume: lead_count, qualified_count, won_count, avg_intent, total_spend, cost_per_won, plus LLM-derived copy labels (offer_type, urgency, cta, price_anchor) per creative. Meta only today — other ad channels have no creative-level breakdown yet, only campaign-level totals (see campaign-performance-tool).

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": "creative-performance-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of creatives to return, ranked by lead volume.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds tenant scoping ("authenticated tenant's"), the sort order that governs which rows come back, and the Meta-only channel constraint. It does not disclose the measurement time window or whether results are paginated, which are meaningful behavioral gaps for a performance endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the field list are front-loaded in one sentence, followed by the channel caveat and sibling pointer — no filler. It is dense to the point of being a run-on, with the enumerated metrics slightly crowding the routing information, but nothing is wasted.

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?

With no output schema, the description usefully enumerates the returned fields including the LLM-derived copy labels, and flags channel coverage limits. What is left unstated is the time period those metrics cover and whether there is any pagination beyond `limit`, which an agent would need to interpret performance numbers correctly.

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 coverage is 100% and the single parameter's description already explains it caps creatives ranked by lead volume. The prose repeats the ranking notion but adds no syntax, bounds, or interaction detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ("returns the authenticated tenant's paid ad creative performance") plus the ordering rule ("ranked by lead volume") and the exact metrics returned. It also explicitly disambiguates from campaign-performance-tool by contrast, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It states the positive case (creative-level paid ad metrics) and an explicit exclusion with a named alternative: non-Meta ad channels have no creative-level breakdown and should go through campaign-performance-tool. That is a clear when-to-use / when-not-to-use routing rule.

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