Skip to main content
Glama
Sign In
GrowthMCP

GrowthMCP

by Lokeshwar2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

analyze_creatives

Compute creative-level delivery and acquisition metrics from ad records to evaluate performance—without ranking creatives.

Instructions

Analyze creative-level delivery and acquisition metrics without ranking creatives.

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": {
      "records": "<records>"
    },
    "name": "analyze_creatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 discloses one trait (no ranking of creatives), but omits whether this is read-only, what permissions are needed, and how it handles the input. One behavioral hint is insufficient for an unannotated tool.

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?

A single front-loaded sentence with no wasted words. It is efficient, though arguably too sparse for a tool with an opaque required parameter, which keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but the description is otherwise thin: no annotations, no usage guidance, and a fully undocumented required array parameter. For a tool of this complexity the definition is not complete enough for reliable invocation.

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

Parameters2/5

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

The single required parameter 'records' is an array of untyped objects with additionalProperties=true and 0% schema description coverage. The description never mentions records or its expected shape, so it fails to compensate for the schema gap that the agent needs to construct a valid call.

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?

States a specific verb (analyze) and resource (creatives) plus the metric scope (delivery and acquisition). The clause 'without ranking creatives' narrows it, but it does not name or contrast with any sibling such as compare_campaign_metrics or analyze_cohorts, so an agent still has to infer where this fits.

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 when-to-use guidance and no named alternative among the many analysis siblings. 'Without ranking creatives' is a scope constraint, not a usage rule, and it does not tell the agent when this tool is the right choice.

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